CAST IMAGING – V3 – SSO - Login - Internal Server Error HTTP 500 - HttpHostConnectException – CAST

Imaging is not opening and displays in the login page a White label error which indicates,

Error Type as Internal Server Error (HTTP 500) and the Cause as HttpHostConnectException that is the application tried to connect to localhost:8096 but the connection was refused.

The error occurs because the Imaging application on port 8090 is trying to connect to the SSO service on localhost:8096, but that service is not running or not reachable.

Action Plan

Check the SSO logs. If there are java.io.EOFException in SerializedApplication.read(), they indicate that there is a corrupted Keycloak SSO service initialization. The java.io.EOFException strongly suggests, incomplete Keycloak startup, corrupted Keycloak data directory or broken realm import during initialization.

Imaging in port 8090 calls SSO for login validation. If Keycloak fails, Imaging UI cannot authenticate, backend calls to auth fail, Imaging cannot connect to 8096, raising HTTP 500 and HttpHostConnectException.

This can be corrected with uninstalling and reinstalling the SSO.
Before uninstalling and reinstalling the SSO, check if there are any dependencies that are indirectly breaking the authentication because Imaging login is a multi step flow.
- Check if any port is already in use. Confirm 8096 is available for SSO, 7474 / 7687 is available for Neo4j and 8090 for Imaging.
- Check if any firewall is blocking the port.
- Check if all the required services are running.
- Check if there is no memory exhaustion.
- Check if the disk is full. If disk is full SSO cannot write temp files, JVM cannot create logs, port never binds, particularly after Neo4j crash dump generation or large docker logs.
- Check if large Neo4j crash dumps are present. CAST Imaging uses Neo4j as its backend graph database. Though it runs as a separate service Imaging depends on it during startup. If Neo4j crashes, Imaging backend may fail initialization, SSO token validation can appear broken and there may be cascading service failures. Please refer CAST IMAGING – V3 – SSO - Error. SSO is not reachable
Stop the SSO service, which will stop all the other dependent services. Open the installation folder of Imaging console V3 which you have unzipped for installation, where you can find a folder named Component installer.
Navigate inside the component installer to Imaging-service -> CAST-Imaging-SSO -> tools.
First, run the cast-imaging-sso-remove bat using cmd with admin mode to remove the existing SSO service.
Clean up the programdata path for the SSO service, because during installation it will check the path for any existing data.If the path contains residual files from a previous installation, it can cause, Failed initialization, corrupted realm or user data and service failing to start.
Reinstall the SSO service by running cast-imaging-sso-install bat using cmd in admin mode, to reinstall the SSO service cleanly.
And then navigate to Program files where you have the option to run the startup batch, start the service in their respective order.

NB: Do not reinstall SSO without cleaning old ProgramData or /var/lib/keycloak first.

CAST Imaging v3, SSO is typically backed by Keycloak the open-source identity and access management (IAM) solution. It runs on port 8096, handles authentication that includes tokens, sessions and realms.

CAST IMAGING – V3 – SSO - Error. SSO is not reachable