Overview of 504/502 Gateway Timeout Errors
504 Gateway Timeout and 502 Bad Gateway errors occur when the server is unable to complete your request due to connectivity issues, system maintenance, or high server load. These errors are temporary in most cases and can often be resolved with basic troubleshooting or waiting for an ongoing issue to be resolved by the technical team.
Possible Common Causes
Temporary connectivity issues
High traffic or server overload
Scheduled system maintenance or updates
General Troubleshooting Steps
To address the 504 or 502 gateway timeout errors, follow these steps:
Refresh Your Browser: Press CTRL + R on your keyboard to reload the page. You can also try closing your browser and reopening it before accessing the online campus again.
Restart Your Router or Switch Connections: Restart your home router or switch between Wi-Fi and mobile data to resolve potential network issues.
Clear Browser Tabs: Close all open browser tabs, wait for a minute, and then try to reload the online campus.
Wait and Retry: If initial attempts fail, wait for 1-3 minutes before trying to refresh again. For ongoing server maintenance, it may take 15 minutes to an hour for the issue to resolve.
Try an Incognito Window or Different Browser: Open the Online Campus in a private/incognito window or use a different web browser entirely to rule out browser-specific issues.
Use the Campus Direct Link: Access your dashboard directly via the Online Campus link, like this: Online Campus Link.
Restart Your Device: As a last resort, restart your computer or mobile device.
When to Escalate
If you have followed all the troubleshooting steps and the issue persists, it is recommended to:
Check for any updates or announcements on the learner portal about ongoing maintenance or issues.
Take a screenshot, with the time and date visible, of the error and contact the Support Team on support@uctonlinehighschool.com.
Conclusion
Most 504/502 gateway timeout errors are temporary and can be resolved using basic troubleshooting steps. For extended disruptions, following the situational scenarios and contacting support with detailed error information ensures timely resolution.

