Skip to content

The panel does not load or says it is updating

One of these, in the browser at the panel address:

  • A page titled Hyperion is updating with a list of steps.
  • A page headed The update didn’t finish.
  • A page headed The control panel isn’t answering.
  • The browser reports “connection refused” or a timeout.
  • The browser warns about the certificate.

Rule these out in order. Run the commands on the master over SSH.

Hyperion is updating appears while hyperion update has the panel stopped to swap the programs. The page lists the steps and returns to the panel by itself. Do nothing and wait. If you have a shell open on the server, the update’s own output shows the same step.

Check: sudo hyperion status shows hyperion-web as active (running) again when the update ends.

The update didn’t finish names the step that failed and does not recover by itself. Follow Recover from a failed update.

The control panel isn’t answering, with no update running, means nginx is up and hyperion-web is not. Read why:

Terminal window
sudo hyperion status
sudo journalctl -u hyperion-web -n 50 --no-pager

Start it again with sudo systemctl restart hyperion-web. If it stops again, the journal names the cause. A new release that cannot start is handled in Recover from a failed update.

“Connection refused” or a timeout on port 8443 has three common causes. Check each from the server:

Terminal window
sudo ss -ltn 'sport = :8443'
  • No listener: the panel is not running (cause 3), or listen in /etc/hyperion/web.toml names another port or only 127.0.0.1. See Configuration.
  • A listener, but the connection fails from outside: a firewall in front of the server. The Firewall page shows whether the node drops by default and whether the Hyperion panel + RPC preset is applied, see Manage a node’s firewall. An unconfirmed default-drop reverts by itself after 300 seconds.
  • Your address was banned after repeated failed sign-ins: see Cannot sign in.

Until you give the panel a domain with a certificate, it serves a self-signed certificate and browsers warn. The setup wizard link prints the certificate’s SHA-256 fingerprint so you can compare it. To set a domain and certificate, use Settings, Panel, Panel domain.

If the setup wizard link is lost and setup is not finished, print a new one:

Terminal window
sudo hyperion setup-link

When setup is already finished, the command answers “Setup is already finished — sign in to the panel normally.”

Apply the fix for the cause that matched above. If none matched, read the last 50 lines of the journal for hyperion-web and hyperion-agent and look up the message.

Terminal window
sudo hyperion status

Both hyperion-agent and hyperion-web show active (running), and the panel’s sign-in page loads.