• Unix-likes are difficult. On 4-5 AM:
    • Caddy‘s file server cannot read from /home if it runs as a systemd service.1 It was reading /home fine until the server had to be rebooted by its server host. I wouldn’t know why it was working fine before.
      • The related issue also caused problems with how Caddy wrote logs, which in turn prevented Caddy from serving. Again, not sure why, seemed like the process user root was changed to caddy.
        • The fix was deleting the log file.
      • The website content of the spacious nexus couldn’t be served by Caddy. As a quick fix, I copied the content to a place where Caddy can read.
  • configure quartz to write to new place, or move it idk. Set Quartz to output to a different directory by using the --output flag.

Footnotes

  1. If you’re running Caddy as a systemd service, reading files from /home will not work, because the caddy user does not have “executable” permission on the /home directory (necessary for traversal). - Caddy Documentation. ↩