● caddy.service - Caddy HTTP/2 web server
Loaded: loaded (/etc/systemd/system/caddy.service; enabled)
Active: failed (Result: exit-code) since lun 2017-08-21 07:41:28 CEST; 11h ag o
Docs: https://caddyserver.com/docs
Main PID: 597 (code=exited, status=226/NAMESPACE)
ago 21 07:41:28 jarvis systemd[1]: Started Caddy HTTP/2 web server.
ago 21 07:41:28 jarvis systemd[1]: caddy.service: main process exited, code...CE
ago 21 07:41:28 jarvis systemd[1]: Unit caddy.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.
ago 21 07:41:28 jarvis systemd[1]: Started Caddy HTTP/2 web server.
ago 21 07:41:28 jarvis systemd[1]: caddy.service: main process exited, code=exited, status=226/NAMESPACE
ago 21 07:41:28 jarvis systemd[1]: Unit caddy.service entered failed state.
By the way; I was looking at this post. There are two tests mentioned. SSLabs.com gives me an A but securityheaders.io a F. Do you have the same? Is there anything I can do about this?
For the folks that were able to get Caddy to run, I have a few questions.
I’ve been at this all afternoon and still can’t access my HA box
In your configuration.yaml file, did you use base URL?
Ex.: base_url: your.site.org:8123
Also does your cert setup look like this?
ssl_certificate: /etc/ssl/caddy/acme/acme-v01.api.letsencrypt.org/sites/your.site.org/your.site.org.crt
ssl_key: /etc/ssl/caddy/acme/acme-v01.api.letsencrypt.org/sites/your.site.org/your.site.org.key
Lastly for port forwarding do you forward 80 --> 80 and 443 --> 8123?
The only thing I see wrong is forwarding 443 to 8123. 443 on your router should forward to 443 on your pi then caddy does the translation to 8123 and for any other services you add to your caddy file.
Thanks, I was able to get this working. I did end up pointing 443 --> 443 but my other issue is that for some reason, the IP of my Raspberry Pi ended up in the ip_bans.yaml. Cleaned that up and everything worked well.