Jellyfin app not accessing internet

[KptnAtsm]

Hello, for a bit of context, i'm running Truenas core on an old bulldozer CPU with a 1060 attached to it for transcoding. i have two 4TB drives in mirror mode.

i've run Jellyfin on this setup for multiple years, and for the last two or so Jellyfin stopped accessing the internet entirely. that means i'm not able to update metadata, install plugins, but i was still able to stream from it with my wireguard setup (set up inside the Router) for when i'm not home.

my solution for the last year or so was to just completely remake the jellyfin install, since internet access would work for a few days/weeks before cutting out. access works through Truenas having a fixed IP adress and jellyfin having its own port assigned. 

also when starting the app in truenas during the period when internet works, there are no errors in the "Related Kubernetes Events" window. but when it stops working it throws error 503 "connection refused". 

i do not have a certificate set up in jellyfin, if that has anything to do with it, and turning on IPv6 in truenas and jellyfin didn't do anything.

if you couldn't already tell, i'm an absolute noob and do not know jack about how networking works. if you want any dumps or logs, please ask.

i've attached the pod log and a log that i found in the jellyfin UI that seemed helpful.

[TheDreadPirate]

Do you have IPv6 setup on your TrueNAS host? Is IPv6 enabled in Jellyfin? It looks like it isn't able to resolve addresses.

Can you share the wireguard config? Minus the keys of course.

[KptnAtsm]

Do you have IPv6 setup on your TrueNAS host?  Is IPv6 enabled in Jellyfin?  It looks like it isn't able to resolve addresses.

Can you share the wireguard config?  Minus the keys of course.

i tried turning autoconfigure ipv6 on in the truenas network settings and enabling it in the jellyfin one. didn't do anything.

i think this is what you mean by config:
[interface]
PrivateKey = [REDACTED]
Address = 10.6.0.2/32
DNS = 10.6.0.1

[Peer]
PublicKey = [REDACTED]
AllowedIPs = 0.0.0.0/0
Endpoint = truenas1.ddns.net:51820
PersistentKeepalive = 25

the truenas1 bit is from when i had a hostname running, but i wasn't able to get https tto work so i stopped using that. the VPN connection works fine though.

[TheDreadPirate]

What is the goal of your wireguard setup? Is it only for Jellyfin? Or is it also for routing ALL internet traffic through it?

If the goal is to route JUST jellyfin through wireguard, or remote system access, you need to change "AllowedIPs" to 10.6.0.0/16. And remove the DNS line.

Since your TrueNAS host is already on the same LAN as the Wireguard server, having DNS set and "AllowedIPs" to 0.0.0.0 is a bit pointless.

[KptnAtsm]

What is the goal of your wireguard setup?  Is it only for Jellyfin?  Or is it also for routing ALL internet traffic through it?

If the goal is to route JUST jellyfin through wireguard, or remote system access, you need to change "AllowedIPs" to 10.6.0.0/16.  And remove the DNS line.

Since your TrueNAS host is already on the same LAN as the Wireguard server, having DNS set and "AllowedIPs" to 0.0.0.0 is a bit pointless.

i basically only use it to access the ip adress of the truenas server
aand the different ports it has. like my <app we don't talk about - TDP> app (which has perfectly fine internet access).

i'll change it, but that doesn't really solve the problem, right?

[TheDreadPirate]

Maybe. You can also try specifically setting Jellyfin to bind to a specific interface. Try experiment setting it to either the LAN interface or Wireguard interface.