Problem reloading Caddy

1. The problem I’m having:

When I try to reload Caddy to update the Caddyfile I use the following:

sudo caddy reload --config /etc/caddy/Caddyfile

2. Error messages and/or full log output:

The output I receive is:

2024/05/09 12:15:46.313 INFO using provided configuration {"config_file": "/etc/caddy/Caddyfile", "config_adapter": ""}

I have no idea what this means.

3. Caddy version:

4. How I installed and ran Caddy:

I don’t remember how I installed Caddy it has been months since I installed it.

a. System environment:

b. Command:

PASTE OVER THIS, BETWEEN THE ``` LINES.
Please use the preview pane to ensure it looks nice.

c. Service/unit/compose file:

PASTE OVER THIS, BETWEEN THE ``` LINES.
Please use the preview pane to ensure it looks nice.

d. My complete Caddy config:

# The Caddyfile is an easy way to configure your Caddy web server.
#
# Unless the file starts with a global options block, the first
# uncommented line is always the address of your site.
#
# To use your own domain name (with automatic HTTPS), first make
# sure your domain's A/AAAA DNS records are properly pointed to
# this machine's public IP, then replace ":80" below with your
# domain name.
{
	admin 0.0.0.0:2020
	acme_dns godaddy 
}

nc.sceptic.au: {
	tls internal
	reverse_proxy localhost:11000
}

sonarr.sceptic.au {
	tls internal
	reverse_proxy 192.168.50.242:8989
}

homepage.sceptic.au {
	tls internal
	reverse_proxy localhost:3000
}

overseerr.sceptic.au {
	tls internal
	reverse_proxy localhost:5055
}

maintainerr.sceptic.au {
	tls internal
	reverse_proxy localhost:6246
}

radarr.sceptic.au {
	tls internal
	reverse_proxy localhost:7878
}

readarr.sceptic.au {
	tls internal
	reverse_proxy localhost:8787
}

lidarr.sceptic.au {
	tls internal
	reverse_proxy localhost:8686
}

sabnzbd.sceptic.au {
	tls internal
	reverse_proxy localhost:8089
}

prowlarr.sceptic.au {
	tls internal
	reverse_proxy localhost:9696
}

https://audio.sceptic.au:443 {
	tls internal
	reverse_proxy localhost:13378
}

tautulli.sceptic.au {
	tls internal
	reverse_proxy localhost:8181
}

paperless.sceptic.au {
	tls internal
	reverse_proxy localhost:8003
}

actual.sceptic.au {
	tls internal
	reverse_proxy localhost:5006
}

freshrss.sceptic.au {
	tls internal
	reverse_proxy localhost:8282
}

immich.sceptic.au {
	tls internal
	reverse_proxy localhost:2283
}

dozzle.sceptic.au {
	tls internal
	reverse_proxy localhost:8888
}

ukuma.sceptic.au {
	tls internal
	reverse_proxy localhost:3001
}

filebrowser.sceptic.au {
	tls internal
	reverse_proxy localhost:8383
}

dockge.sceptic.au {
	tls internal
	reverse_proxy localhost:5001
}

linkding.sceptic.au {
	tls internal
	reverse_proxy localhost:9090
}

change.sceptic.au {
	tls internal
	reverse_proxy localhost:5000
}

duplicati.sceptic.au {
	tls internal
	reverse_proxy localhost:8200
}

stirlingpdf.sceptic.au {
	tls internal
	reverse_proxy localhost:8088
}

nomie.sceptic.au {
	reverse_proxy 192.168.50.242:5000
}
nomie-db.sceptic.au {
	reverse_proxy 192.168.50.242:5984
}

# Refer to the Caddy docs for more information:
# https://caddyserver.com/docs/caddyfile

5. Links to relevant resources:

Ubuntu 23.10
Docker 26.1.1

There’s no problem. You asked Caddy to reload the configuration from the file /etc/caddy/Caddyfile, and Caddy is telling you in an info log it’s reloading configuration from the file /etc/caddy/Caddyfile that you have provided in the command. Are your websites not working?

By the way, you might want to revoke your godaddy API key. Don’t share API keys in public.

1 Like

Oh, dear me. I hope I haven’t caused myself some issues.

Ok, I just wasn’t sure if that info was something going wrong, I’m pretty inexperienced with reverse proxies and Linux.

Thanks for your help.

1 Like