If you receive a 504 Gateway Timeout error in your standard browser window, the issue is typically caused by corrupted local browser cache, outdated session cookies, or interfering browser extensions rather than a platform-wide outage.
Follow these steps in order to restore normal access to your Portal:
1. Fully Clear Browser Cache and Cookies
Cached session data can conflict with updated portal configurations.
Clear all browsing history, cache, and cookies from "All time" (not just the past hour or day).
Close and restart your browser completely before attempting to log in again.
2. Switch to Google Chrome, other browsers or Use Incognito Mode
If using Safari, Edge, or Firefox, switch to Google Chrome to test if the issue is browser-specific.
Use an Incognito / Private Window (Ctrl + Shift + N on Windows or Cmd + Shift + N on Mac) as a temporary workaround to continue daily operations while troubleshooting your standard session.
3. Disable Conflicting Browser Extensions
Third-party extensions (especially ad blockers, password managers, and VPN or proxy plugins) can intercept or block connections to the authentication gateway.
Temporarily disable all browser extensions.
Relaunch the browser and attempt to log in. If successful, re-enable your extensions one at a time to identify the conflicting add-on.
4. Test Access via the Main Website
Navigate to the primary Anytime Mailbox login page at www.anytimemailbox.com instead of using a saved bookmark or direct sub-link.
Check if the main public site loads
What to Send to Partner Support If the Issue Persists
If the 504 error continues after completing the steps above, submit a ticket to the Partner Support Team with the following details so our tech team can isolate the gateway connection:
Screenshot: A full-screen capture showing the 504 error page, including the URL bar and error details.
Operating System (OS): Specify whether you are using Windows (e.g., Windows 10/11) or Mac (macOS version).
Browser & Version: The specific browser used (e.g., Google Chrome v128, Safari v17).
Other Details:
Confirmation that the issue still works in Incognito mode.
Whether the main public website loads or fails.
Any specific steps taken right before the timeout occurred.