MyAnonamouse's Dynamic Seedbox IP API endpoint may error in various ways against the cookie value you provide. This page will help you understand what those errors mean and how to fix them.
- 429 Last Change Too Recent
- 403 Invalid Session
- 403 Invalid Session - IP Mismatch
- 403 Invalid Session - ASN Mismatch
- 403 Invalid Session - Invalid Cookie
- 403 Incorrect Session Type - Not Allowed This Function
- 403 Incorrect Session Type - Non-API Session
Note
For errors related to Host and Origin headers, see the
security guide. For network errors, see the
network troubleshooting guide.
Cause: MAM enforces an account-wide one-hour interval between seedbox IP updates.
Fix: You just have to wait it out, at most one hour. This is a policy of MAM. Mousehole will retry automatically. You do not need a new cookie or to restart Mousehole.
Cause: MAM could not validate the session. This is a general error, usually returned when a more specific error could not be identified.
Fix: Get a new cookie value following the steps in Getting Your Cookie Value.
Cause: The session cookie is locked to a single IP address, and Mousehole is not running from that IP. This happens when the session was created with "IP locked".
Fix: Create a new session with ASN selected for "IP vs ASN locked session".
Cause: Mousehole is running on an IP that MAM does not expect. MAM expects that your IP is in a known AS (a block of IP addresses numbered by an ASN). If your IP is not in the expected AS, MAM will reject the request.
Fix: Add Mousehole's IP address to the session's allowed ASNs:
-
Copy the IP address shown on Mousehole's main page.
-
Go to the MAM Security Settings page.
-
Find your existing Mousehole session in the table and click the "Manage Session" button.
-
In the popup, add the Mousehole IP address to the "Add additional ASN via IP address" text box.
(Ensure "Yes" is selected for "Allow Session to set Dynamic Seedbox".)
Then press the "Update the session" button.
-
Back in Mousehole, press the "Update Now" button.
-
You should now see an OK status.
Note
It is normal to have to fix this issue a handful of times if your VPN connection is configured for a geographic area, such as a particular city. VPN operators may have have multiple ASNs in a given area, and therefore you may need to add multiple ASNs to your session over time.
Cause: The cookie value stored in Mousehole is incorrect — possibly a typo or a copy of the wrong value.
Fix: Get a new cookie value following the steps in Getting Your Cookie Value. When pasting the cookie value into Mousehole, ensure there are no extra spaces at the beginning or end of the value.
Cause: The session cookie belongs to a session that was not created with permission to set the Dynamic Seedbox IP. This means "Allow Session to set Dynamic Seedbox" was set to "No" when the session was created.
Fix: Get a new cookie value following the steps in Getting Your Cookie Value, ensuring to select "Yes" for "Allow Session to set Dynamic Seedbox" when creating the session.
Cause: The cookie belongs to a regular MAM web browser session, not an API session. (Did you copy the cookie from your browser's developer tools? 🤨)
Fix: Create a new session the right way by following the steps in Getting Your Cookie Value.