2025-03-12, 10:46 PM
My caddy config wasn't the issue.
I have solved it by trusting my caddy certificate in Windows as a Trusted Root Certificate. I confirmed in Wireshark that the Jellyfin client app, even when I put in http:// as the URL, and even when I set up caddy to ONLY serve HTTP, Jellyfin still tries to access HTTPS instead. It seems like the Jellyfin client does not accept domains that are not TLS-supported. Unfortunately, I don't think it's possible to trust a custom certificate on my smart TV. So I'll have to stick to using the IP address there. Or, getting a proper certificate, but that would mean exposing my homelab IP in my subdomain DNS records, and opening a port to allow the certbot to work, which is not ideal.
I have solved it by trusting my caddy certificate in Windows as a Trusted Root Certificate. I confirmed in Wireshark that the Jellyfin client app, even when I put in http:// as the URL, and even when I set up caddy to ONLY serve HTTP, Jellyfin still tries to access HTTPS instead. It seems like the Jellyfin client does not accept domains that are not TLS-supported. Unfortunately, I don't think it's possible to trust a custom certificate on my smart TV. So I'll have to stick to using the IP address there. Or, getting a proper certificate, but that would mean exposing my homelab IP in my subdomain DNS records, and opening a port to allow the certbot to work, which is not ideal.