🐱
nginx serving normally

It works.

You are looking at the replacement for that beige Debian page with the two paragraphs of documentation links. Same job, considerably more cat.

meow.meow.meow.meow.me.ow.meow.lamps-dev.dev

What this page actually proves

  • DNS resolves this hostname to the right server, all seven labels of it.
  • nginx matched the server_name and picked the correct site block.
  • TLS terminated on a valid Let's Encrypt certificate, so no browser warnings.
  • The document root is readable and static files are being served.
  • Port 80 redirects to HTTPS instead of quietly serving plain text.
Nothing here is broken. If you expected an application and got a cat, the app simply has not been deployed to this document root yet.

Replacing this page

Drop your files into the document root and this disappears on the next request. No reload needed for static content.

/var/www/meow.meow.meow.meow.me.ow.meow.lamps-dev.dev/

Config lives at /etc/nginx/sites-available/ with the usual symlink into sites-enabled/. Test with nginx -t before reloading, always.

Served by nginx on a Raspberry Pi. Supervised by a black cat who did not consent to any of this.