Description
A Bad Gateway error during sign-in may indicate that the Web Server cannot communicate with the Authentication Server.
Solution
Open your browser’s developer tools. The keyboard shortcut may vary depending on the browser you are using.
Open the Network tab and enable Preserve log.
Use the Network tab and select Preserve log before reloading the page.
If the failed request uses the /auth path, the Web Server is trying to contact the Authentication Server, but the request is not completing successfully.
Check the Server Manager Console (SMC) to confirm whether the Authentication Server is running.
Start the Authentication Server if it is stopped.
After the Authentication Server starts, open the Spectrus JS link again.
In this example, the response (Status Code 200 OK) confirms that the Authentication Server is now reachable.
This indicates that the login process has successfully reached the authentication stage.
Tip: If you see the Spectrus JS screen with three dots (…), the page is still being served by the Web Server. If the page appears without the dots and prompts for a username and password, it is coming from Keycloak.
vs.
Comments
0 comments
Article is closed for comments.