Troubleshooting 502 and 503 Server Errors

Last updated: March 11, 2026

If you're experiencing 502 Bad Gateway or 503 Service Temporarily Unavailable errors when using the platform, these are typically temporary server issues that can affect various parts of the application including the dashboard, API endpoints, and portal access.

Common Scenarios

These errors can occur in several situations:

  • Dashboard access showing 503 errors

  • API calls returning 502 Bad Gateway responses

  • User creation and management functions becoming unavailable

  • General application slowdowns

What to Do

When encountering these errors:

  1. Wait and retry: These are often temporary issues that resolve automatically within a short time period.

  2. Clear browser cache: Sometimes clearing your browser's cache and cookies can help resolve loading issues.

  3. Try a different browser: Test if the issue persists across different browsers (Chrome, Edge, Firefox, etc.).

  4. Contact support: If the errors persist or are affecting critical operations, reach out to the support team with details about when the error occurred and what you were trying to do.

For API Users

If you're experiencing 502 errors with API calls:

  • Note the exact time the error occurred

  • Include the request payload/body in your support request

  • Implement retry logic in your integration to handle temporary failures

Resolution

Our technical team actively monitors for these issues and works to resolve them quickly. In most cases, these are temporary infrastructure issues that are resolved without any action needed from users. The platform team may also proactively increase resources to prevent similar issues in the future.