I updated to caddy 2.8.1 and now my caddy isn't running correctly (very new to this)

Help
1

1. The problem I’m having:

I updated to caddy 2.8.1 and now I’m running into an error launching it. my configuration was working just fine until I updated it and I don’t really know what to do or what’s going on with why it wont run correctly anymore. I am very new to a lot of this (server hosting, linux, and and networking) and I just was hosting a jellyfin server so I could watch stuff during lunches at work and such. I don’t fully understand a lot of these concepts but I would like to learn about them. I do have xcaddy and go installed because I’m using cloudflare. any Advice, help or just understanding of what’s going on is greatly appreciated.

2. Error messages and/or full log output:

Error: adapting config using caddyfile: parsing caddyfile tokens for 'tls': getting module named 'dns.providers.cloudflare': module not registered: dns.providers.cloudflare, at Caddyfile:4

3. Caddy version: 2.8.1

4. How I installed and ran Caddy:

sudo apt-get install caddy
sudo caddy start

a. System environment:

Ubuntu 22.04.4 LTS (GNU/Linux 5.15.0-107-generic x86_64)

b. Command:

sudo caddy start
sudo caddy

d. My complete Caddy config:

jelly.inflatejoe.com {
        reverse_proxy 10.0.0.38:8096
        tls {
                dns cloudflare ***************my api key**********************
        }

}

5. Links to relevant resources:

2

The issue is you installed Caddy using the apt repo, then built Caddy with the cloudflare plugin and placed the final executable in-place of the plain vanilla Caddy executable. The apt tool doesn’t know that you’ve customized the executable, so it blindly replaced the executable with the new version when it came time to upgrade.

To retain the custom executable, you should follow the steps at the bottom of this page:

Build the custom caddy executable like you did before if you need the Cloudflare plugin.

That said, your Caddyfile seems to not require wildcard certificate, so you don’t need the Cloudflare plugin.

2 Likes
3

when you say doesn’t require wildcard certificate and that I don’t need the cloudflare plugin, what exactly does that mean? If I can just run it without using cloudflare and only caddy I wouldn’t mind that. Also thank you for the quick reply and help

4

Is the posted Caddyfile the full content of the file? In other words, do you have any other site defined as this?

*.inflatejoe.com {
     # config body
}

If not, you can simply change your Caddyfile to:

jelly.inflatejoe.com {
        reverse_proxy 10.0.0.38:8096
}
2 Likes
5

Oh awesome, and yeah that was the entire file, I really am just looking to use this for access to my jellyfin server outside my home

6

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