Email Alerts
Get an email when a container fails or a server stops answering. Gmail, Sendhiiv, Outlook and other providers.
Email alerts tell you when something breaks, without you watching a screen. Go to Monitoring → Notifications.
What triggers an email
While DeployOS is open it checks every server's containers every two minutes. It emails you when a container is unhealthy, crash-looping or dead, when a server stops answering (optional), and again when things recover. A problem that stays broken is repeated after the interval you choose (60 minutes by default) so you are reminded without being flooded.
Alerts run only while DeployOS is open on your computer; nothing is installed on your servers.
Setting it up
- Open Monitoring → Notifications and switch Email alerts on.
- Choose your email provider from the tiles. Sendhiiv, Gmail, Outlook / Microsoft 365, Postmark, SendGrid, Mailgun, Resend, Amazon SES, or Custom SMTP for any other server.
- Fill in the username and password. The password is stored in your computer's keychain, never in a file.
- Enter who should receive alerts (comma-separated).
- Press Save, then Send test email. The result stays on screen, so a long error can be read.
You can add more than one provider. The Primary one is tried first; if it fails, the others are tried in order.
Provider notes
| Provider | What to enter |
|---|---|
| Sendhiiv | Host smtp.sendhiiv.com, port 587 (STARTTLS; 465 with TLS also works). Create an SMTP credential in the Sendhiiv dashboard under API keys, then SMTP relay, and use its username and password. Use a From address on a domain you have verified in Sendhiiv |
| Gmail | Needs an App Password, not your normal password — see below |
| Outlook / Microsoft 365 | Host smtp.office365.com, port 587, your mailbox login |
| Postmark | Username and password are both your server token |
| SendGrid | Username is the word apikey; the password is your API key |
| Resend | Host smtp.resend.com, port 465 (TLS); username is resend |
| Custom SMTP | Host, port and security as given by your mail provider |
Gmail: use an App Password
Google does not allow normal passwords for apps. To get an App Password:
- Turn on 2-Step Verification on your Google account (App Passwords do not exist without it).
- Open Google's App passwords page (the Gmail form has a button that opens it), name it "DeployOS" and create it.
- Paste the 16-letter code as the password. Spaces are fine; DeployOS removes them.
- Use your full Gmail address as the username, port 587 with STARTTLS.
The form warns you if the code you paste is not 16 characters. Google Workspace admins may need to allow App Passwords first.
The From address
Leave it blank to send from the username, if the username is an email address. You can enter a plain address (alerts@yourdomain.com), a named one (DeployOS <alerts@yourdomain.com>), or just a display name (DeployOS server), in which case the username is used as the address. If your username is not an email address (SendGrid's apikey, for example), enter a real From address on a domain you have verified with the provider.
When the test fails
| Message | Cause and fix |
|---|---|
| "couldn't read the saved password … from the system keychain" | The keychain refused access. Re-enter the password and press Save |
| "no password is saved" | Type the password and press Save before testing |
| "bad From address" or "isn't a valid From address" | Use you@domain.com, Name <you@domain.com>, or a name plus an address-style username |
| The server "refused the message" | Many providers only send from an address you have verified. Check the From address and recipients |
| Authentication errors on Gmail | You used your normal password. Use an App Password |
Incident history
With Keep an incident history on, every failure and recovery is recorded under Monitoring → History, which also feeds the Dashboard's needs-attention panel.
Related: Monitoring & Metrics.