Mailwake

Troubleshooting

Follow the path in order: the outpost process → mailbox → subscribed folder → delivery channel → phone. A channel test bypasses mailbox monitoring; a new message checks the whole path.

The outpost or the console is unreachable

Check docker compose ps and docker compose logs --tail=100 core. Localhost binding is intentional; use an SSH tunnel or a working HTTPS proxy from another device. Check writable volume permissions when startup reports data_directory_permission_denied or data_directory_read_only. The container runs as user 10001:10001.

Setup code or administrator password

Until setup completes, each outpost restart rotates the setup code. Read the current process logs. To reset an administrator password, stop the outpost and use the same Compose project and data volume:

sh 
docker compose stop core
docker compose run --rm -it core admin reset-password
docker compose start core

The interactive reset signs out browser sessions and preserves API tokens, mailboxes and queued work. The recovery command takes the data-directory lock, so the running outpost must be stopped.

A new message produces no notification

  1. Verify the mailbox connection and IMAP credentials.
  2. Check that the exact server folder is subscribed. A fresh subscription skips old messages.
  3. Allow the selected scheduled interval to pass, or inspect the realtime connection.
  4. Inspect delivery history. If there is no event, investigate monitoring. If an event failed, inspect its channel error.
  5. Send a channel test. For Mailwake App, verify both the selected receiving phone and ordinary push entitlement.

A retry count of 0 means one attempt. Increase it deliberately before expecting automatic retries. A channel's accepted status confirms service acceptance; inspect the downstream provider and phone for display issues.

App connection fails

Open the outpost HTTPS address in Safari first. Check the certificate and routing, create a fresh five-minute invitation, and compare the outpost fingerprint. A clock_skew error requires synchronizing the outpost host clock. Check that the owner granted the required permissions and that Pro is active for actions that require it.

If the phone was revoked, select a new receiving phone and save the channel. After changing the push delivery service environment, use the documented operator reset in deployment and re-pair; environment identities stay separate.

Ask for help

Use GitHub Issues for reproducible outpost bugs. Include version, error code, timing and the console's redacted diagnostics. Keep passwords, API tokens, invitation links and message content out of public reports. Report security issues using SECURITY.md.

Markdown · AGPL-3.0-only · Mailwake contributors