---
tags: journal
date: 2026-07-09
draft: true
publish: false
---
- *Unix*-likes are difficult. On 4-5 AM:
  - *[[Caddy]]*‘s [file server](https://caddyserver.com/docs/caddyfile/directives/file_server) cannot read from `/home` if it runs as a *systemd* service.[^systemd-service] 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.

[^systemd-service]: *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*](https://caddyserver.com/docs/caddyfile/directives/file_server).