Thank you for the suggestion. I did exactly as you requested, but the problem is the same. I checked the journal logs again and they are empty.
Job for caddy.service failed because the control process exited with error code.
See "systemctl status caddy.service" and "journalctl -xeu caddy.service" for details.
mike@ubuntu-s-1vcpu-1gb-nyc3-01:/$ journalctl -u caddy --no-pager | less +G
mike@ubuntu-s-1vcpu-1gb-nyc3-01:/$ systemctl status caddy.service
× caddy.service - Caddy
Loaded: loaded (/etc/systemd/system/caddy.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Sat 2024-02-10 15:12:19 UTC; 34s ago
Duration: 4min 3.200s
Docs: https://caddyserver.com/docs/
Process: 27515 ExecStart=/usr/bin/caddy run --environ --config /etc/caddy/Caddyfile (code=exited, status=1/FAI>
Main PID: 27515 (code=exited, status=1/FAILURE)
CPU: 81ms