+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+---- Forum: Networking & Access (https://forum.jellyfin.org/f-networking-access)
+---- Thread: SOLVED: Jellyfin media player connection on same device (/t-solved-jellyfin-media-player-connection-on-same-device)
Jellyfin media player connection on same device - Daxel - 2024-01-04
I can't log in via jellyfin media player on the same PC where I installed my media server.
honestly, looking around I didn't find much, and I don't understand the reason for this, given that I set everything that could be done, such as certificates or Upnp for remote access.
some idea?
RE: Jellyfin media player connection on same device - TheDreadPirate - 2024-01-04
What address are you typing into JMP?
RE: Jellyfin media player connection on same device - Daxel - 2024-01-04
I'm using a "No-ip" hostname so I don't have to always enter the ip
RE: Jellyfin media player connection on same device - tmsrxzar - 2024-01-04
if "on same device" means the device where jellyfin server is installed; check your network settings for bind addresses, it should not need any weird internet addresses as the local lan address or localhost should work - if you allow jellyfin to listen to localhost
RE: Jellyfin media player connection on same device - TheDreadPirate - 2024-01-04
(2024-01-04, 10:36 PM)Daxel Wrote: I'm using a "No-ip" hostname so I don't have to always enter the ip
Is your DDNS using your LAN IP or your WAN IP? If the latter, do you have NAT loopback setup?
RE: Jellyfin media player connection on same device - Daxel - 2024-01-05
Lan ip*
nat loopback?
RE: Jellyfin media player connection on same device - TheDreadPirate - 2024-01-05
AFAIK, DDNS will not work with LAN IPs the way you think it will. Only WAN IPs.
NAT Loopback/hairpin is a router function that some routers have where it will keep traffic local if a DNS lookup resolves to itself. This allows you to use a DDNS or domain pointing to your public IP. But requires that a port forwarding rule be setup to function.
Instead of using DDNS, why not just use your server's local hostname. Most routers will support that.