Troubleshooting

Start hereCopy Anchor Link

On the node with the problem:

seylo status

It shows the node and agent version, the panel it belongs to and whether it is connected (with the last connection error and when it retries), whether the node is behind on the panel's changes, reports waiting to be sent, every service on the node with its state, and recent errors.

seylo health

runs the node health checks: Docker, disk, clock, ports, DNS, the proxy and the panel connection, each with a fix. The same checks run from the heart icon on Nodes.

seylo logs -f          # the agent's own log
seylo panel logs -f    # the panel's output, on the panel's node

Share a reportCopy Anchor Link

seylo troubleshoot

Collects what someone helping you would ask for (versions, health check results, the agent's state and logs, Docker and Seylo's containers, the node's config), removes secrets and uploads it. You get a link like https://seylo.dev/l/<id> to paste into an issue or a chat, and when it expires.

• Tokens, keys, passwords (also inside URLs and KEY=value lines), setup links, private keys and email addresses are replaced with [REDACTED] before anything leaves the node. --redact-ips also replaces public IP addresses; --keep-emails keeps email addresses.
• --include-service-logs adds the last lines of every service's logs.
• --dry-run (or --print) prints the report instead of uploading it, so you can read it first.
• The upload is refused if the report still contains something that looks like a secret. Nothing is stored in that case.
• Anyone with the link can read the report. It is not indexed by search engines and is deleted after 30 days.

Common problemsCopy Anchor Link

Still stuckCopy Anchor Link

Open an issue on GitHub with the link from seylo troubleshoot.