Troubleshooting Containerized Consoles#

  • Health shows Error. Confirm the hostname resolves, port 3000 is reachable from the SynergyCP master, the API key matches, and scp-console-server is running on the Console Server (systemctl status scp-console-server).
  • Consoles stay “warming up”. The Console Server hasn’t obtained its SSL certificate yet. Verify the public DNS A record is correct and that ports 80 and 443 are reachable from the internet, then allow a few minutes for issuance.
  • “No healthy console server” when launching. The server’s IP Group has no healthy Console Server assigned. Assign a Console Server to that IP Group, or fix the health of the one already assigned.
  • An image or tag is missing when assigning a server. Use Refresh console image catalog on the Console Servers page to refresh the available images.
  • The console connects but the BMC KVM won’t load. Confirm the Console Server host itself can reach the BMC network (ping / curl -k a known BMC IP). If the host can’t reach the BMCs, neither can the containers it runs.

For problems specific to uploading ISOs into a console, see the troubleshooting notes on Uploading ISOs to a Console.

Backward Uploading ISOs to a Console Upgrading Forward