|
2024-02-16, 07:15 PM
I ensured I'm running the latest update to Jellyfin and have disabled my piHole as my DNS. Remote connection is allowed in my Jellyfin servers.
I also disabled Windows Firewall on the server to ensure it wasn't causing the issue.
2024-02-16, 07:23 PM
Can you share your jellyfin server log with us via sourcebin? Restart the server and give us the latest log. The startup logs contain a lot of info we would need to troubleshoot this.
C:\ProgramData\Jellyfin\Server\log
Jellyfin 10.10.1 (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}
2024-02-16, 07:36 PM
I'm having trouble with Sourcebin (at work and trying to do it remotely) but I did upload the log itself to my proton drive if that is any help. If not I will get it on Sourcebin when I get home in a few hours.
https://drive.proton.me/urls/774QJNSNGW#1sLCDkiaB24s
> Error creating port map on local port 8096 to public port 8096 with device "192.168.1.1:56688".
Probably unrelated. But it looks to me that your Jellyfin instance isn't able to automatically map the port. Perhaps you should turn off automatic port mapping if your router doesn't support it.
2024-02-16, 09:51 PM
Manually port forward instead of automatic port mapping.
Are you running a VPN client on this server?
Jellyfin 10.10.1 (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)
2024-02-17, 02:07 AM
Running a VPN with split-tunneling at times, but it's currently not running.
I disabled auto port mapping, but I still have the same issue.
2024-02-17, 02:19 AM
Fixed. Router pushed an update that messed with my assigned IP addresses.
|
|
|
|
|
