1. Caddy version (caddy version
):
2.5.1
2. How I run Caddy:
I run Caddy on ubuntu directly, not on docker. The purpose is to serve SSL and reverse proxy to a Budibase server installed on docker on the same machine
a. System environment:
Ubuntu 22.04
b. Command:
# systemctl restart caddy
c. Service/unit/compose file:
Paste full file contents here.
Make sure backticks stay on their own lines,
and the post looks nice in the preview pane.
d. My complete Caddyfile or JSON config:
Paste config here, replacing this text.
Use `caddy fmt` to make it readable.
DO NOT REDACT anything except credentials.
LEAVE DOMAIN NAMES INTACT.
Make sure the backticks stay on their own lines.
3. The problem Iâm having:
After executing caddy trust and configuring the Caddyfile using the option " tls internal certs" I was expecting it would work but it did not.
4. Error messages and/or full log output:
Jun 22 09:37:35 budibase01 caddy[39480]: caddy.HomeDir=/var/lib/caddy
Jun 22 09:37:35 budibase01 caddy[39480]: caddy.AppDataDir=/var/lib/caddy/.local/share/caddy
Jun 22 09:37:35 budibase01 caddy[39480]: caddy.AppConfigDir=/var/lib/caddy/.config/caddy
Jun 22 09:37:35 budibase01 caddy[39480]: caddy.ConfigAutosavePath=/var/lib/caddy/.config/caddy/autosave.json
Jun 22 09:37:35 budibase01 caddy[39480]: caddy.Version=v2.5.1 h1:bAWwslD1jNeCzDa+jDCNwb8M3UJ2tPa8UZFFzPVmGKs=
Jun 22 09:37:35 budibase01 caddy[39480]: runtime.GOOS=linux
Jun 22 09:37:35 budibase01 caddy[39480]: runtime.GOARCH=amd64
Jun 22 09:37:35 budibase01 caddy[39480]: runtime.Compiler=gc
Jun 22 09:37:35 budibase01 caddy[39480]: runtime.NumCPU=4
Jun 22 09:37:35 budibase01 caddy[39480]: runtime.GOMAXPROCS=4
Jun 22 09:37:35 budibase01 caddy[39480]: runtime.Version=go1.18.1
Jun 22 09:37:35 budibase01 caddy[39480]: os.Getwd=/
Jun 22 09:37:35 budibase01 caddy[39480]: LANG=C.UTF-8
Jun 22 09:37:35 budibase01 caddy[39480]: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
Jun 22 09:37:35 budibase01 caddy[39480]: NOTIFY_SOCKET=/run/systemd/notify
Jun 22 09:37:35 budibase01 caddy[39480]: HOME=/var/lib/caddy
Jun 22 09:37:35 budibase01 caddy[39480]: LOGNAME=caddy
Jun 22 09:37:35 budibase01 caddy[39480]: USER=caddy
Jun 22 09:37:35 budibase01 caddy[39480]: INVOCATION_ID=5346b0aefe414423b3bf38683f2d7767
Jun 22 09:37:35 budibase01 caddy[39480]: JOURNAL_STREAM=8:449323
Jun 22 09:37:35 budibase01 caddy[39480]: SYSTEMD_EXEC_PID=39480
Jun 22 09:37:35 budibase01 caddy[39480]: {"level":"info","ts":1655887055.1816814,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":""}
Jun 22 09:37:35 budibase01 caddy[39480]: {"level":"warn","ts":1655887055.1825554,"msg":"Caddyfile input is not formatted; run the 'caddy fmt' command to fix inconsistencies","adapter":"caddyfile","file":"/etc/caddy/Caddyfile","line":12}
Jun 22 09:37:35 budibase01 caddy[39480]: {"level":"info","ts":1655887055.1831179,"logger":"admin","msg":"admin endpoint started","address":"tcp/localhost:2019","enforce_origin":false,"origins":["//localhost:2019","//[::1]:2019","//127.0.0.1:2019"]}
Jun 22 09:37:35 budibase01 caddy[39480]: {"level":"info","ts":1655887055.1832745,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0xc000386c40"}
Jun 22 09:37:35 budibase01 caddy[39480]: {"level":"info","ts":1655887055.1832862,"logger":"tls.cache.maintenance","msg":"stopped background certificate maintenance","cache":"0xc000386c40"}
Jun 22 09:37:35 budibase01 caddy[39480]: run: loading initial config: loading new config: loading http app module: provision http: getting tls app: loading tls app module: provision tls: loading certificates: open internal: no such file or directory
Jun 22 09:37:35 budibase01 systemd[1]: Started Caddy.
Jun 22 09:37:35 budibase01 systemd[1]: caddy.service: Main process exited, code=exited, status=1/FAILURE
Jun 22 09:37:35 budibase01 systemd[1]: caddy.service: Failed with result 'exit-code'.
5. What I already tried:
Iâve tried to run Caddy from a docker compose file, along with budibase, but that did not work.