2024-12-07, 09:26 PM
https with just an ip locally is never going to work. Try with the http://{ip}:8096 if you have configured that port to be used.
> I used a powershell command to generate a self-signed token for HTTPS
We strongly recommend against using self signed certificates. Only web has some basic support for that and all our clients we do not expect to work with self signed certificates. Try removing the self signed certificate and try again using http.
> I have also connected the http port to my cloudflare tunnel
We also strongly suggest against using CloudFlare's tunnel feature with Jellyfin as it is violating their ToS and they can terminate your account.
In basic you should try the following:
1) Stop using self signed certificates
2) Make sure the firewall is not the problem on the server
3) Connect to it with the configured Docker HTTP port. Not HTTPS.
> I used a powershell command to generate a self-signed token for HTTPS
We strongly recommend against using self signed certificates. Only web has some basic support for that and all our clients we do not expect to work with self signed certificates. Try removing the self signed certificate and try again using http.
> I have also connected the http port to my cloudflare tunnel
We also strongly suggest against using CloudFlare's tunnel feature with Jellyfin as it is violating their ToS and they can terminate your account.
In basic you should try the following:
1) Stop using self signed certificates
2) Make sure the firewall is not the problem on the server
3) Connect to it with the configured Docker HTTP port. Not HTTPS.
Not your average hoarder.
Storage: 8x18TB RAIDz2 + 2x16TB Mirror + 512GB NVMe OS drive
CPU: Ryzen 1700
Cooler: Scythe Fuma 2
Motherboard: Gigabyte AORUS B450 PRO
RAM: DDR4; 2x8GB + 2x16GB
Storage: 8x18TB RAIDz2 + 2x16TB Mirror + 512GB NVMe OS drive
CPU: Ryzen 1700
Cooler: Scythe Fuma 2
Motherboard: Gigabyte AORUS B450 PRO
RAM: DDR4; 2x8GB + 2x16GB