2025-03-19, 02:46 PM
(This post was last modified: 2025-03-19, 02:47 PM by TheDreadPirate.)
And you have NOT made any changes to Jellyfin's network config?
For testing, can you bring down your wireguard interface and then restart Jellyfin? After it finishes starting, can you check the log to see if it found any interfaces? "Filtered interface addresses".
I don't THINK that should matter. Plenty of other people running wireguard, or other VPNs on top of wireguard, and Jellyfin would find both the physical interface and VPN interface.
Didn't see your post before submitting.
Are you able to access Jellyfin via the WG or LAN IP now? Is port 8096 open on the host?
For testing, can you bring down your wireguard interface and then restart Jellyfin? After it finishes starting, can you check the log to see if it found any interfaces? "Filtered interface addresses".
I don't THINK that should matter. Plenty of other people running wireguard, or other VPNs on top of wireguard, and Jellyfin would find both the physical interface and VPN interface.
Didn't see your post before submitting.
Are you able to access Jellyfin via the WG or LAN IP now? Is port 8096 open on the host?
Jellyfin 10.10.7 (Docker)
Ubuntu 24.04.2 LTS w/HWE
Intel i3 12100
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
4x WD Red Pro 6TB CMR in RAIDZ1
![[Image: GitHub%20Sponsors-grey?logo=github]](https://img.shields.io/badge/GitHub%20Sponsors-grey?logo=github)
Ubuntu 24.04.2 LTS w/HWE
Intel i3 12100
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
4x WD Red Pro 6TB CMR in RAIDZ1