Something is wrong

Two things make a problem fixable: what you expected, and what the server says.

First, ask the server

sudo nukeflow doctor

It checks the things that actually break — DNS pointing somewhere else, a certificate that was never issued, a disk that filled up, mail that is refused, a container that keeps restarting — and says which one it is. A surprising share of problems end here.

Then collect the details

sudo nukeflow diagnostics

This writes an archive next to you: versions, container states, the last log lines, the results of the same checks. Every secret from .env and anything shaped like a password, a token or a key is replaced before it is written, and e-mail addresses are masked unless you ask to keep them.

Read it before you send it — tar -xzf and look. It is your data and you should know what is in it.

Send it

Attach the archive to a message describing what you did, what you expected and what happened instead. Include the version (nukeflow status prints it).

Nukeflow is young. If you are reading this page, you are one of the first people to run it, and a report from you is worth more than a hundred later ones.

Before you lose anything

If the installation is broken but the data is intact, do not reinstall. nukeflow rollback returns to the previous release including the database, and nukeflow backup now takes a copy first. Ask before you delete anything.