Caddy continues using old configuration after Caddyfile update.

Updated Caddyfile but changes don't take effect. Caddy logs show errors pointing to old ports or configuration. Services show 502 Bad Gateway after proxy configuration changes.

Caddy maintains an autosave.json file that caches configuration. When you update the Caddyfile, Caddy may still use the cached autosave configuration instead of the new file.

Remove the autosave file and restart Caddy.

Steps:

1. Remove the autosave file:

```bash docker exec folkzone-wiki rm /config/caddy/autosave.json ```

2. Restart Caddy:

```bash docker compose restart caddy ```

3. Verify the new configuration loaded:

```bash docker compose logs –tail=10 caddy ```

Remove autosave.json after manual Caddyfile changes. Use `caddy reload` instead of restart when possible.

• Troubleshooting Index
• Docker Infrastructure

Last updated: 2026-06-19

• Return to folkzone