How to disable automatic https?

1. The problem I’m having:

I currently host jellyfin and would like to access it via my domain, but at the same time I’m not so comfortable exposing it to the internet. I currently have jellyfin.mydomain.com pointing to my local ip and I have caddy configured to listen to the respective requests.

I currently have ‘tis internal’ setup because caddy wouldn’t be able to get a certificate because it’s not exposed to the internet. However due to the internal tls jellyfin’s apps aren’t trusting my self signed certs and as a result I’d like to just disable https altogether.

Could someone advise me how to disable https for just one domain? Any help would be appreciated.

2. Error messages and/or full log output:

N/A

3. Caddy version:

2.6.2

4. How I installed and ran Caddy:

curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' | sudo gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt' | sudo tee /etc/apt/sources.list.d/caddy-stable.list
sudo apt update
sudo apt install caddy

a. System environment:

Ubuntu LXC on Proxmox host, i5 8400, 32gb ram

b. Command:

sudo caddy start

d. My complete Caddy config:

jellyfin.mydomain.com {
        tls internal
        reverse_proxy localhost:8096
}

5. Links to relevant resources:

Howdy @borkode, have you tried just specifying the http:// scheme in your site address? e.g.:

http://jellyfin.example.com {
  reverse_proxy localhost:8096
}

Leaving the scheme off the site address lets Caddy infer you want both, but being specific here tells Caddy exactly what you want.

Just worth mentioning, this version is super old, like more than two years or something. You might want to update to the latest, there’s a lot of bug fixes and feature improvements.

I’ll check out the http method, also regarding my version this is actually pretty weird. I only installed caddy a few months ago and idk why it gave me an old version. Running sudo apt update shows no version seems to not show any new versions so thats weird.

Figured out what was going, a few weeks ago I had an unrelated issue with caddy and had to run sudo apt purge caddy, doing that got rid of the cloud smith repo. After adding it back I could install the latest version of caddy. Thank you @Whitestrake for letting me know otherwise I’d never know haha

1 Like