Troubleshooting & Getting Help
Running a hub sometimes involves an unfamiliar computer term. This page exists so you don’t have to guess, and so you know exactly where to ask when it’s not here.
Common issues
Section titled “Common issues”My hub’s setup script won’t run
Section titled “My hub’s setup script won’t run”Make sure Docker is installed and actually running (look for its icon in your system tray/menu bar) before running the setup script. The script needs Docker to be open, not just installed.
My hub was working, now it isn’t reachable
Section titled “My hub was working, now it isn’t reachable”Check that the computer running your hub is still on and connected to the internet or your network: a hub only works while its computer is running. If the computer is fine and it’s still unreachable, see Getting Help.
My browser shows a security warning visiting my hub
Section titled “My browser shows a security warning visiting my hub”This shouldn’t happen under normal operation: your hub’s certificate is issued and renewed automatically (see Automatic HTTPS). If you see this, report it; it usually means something needs attention on the automatic side, not something you can fix by clicking through the warning.
I forgot my hub’s admin password
Section titled “I forgot my hub’s admin password”Ask another admin on your hub to reset it from the Members tab in Hub Management, if one exists. If you’re the only admin, this currently needs direct help. See Getting Help.
Guest Wi-Fi setup isn’t working
Section titled “Guest Wi-Fi setup isn’t working”Double check the guest network password is at least 8 characters, and that you ran the setup script the way described on screen (Administrator on Windows, sudo on Linux): most failures here trace back to one of those two things. See Guest Wi-Fi Access.
Getting help
Section titled “Getting help”If nothing above covers it, don’t try to guess your way through unfamiliar terminal commands; ask. citinet’s issue tracker on GitHub is the main place to report problems today.
When reporting, include what you were trying to do, what happened instead, and your hub’s visibility setting (Local Network Only or Tailscale): that’s usually enough for someone to help without needing back-and-forth.
If you’re comfortable with a terminal and want to dig in yourself first, see Command-Line Reference for the same kind of hands-on Docker/log inspection used to diagnose real issues on this project.
