Caddy Service crashed

Hi,

I was editing my Caddy file, and when I tried to reload it the Caddy Service failed to start

Here are my logs

– The start-up result is done.
Oct 29 12:32:03 CadServ kernel: random: crng init done
Oct 29 12:32:04 CadServ su[439]: Successful su for root by skywave
Oct 29 12:32:04 CadServ su[439]: + /dev/tty1 skywave:root
Oct 29 12:32:04 CadServ su[439]: pam_unix(su:session): session opened for user root by skywave(uid=1000)
Oct 29 12:32:04 CadServ su[439]: pam_systemd(su:session): Cannot create session: Already running in a session
Oct 29 12:32:15 CadServ caddy[412]: Activating privacy features…2017/10/29 12:32:15 get directory at ‘https://acme-v01.api.letsencrypt.org/directory’: failed to get json “https://acme-v01.api.letsencrypt.org/directory”: Get https://acm
Oct 29 12:32:15 CadServ systemd[1]: caddy.service: Main process exited, code=exited, status=1/FAILURE
Oct 29 12:32:15 CadServ systemd[1]: caddy.service: Unit entered failed state.
Oct 29 12:32:15 CadServ systemd[1]: caddy.service: Failed with result ‘exit-code’.
Oct 29 12:34:43 CadServ systemd[1]: Network Service is not active.
Oct 29 12:34:43 CadServ systemd[1]: Dependency failed for Wait for Network to be Configured.
– Subject: Unit systemd-networkd-wait-online.service has failed
– Defined-By: systemd
– Support: Debian -- Support

– Unit systemd-networkd-wait-online.service has failed.

– The result is dependency.
Oct 29 12:34:43 CadServ systemd[1]: systemd-networkd-wait-online.service: Job systemd-networkd-wait-online.service/start failed with result ‘dependency’.
Oct 29 12:34:43 CadServ systemd[1]: Started Caddy HTTP/2 web server.
– Subject: Unit caddy.service has finished start-up
– Defined-By: systemd
– Support: Debian -- Support

– Unit caddy.service has finished starting up.

– The start-up result is done.
Oct 29 12:35:03 CadServ caddy[450]: Activating privacy features…2017/10/29 12:35:03 get directory at ‘https://acme-v01.api.letsencrypt.org/directory’: failed to get json “https://acme-v01.api.letsencrypt.org/directory”: Get https://acm
Oct 29 12:35:03 CadServ systemd[1]: caddy.service: Main process exited, code=exited, status=1/FAILURE
Oct 29 12:35:03 CadServ systemd[1]: caddy.service: Unit entered failed state.
Oct 29 12:35:03 CadServ systemd[1]: caddy.service: Failed with result ‘exit-code’.
Oct 29 12:37:20 CadServ sshd[465]: Accepted password for skywave from 192.168.1.156 port 60636 ssh2
Oct 29 12:37:20 CadServ sshd[465]: pam_unix(sshd:session): session opened for user skywave by (uid=0)
Oct 29 12:37:20 CadServ systemd[1]: Started Session 3 of user skywave.
– Subject: Unit session-3.scope has finished start-up
– Defined-By: systemd
– Support: Debian -- Support

– Unit session-3.scope has finished starting up.

– The start-up result is done.
Oct 29 12:37:20 CadServ systemd-logind[319]: New session 3 of user skywave.
– Subject: A new session 3 has been created for user skywave
– Defined-By: systemd
– Support: Debian -- Support
– Documentation: multiseat

– A new session with the ID 3 has been created for the user skywave.

– The leading process of the session is 465.
Oct 29 12:37:30 CadServ su[481]: Successful su for root by skywave
Oct 29 12:37:30 CadServ su[481]: + /dev/pts/0 skywave:root
Oct 29 12:37:30 CadServ su[481]: pam_unix(su:session): session opened for user root by skywave(uid=1000)
Oct 29 12:37:30 CadServ su[481]: pam_systemd(su:session): Cannot create session: Already running in a session
Oct 29 12:39:29 CadServ systemd[1]: Reloading.
Oct 29 12:39:30 CadServ systemd[1]: apt-daily.timer: Adding 3h 34min 56.693526s random time.
Oct 29 12:39:30 CadServ systemd[1]: apt-daily-upgrade.timer: Adding 47min 18.033860s random time.

Can anyone help me please?

This is also what I get after running Journalctl -u caddy.service

Oct 29 12:45:09 CadServ systemd[1]: Started Caddy HTTP/2 web server.
Oct 29 12:45:29 CadServ caddy[391]: Activating privacy features…2017/10/29 12:45:29 get directory at ‘https://acme-v01.api.letsencrypt.org/directory’: failed to get json “https://acme-v01.api.letsencrypt.org/directory”: Get https://acm
Oct 29 12:45:29 CadServ systemd[1]: caddy.service: Main process exited, code=exited, status=1/FAILURE
Oct 29 12:45:29 CadServ systemd[1]: caddy.service: Unit entered failed state.
Oct 29 12:45:29 CadServ systemd[1]: caddy.service: Failed with result ‘exit-code’.
Oct 29 12:58:10 CadServ systemd[1]: Started Caddy HTTP/2 web server.
Oct 29 12:58:30 CadServ caddy[467]: Activating privacy features…2017/10/29 12:58:30 get directory at ‘https://acme-v01.api.letsencrypt.org/directory’: failed to get json “https://acme-v01.api.letsencrypt.org/directory”: Get https://acm
Oct 29 12:58:30 CadServ systemd[1]: caddy.service: Main process exited, code=exited, status=1/FAILURE
Oct 29 12:58:30 CadServ systemd[1]: caddy.service: Unit entered failed state.
Oct 29 12:58:30 CadServ systemd[1]: caddy.service: Failed with result ‘exit-code’.

Derp, figured it out. The new entry in Caddyfile was the problem. Which is strange since I used the same template for the other services

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.