-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
Mark Rotteveel | Dotwebster.com edited this page Jul 3, 2026
·
1 revision
Use this page for first-pass checks before deeper investigation.
Check:
- Relaywright service is running.
- HTTPS port is correct.
- Host firewall allows the selected admin port from your management network.
- Browser is using
https://, nothttp://, unless HTTP was intentionally enabled. - Certificate warning is expected if using a self-signed certificate.
Check:
- device source IP is covered by an enabled Trusted Network;
- SMTP listener port is reachable from the device;
- sender address is allowed by global or device policy;
- recipient domain is allowed and not blocked;
- message size and recipient count are under limits;
- rate limit has not been reached.
Use Diagnostics Flow Checker with the device IP, sender, recipients, and size.
Check:
- upstream host and port;
- TLS mode;
- upstream authentication;
- DNS from the Relaywright host;
- outbound firewall rules;
- upstream provider rate limits or outages.
Run upstream connectivity diagnostics and inspect message delivery attempts.
Check:
- backup directory is writable;
- data volume has enough space;
- previous backup validation result;
- encryption password if validating an encrypted backup;
- whether the install uses SQLite or a server database.
Built-in backup and restore is SQLite-only. SQL Server and MySQL require platform backup tooling.
Check:
- alert recipients are valid;
- alert rule is enabled;
- cooldown has elapsed;
- upstream configuration works;
- the upstream provider accepts mail from the configured Relaywright account.
Do not paste secrets, raw message bodies, OAuth client secrets, certificate passwords, protected blobs, or private SMTP transcripts into public issues, Wiki pages, screenshots, or shared logs.