It’s a bit off-topic but is it possible to resolve in my lan jellyfin.example.com to a internal ip instead of vps and outside my lan use the same domain but use pangolin wireguard to connect to the resource?
Yes you can do that. Please open a seperate thread so that we can discuss there and don’t clutter here. @Floordb
Has anyone else had issues with their WireGuard sites with newer versions of Pangolin?
Ever since updating to 1.18.0, my WireGuard site to tunnel Jellyfin and some other apps has started having intermittent issues. The site itself isn’t connecting right away, and resources proxied through the site take a while to be publicly accessible.
What’s strange is that Pangolin shows that the WireGuard site is now connected for me, but I can’t access some of the resources from that site, such as Jellyfin. I try to access my Jellyfin resource but just get “no available server”. Connecting via my local network, however, works just fine.
Any ideas of what could be happening? Please let me know. Thanks!
I just fixed it, but the solution was very strange. As an example, I changed the resource settings for Jellyfin to proxy from http://(WIREGUARD-IP):8096 to https://(WIREGUARD-IP):8096 and saved the target settings in the GUI. Then I changed it back from https://(WIREGUARD-IP):8096 to http://(WIREGUARD-IP):8096 and now it works.
I have no clue why…