+- 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: Setting up remote access (/t-setting-up-remote-access--6342)
Pages:
1
2
RE: Setting up remote access - three2do1 - 2024-06-05
No, sorry only on local wifi
Apologies if my lack of knowledge is causing confusion
I havent got anything to work remotely and I am trying to use jellyfin android app or finamp remotely without success
I am using jellyfin 10.9.4
RE: Setting up remote access - TheDreadPirate - 2024-06-05
What address are you typing into Jellyfin when trying to access it remotely? Your public IP (don't share that here)? If you are typing in the private IP (probably 192.168.X.X) that won't work.
RE: Setting up remote access - three2do1 - 2024-06-05
I dont think I have a public IP so that is probably what I need to obtain
Is this related to DNS?
RE: Setting up remote access - TheDreadPirate - 2024-06-05
You do. Its how you access the Internet. You can go to your router's main page to get your public IP or use this website.
https://whatismyipaddress.com/
RE: Setting up remote access - three2do1 - 2024-06-05
ah. Thankyou this is news to me
so just to be clear, do I need to use my public IP only when remotely accessing or can I use all the time?
I will try this and let you know
It almost worked..
I managed to get into my front page but couldn't click anything and now I cant use this IP at all
RE: Setting up remote access - three2do1 - 2024-06-05
EDIT
Wierd. Now it is working... Not sure why the hiccups but I will take this for now!!
Thankyou
I do have another question if you have the time
Is this a secure form of connection or is it vulnerable to hacks? some things I've read seem a little concerning
RE: Setting up remote access - TheDreadPirate - 2024-06-05
Hacks are extremely unlikely for us plebs. But there are a lot of things you can do to secure your setup. The problem is the learning curve.
The one thing I think you should do is go to DuckDNS and get a dynamic DNS address. You then install the DuckDNS client on your Jellyfin server and instead of using your IP you will use this DuckDNS address and the client you installed will automatically update the address if your public IP changes (which does happen on residential connections).
A lot of routers have a feature called "NAT loopback" or "NAT Hairpin". With that enabled your router will automatically keep traffic local if use your DuckDNS/public IP address while at home. Without it, when you use your public IP or DuckDNS address while at home, the traffic will go out to the Internet only to come right back. With NAT Loopback you avoid this and also don't have to switch between your public IP and local IP.
RE: Setting up remote access - three2do1 - 2024-06-05
Thanks so much. This was a pain for a long time for me!! Finally up and running thanks to you 👌
RE: Setting up remote access - pcm - 2024-06-06
There's a couple of things that you might want to look into and find out ...Â
1. do you have a firewall on the router ? if you do, are you sure you have a rule in place that allows TCP and UDP packets to flow out of port 8096 ?Â
2. does your ISP block not-well-known ports ? if they do, can you ask them to open it for you ?
It might be worth it for you to change the port on your jellyfin-web-server to port 80 instead of 8096 and then setup a port-forward for port-80 on your router that goes to your server. This would be a simple enough thing to do and almost all firewalls and ISP allow traffic thru port-80 by-default without any additional hassle.
EDIT: Just realized that the issue is solved. And there is no way for me to delete my post... Oops