2024-01-11, 07:46 PM
Is UFW active? If you add a rule, but UFW isn't active, it won't change anything.
sudo ufw status
sudo ufw status
2024-01-11, 07:46 PM
Is UFW active? If you add a rule, but UFW isn't active, it won't change anything.
sudo ufw status
2024-02-05, 05:52 AM
I was running into this session with my installation (proxmox -> TrueNas). I had installed Jellyfin earlier and messed it up, so I trashed it and started again, however my browser didn't know it was a new session I think. Clearing my browser cache/cookies fixed it. So that's worth a try for anyone else that runs into this.
2024-08-16, 06:59 PM
(This post was last modified: 2024-08-16, 07:00 PM by SenileOtaku. Edited 1 time in total.)
Just today this started happening on my Jellyfin server.
Jellyfin 1.9.8 Fedora 40 (baremetal, no containers or VM) Failing from two machines (also running Fedora 40) with Firefox 129, Chromium 127.0.6533.99, and jellyfin-media-player 1.10.0-1. Also failing on a Mint 22.04 system (Firefox 129) Even trying from the Falkon browser on Haiku, connecting to http://192.168.3.15:8096, it shows the "Manual Login" option (on the "Please Sign In" screen), but logging in with that just drops me right back to the Please Sign In screen that only shows "Manual Login" and "Forgot Password" I've checked the ports on the media server: jelabarre@5040mediaserver:~$ sudo ss -tulpn | grep jellyfin udp UNCONN 0 0 192.168.3.15:48054 0.0.0.0:* users:(("jellyfin",pid=1036,fd=482)) udp UNCONN 0 0 0.0.0.0:7359 0.0.0.0:* users:(("jellyfin",pid=1036,fd=485)) udp UNCONN 0 0 239.255.255.250:1900 0.0.0.0:* users:(("jellyfin",pid=1036,fd=481)) tcp LISTEN 0 512 *:8096 *:* users:(("jellyfin",pid=1036,fd=514)) jelabarre@5040mediaserver:~$ sudo lsof -i -P -n | grep jellyfin jellyfin 1036 jellyfin 481u IPv4 10186 0t0 UDP 239.255.255.250:1900 jellyfin 1036 jellyfin 482u IPv4 10187 0t0 UDP 192.168.3.15:48054 jellyfin 1036 jellyfin 485u IPv4 10188 0t0 UDP *:7359 jellyfin 1036 jellyfin 514u IPv6 10193 0t0 TCP *:8096 (LISTEN)
2024-08-16, 07:16 PM
Can you share your full jellyfin log via pastebin?
2024-10-31, 05:14 AM
sadly I get the same thing.
I install jellyfin via the package manager in synology I went to the control panel shared folder edit permissions and added read/write to sc-jellyfin and the sc-ffmpeg7 user I load the jellyfi url and when I click "connect" i just get We're unable to connect to the selected server right now. Please ensure it is running and try again. thats as far as i got and i give up. i remember in DSM6 i installed jellyfin and it "just worked" on browser as well as the fireTV client. now... i just dont know how to further debug this issue
2024-10-31, 12:35 PM
If you connected to a different jellyfin instance at the same address, you may need to clear your cache or Ctrl+f5 to force a full refresh.
2024-11-02, 07:17 AM
I think I found the issue as I had a similar experience with cloudflare using proxming LXC and truenas media server. I tried everything and couldnt get it fixed then I found it was simply sign into jellyfin locally with an admin, go to dashboard, settings, networking and allow remote connections.
2024-12-26, 11:50 PM
I had this issue too, I just clicked on the server that was showing an issue, clicked the top right then delete. Jellyfin then went through the initial pages and installed right away.
2025-01-07, 07:15 PM
Hi guys,
I am running TrueNas and upgraded my Jellyfin Community Instance to the newest stable version. Unfortunately I did not backup Jellyfin configuration and I ended up with the same screen most guys here posted. I selected the server and got the error message. I managed to clear the cache and I can connect again, BUT the Jellyfin instance cannot connect to the internet. It can not retrieve any metadata & can not load new movies from my SMB share. Since the Jellyfin Instance shell has not much tools, I tried to download vim, nano or other packages for editing config files to fix this issue. But also there no internet connection. I tried different things I found in the forums and online, but seem not to solve the issue - The server is running on the right port - HTTPS is NOT enforced - IPv6 is disabled - address binds to 0.0.0.0 - multiple restarts of the instance in between I cannot figure out where the issue is comming from. Anyone has a solution or a guess?
2025-01-07, 11:34 PM
Can you share your jellyfin log via pastebin?
|
|
|