FAQ

This article collects the most common questions and troubleshooting methods you may encounter while using the panel.

Installation & Login

Q: What are the requirements for installing the panel?

A Linux server with a public IP (Debian / Ubuntu / CentOS and other mainstream distributions are recommended), with 512MB+ of memory for smooth operation. The servers being managed do not need anything installed — they only need to be reachable via SSH.

Q: What are the default account and password?

The default account is admin and the password is 123456. Please change it immediately after your first login (user icon in the top-right of the panel → User Settings).

Q: What if I forgot my login password?

If you changed it and forgot it, you can reset it on the panel server. Run the following command to reset to the default password (or set a new one):

# Go to the panel installation directory and use the built-in script to reset the password
cd /opt/ssh-everywhere
python3 -c "from app import reset_password; reset_password('new-password')"

> The exact script name may vary between versions; you can also directly edit the users table in the data/ssheverywhere.db database.

Q: How do I change the panel port (5501)?

Modify Environment=PORT=5501 in the systemd service, then reload:

systemctl edit ssh-everywhere.service
# Add or modify: Environment=PORT=your-port
systemctl daemon-reload && systemctl restart ssh-everywhere.service

Remember to open the new port in the cloud firewall / security group afterwards.

Q: Can't access the panel (port 5501)?

Troubleshoot in order:

1. Confirm the panel service is running: systemctl status ssh-everywhere.service

2. Check whether the panel server's cloud firewall / security group allows port 5501 (this is the most common cause)

3. Confirm the access address is http://server-public-ip:5501 (not https, unless you configured a reverse proxy)

Server Related

Q: What if a server shows "Offline"?

"Offline" only means the panel cannot reach it via SSH — it does not mean the server is down. Troubleshoot in order:

1. Confirm the server itself is up: check the power status in your hosting provider's console

2. Test SSH port reachability: run nc -zv <target-IP> <port> from the panel server to see whether the port is reachable

3. Check firewall / security group: whether the target server's cloud firewall / security group allows the SSH port

4. NAT server — check port mapping: confirm the NAT port mapping still exists and the internal target IP is correct

5. Check source-IP whitelist: some providers restrict source IPs on the SSH port; add the panel server's IP to the whitelist

6. Verify credentials: whether the username and password/private key are correct

Q: Can't connect when adding a server?

Confirm the SSH port, username, and password are correct
Confirm the target server's sshd is running
Confirm the firewall allows the SSH port
Major clouds (Tencent Cloud / Alibaba Cloud) disable root by default — log in with a regular user (e.g. ubuntu)

Q: Can't connect to a NAT server (non-22 port)?

A NAT server's port mapping must be reachable from the network where the panel server lives. Common causes:

The port mapping has expired (check/recreate it in the provider's console)
The provider has whitelisted source IPs (add the panel server's IP to the whitelist)
The mapped internal IP/port was entered incorrectly

Port Tunneling / Forwarding Related

Q: Port Tunneling shows "Offline"?

Tunneling depends on the Agent being online. When the Agent goes offline (device shut down, network down, Agent stopped), tunneling is interrupted
After the panel service restarts, tunneling automatically recovers when the Agent reconnects — just wait a moment
Confirm the panel server's cloud firewall allows the listening port

Q: Forwarding a non-22 port doesn't work?

Forwarding non-SSH ports (e.g. 9117) requires the tunneling server to have the new Agent installed (the old version only supported 22). Reinstall the Agent to fix it.

Q: Port Forwarding was created but doesn't take effect?

Traditional port forwarding must be done on the server itself, which requires an independent public IP. Check:

1. Whether the target server / intermediate firewall allows the target port

2. Whether the target IP you entered is actually reachable

3. Whether the cloud security group is blocking the listening port

Q: What's the difference between Port Tunneling and Port Forwarding?

Port Tunneling: for devices without a public IP, goes over the reverse tunnel and opens a public port on the panel server.
Port Forwarding: for servers with a public IP, uses the system firewall's DNAT and is performed on the target server itself.

See Port Tunneling and Port Forwarding for details.

Docker / App Installation Related

Q: App Store / Docker installation fails?

The panel displays errors honestly (it does not fake success). Common causes:

1. Outdated distribution: versions that have reached EOL, such as Fedora 32, have stopped maintaining their software sources, so installation times out or fails. Upgrading the system is recommended.

2. Network unreachable: the official Docker sources (get.docker.com / download.docker.com) may be inaccessible in some network environments (e.g. NAT servers in mainland China). In this case, configure a Docker mirror source in China, or use the "mirror source" feature to switch to an Alibaba Cloud source.

3. Package name differences: some apps (e.g. ufw, Node.js's deb.nodesource) depend on specific distributions and may not install on non-Debian/Ubuntu systems; the error message will clearly indicate this.

Q: Pulling Docker images is very slow / times out on servers in mainland China?

This is a network issue, not a panel issue. It is recommended to configure a Docker image accelerator (public accelerators such as docker.1ms.run / docker.m.daocloud.io), or first run the following on the server:

# Reference: configure the Alibaba Cloud personal accelerator (replace with your own accelerator address)
sudo mkdir -p /etc/docker
sudo tee /etc/docker/daemon.json <<'EOF'
{ "registry-mirrors": ["https://your-accelerator-address"] }
EOF
sudo systemctl restart docker

General Troubleshooting Tips

1. Test port reachability first, then check credentials: nc -zv <IP> <port>

2. Compare with other servers: if servers of the same type connect fine but only this one fails, the problem is specific to this one (firewall/mapping/whitelist)

3. Check the logs: panel logs are in service.log; tunnel/Agent logs can help locate connection problems

Documentation

FAQ