Skip to content

Troubleshooting

A tab I expected isn't there

Cockpit adapts to the gateway's actual hardware. Wi-Fi and Cellular tabs (and the Default route card) on the Network page only appear on models that have that hardware — see Network → Overview. If your model doesn't have Wi-Fi or a cellular modem, those tabs are expected to be missing.

Network page shows an error for Cellular, ZeroTier, or EProx

The Node.js web process talks to a separate, privileged helper process for anything that needs elevated access — networking, services, updates. If that helper is unreachable, the affected panel on the Network page shows an error message in place of its normal content, while the rest of the page (like Ethernet) keeps working.

If you see this:

  1. Check whether the issue is limited to one panel or affects the whole Network page.
  2. Try Settings → System → Reboot device if the problem doesn't clear on its own — this restarts both the web process and the helper.
  3. If it persists after a reboot, contact whoever supports this gateway's deployment — this points to a problem with the helper process itself, not something fixable from the Cockpit UI.

I can't sign in

  • "Invalid username or password" covers both a wrong password and an unrecognized username — Cockpit doesn't distinguish the two, so double check both.
  • "Too many attempts. Try again shortly." means sign-in is temporarily rate-limited after repeated failures. Wait a minute before retrying.
  • If you were told you have a starting/temporary password, use that — you'll be walked through setting a new one immediately after signing in.

I saved an Ethernet change and now can't reach the gateway

This is exactly the scenario the Ethernet staged-change flow protects against. Wait out the countdown shown in the pending banner (typically well under a few minutes) — the gateway automatically rolls back to its previous, working configuration on its own. Once you can reach it again, re-check your intended settings before saving.

I disabled a service and lost remote access

If the service you disabled was flagged as remote-access-critical (see Services), you'll need local access to the gateway to re-enable it — Cockpit warns about this before you confirm, precisely because it can't be undone remotely once you've lost the connection.