The panel does not load or says it is updating
What you see
Section titled “What you see”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.
1. An update is running
Section titled “1. An update is running”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.
2. An update stopped halfway
Section titled “2. An update stopped halfway”The update didn’t finish names the step that failed and does not recover by itself. Follow Recover from a failed update.
3. The panel service is down
Section titled “3. The panel service is down”The control panel isn’t answering, with no update running, means nginx is up and hyperion-web is not. Read why:
sudo hyperion statussudo journalctl -u hyperion-web -n 50 --no-pagerStart 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.
4. The port is not reachable
Section titled “4. The port is not reachable”“Connection refused” or a timeout on port 8443 has three common causes. Check each from the server:
sudo ss -ltn 'sport = :8443'- No listener: the panel is not running (cause 3), or
listenin/etc/hyperion/web.tomlnames another port or only127.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.
5. The certificate warning
Section titled “5. The certificate warning”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:
sudo hyperion setup-linkWhen 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.
Check that it is fixed
Section titled “Check that it is fixed”sudo hyperion statusBoth hyperion-agent and hyperion-web show active (running), and the panel’s sign-in page loads.