> ## Documentation Index
> Fetch the complete documentation index at: https://www.notifuse.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Production checklist

> What to check on a self-hosted Notifuse instance before you send real email from it.

Go through this list before a self-hosted instance sends its first real campaign. It assumes the official `compose.yaml` from [Installation](https://www.notifuse.com/docs/self-hosting/installation.md).

## Network and HTTPS

- Put a reverse proxy with TLS in front of Notifuse. `compose.yaml` serves plain HTTP on port `8081`, on every interface unless you set `HTTP_BIND=127.0.0.1` in `.env`, which you should do when the proxy runs on the same server. See [Installation](https://www.notifuse.com/docs/self-hosting/installation.md#option-1-docker-compose-recommended).
- Make the proxy forward the original `Host` header, or set `X-Forwarded-Host`. Without it, web versions of your emails stop opening ([A public API endpoint](https://www.notifuse.com/docs/self-hosting/installation.md#a-public-api-endpoint)).
- Set the API endpoint to the public HTTPS address, such as `https://emails.yourcompany.com`. The setup wizard prefills **API endpoint** with the address of the page, so check it if you ran the wizard over plain HTTP. Notifuse writes this address into emails, invitations and provider webhooks. To change it later, follow [Changing your domain](https://www.notifuse.com/docs/self-hosting/changing-domain.md).

## Secrets and database

- Generate `SECRET_KEY` once, with `openssl rand -base64 32`, and store a copy outside the server. It encrypts the stored credentials, and a new key on its own leaves them unreadable. To change it, follow [Replacing the secret key](https://www.notifuse.com/docs/self-hosting/installation.md#replacing-the-secret-key).
- Give PostgreSQL its own password with `DB_PASSWORD` in `.env`, as the installation commands do. Without it, `compose.yaml` uses `postgres`.
- Keep the PostgreSQL port bound to `127.0.0.1`. The official `compose.yaml` publishes it as `127.0.0.1:5433`, reachable from the server itself for `psql` and backups. Set `POSTGRES_HOST_PORT` in `.env` if 5433 is taken, rather than opening the port to the network.
- Keep the directory that holds `compose.yaml` where it is. Compose names the database volume after it, and a renamed directory starts a new installation on an empty database ([Installation](https://www.notifuse.com/docs/self-hosting/installation.md#option-1-docker-compose-recommended)).

## Email

- Set up the system SMTP server and send a test from **Test connection** in the setup wizard. Notifuse sends sign-in codes and invitations through it, so nobody can receive a sign-in code until it works. You can change it later as root in **System Settings**.
- Connect each workspace to its email provider. The system SMTP server only carries sign-in codes and invitations; workspaces set up their own provider for campaigns and transactional email.
- Authenticate your sending domain (SPF, DKIM, DMARC) with that provider before the first campaign. Notifuse does not check these records, so verify them at the provider. See [Authenticate your domain](https://www.notifuse.com/docs/deliverability/authenticate-your-domain.md).

![The System Settings drawer: root email, API endpoint and the system SMTP used for sign-in codes](https://www.notifuse.com/docs/assets/screenshots/system_settings.png)

## Backups

- Back up every database (`notifuse_system` and each `notifuse_ws_…` database) on a schedule, and keep `SECRET_KEY` with the dumps, off the server. [Backups](https://www.notifuse.com/docs/self-hosting/backups.md) gives the commands.
- Restore one backup into an empty installation at least once, and sign in to check your workspaces, before you rely on it.
- Once the restore works, set `DB_EXPECT_EXISTING=true` in `.env`. Notifuse then refuses to start on an empty database instead of creating a new installation on it.

## Updates and telemetry

- Decide on **Check for updates** and **Anonymous telemetry**, both on by default in the setup wizard. Update checks show new versions and security fixes on the workspace list. Change either later in **System Settings** (**Check for Updates**, **Telemetry**), or with the `CHECK_FOR_UPDATES` and `TELEMETRY` variables, which win over the console.
- Pin the release you run with `NOTIFUSE_VERSION` in `.env` (for example `NOTIFUSE_VERSION=v44.0`), so a new copy of `compose.yaml` does not upgrade you by surprise. When you upgrade, follow [Upgrade to a new release](https://www.notifuse.com/docs/self-hosting/upgrading.md).

## Monitoring

- Watch `GET /healthz`. It answers `200` with `{"status":"ok"}` when Notifuse reaches its system database within 2 seconds, and `503` with `{"status":"unavailable"}` otherwise. `compose.yaml` already uses it as the container health check, every 30 seconds.
- Read the server log with `docker compose logs -f api`. `compose.yaml` caps it at five files of 10 MB.
