Troubleshooting

Troubleshooting

What to check first, then the page that fixes your problem.

imbox docs

Find your symptom, read the cause, run the fix. Each entry quotes the message you will see, so you can search for it.

Start here

Three checks tell you which part is broken. Run them first.

On a server you set up with the script:

curl -s http://127.0.0.1:8787/healthz          # {"ok":true} when the app is up
sudo systemctl status imbox                    # running, or why it stopped
sudo journalctl -u imbox -n 100 --no-pager     # the last 100 log lines

With Docker Compose:

docker compose ps
curl -s http://127.0.0.1:8787/healthz
docker compose logs --tail 100 imbox

How to read the answers:

What you seeWhat it meansGo to
healthz does not answerThe app is not runningInstall and startup
healthz answers, the site does not openDNS, the certificate or the proxyThe site does not open
The site opens, sign-in failsPassword, lockout or two-factorSigning in
Signed in, but a button fails with a red messageOften a wrong APP_URLActions fail with "This request did not come from the app"
A mailbox shows a sync problemProvider sign-in or settingsMailboxes and sync
Mail will not sendPort, limit or providerSending
A new release did not startThe health check failedUpdates

The log has two kinds of lines worth searching for. A failed request reads request failed: METHOD /path -> status: …. A background job that failed reads job mail-sync error.

Check the version

curl -s https://imbox.example.com/api/version shows the running version and commit. If it is not what you just installed, the new release did not take. See Updates.

Loading diagram...

Pick your problem

Still stuck

  1. Run the three checks under Start here, and keep the output.
  2. Search the issues for the message you see.
  3. Open a new issue with the output of /api/version, the last 50 lines of the log, and what you did. Remove addresses and passwords first.