|
8 hours ago
(This post was last modified: 8 hours ago by aeternalis. Edited 1 time in total.)
Attempting to just go to https://jellyfin.domain.com results in that SSL_ERROR_INTERNAL_ERROR_ALERT problem on a browser. I have to specify http and port 8096. Https doesn't work at all on any client. I know there are https options in jellyfin itself, but unless I read the tutorials wrong, it seems caddy and dns should have provided that functionality.
7 hours ago
When you go to the https URL, can you inspect the certificate the browser received and check that it is valid and that it includes your subdomain and not just domain.tld?
Jellyfin 10.10.3 (Docker)
Ubuntu 24.04 LTS Intel i3 12100 Intel Arc A380 OS drive - SK Hynix P41 1TB Storage 3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library) ![[Image: GitHub%20Sponsors-grey?logo=github]](https://img.shields.io/badge/GitHub%20Sponsors-grey?logo=github){kind=icon}
5 hours ago
From what I gather, there is no certificate being supplied. I have always use HTTPS enabled in cloudflare. I also have edge certificates setup (at least to my knowledge, I have them setup properly).
5 hours ago
(This post was last modified: 5 hours ago by TheDreadPirate. Edited 1 time in total.)
Do you have CF set to "Proxied" or is it "DNS Only". If it is DNS only, CF shouldn't be a factor at all. Caddy should be making the request automatically to Let's Encrypt for certificates and serving those.
Jellyfin 10.10.3 (Docker)
Ubuntu 24.04 LTS Intel i3 12100 Intel Arc A380 OS drive - SK Hynix P41 1TB Storage 3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)
2 hours ago
My DNS is setup as in the screenshot below. The "MX" and "TXT" ones were ones that CF autopopulated.
The A record is for the domain itself (@ for CF) and points to my JF sever's public IP and the CNAME is for jellyfin.domain.com, with the target set to the domain itself. https://imgur.com/a/hwVUmyX |
|
|
|
|
