The page always works at /status on the panel's address. You can also show it on a domain or subdomain of your own, such as status.example.com, so customers never see the panel's address.

How it works

The page is served by the panel. A domain of your own works as a reverse proxy: your domain points to a web server, and that web server forwards every request to the panel's /status. PawStatus then uses your address in every link it creates.

PawStatus cannot create the DNS record, the nginx file or the certificate by itself, because those live outside the panel. What it does is generate everything you need to copy and then check that the result works.

Setup

  1. In Admin > Status Page > Settings > Your own domain, type the address in Public address, with https:// and no path, for example https://status.example.com.
  2. The page shows the steps for that address, ready to copy:
    • A DNS record (A, or CNAME) for the domain, pointing to the server that will run nginx.
    • An nginx block for that domain.
    • A certbot command that issues the certificate and sets up https.
  3. Create the DNS record, add the nginx block to the configuration of that server, reload nginx, and run the certbot command.
  4. Save the settings, then press Verify.

Verify fetches your address and tells you whether it really serves your status page. It needs the address to be saved first.

The nginx block

The block goes on any server you control. It can be the panel's own server. It looks like this:

ini
server {
    listen 80;
    server_name status.example.com;

    location / {
        proxy_pass https://panel.example.com/status/;
        proxy_ssl_server_name on;
        proxy_set_header Host panel.example.com;
        proxy_cookie_domain panel.example.com $host;
    }
}

Then issue the certificate:

css
certbot --nginx -d status.example.com

If your panel runs on a port other than 443, the generated block includes it in proxy_pass and in the Host header.

What changes once it is set

Every link on the page, the subscription form and its redirects, the RSS feed, the links in emails and in webhooks use your address. The page at /status on the panel keeps working too.

If Verify fails

MessageWhat to check
The address did not answerThe DNS record, the certificate and the nginx block.
The address answered but it is not serving this status pageThe proxy_pass line must point to the panel's /status/.
Private and reserved addresses are not allowedThe domain resolves to a private address. Use a public one.

Previous: Designs · Next: Notifications