Logs & support

When something isn't behaving and you want help, the fastest path is to capture your instance's logs and share them with support. Because GRIDer runs on your own server, those logs live with you — nobody else can read them unless you send them.

Viewing logs

GRIDer runs as Docker containers. From the install directory on your server (the default is /opt/grider):

# Live — follow the app logs
docker compose logs -f app

# The last 200 lines
docker compose logs --tail=200 app

# Only what happened in the last hour
docker compose logs --since=1h app

• app is the GRIDer service; db is its database. Most support cases only need app.
• Save them to a file you can attach by redirecting the output:

docker compose logs --since=2h app > grider-logs.txt

If you followed the Hetzner guide, you reach the server over SSH — your VPS provider's console also has an SSH/terminal button.

What's safe to share

GRIDer is built not to write secrets to its logs — no private keys, API secrets or seed phrases. The logs hold operational events (grid actions, errors, timings), which is exactly what support needs. Even so, skim a file before sending it, and never share your install token, your .env file or any exchange API secret.

Getting support

1. Reproduce the issue, or note when it last happened.
2. Capture the relevant logs (a --since window around that time helps).
3. Open a ticket on Discord and attach the file, with a short note on what you expected versus what happened.

For anything touching your funds, remember GRIDer should never need withdrawal permission or your seed phrase. See Troubleshooting for common situations you can often resolve yourself, and Updating GRIDer if a fix has shipped in a newer version.