Can't connect using local IP outside of the local machine

[stickybug]

Hi, I have seen lots of posts about connection issues but none seem to fix mine.

I started a new Jellyfin server on an Ubuntu machine moving away from my old Windows machine.
I have set up Jellyfin and using the web intnterface on the 192.168.0 address.
But if I try to connect to the same address on my windows pc or iphone using the jellyfin app it cannot connect.
I have also installed Tailscale as I used it on my last machine to connect from outside the network.
Using Tailscale works with my other devices using the Tailscale ip but I would like to connect to the local ip while on my network.

All devices are on the same subnet.Not sure why the windows jellyfin server worked straight away with no issues and my new ubuntu one doesn't.
I have also used "sudo ufw allow 8096" and "sudo ufw enable" to make sure it's on.

I have also checked the tickbox to allow remote connections on Jellyfin

Any ideas on whats stopping this from getting to my other decives?

[jravin]

@stickybug

From what i am reading, you installed Ubuntu ... figure version 25.x ..., and logged into the GUI for that machine to install and setup Jellyfin.  Everything worked like a champ while on the local box.

Start with verifying the service is running:

Code:

/usr/bin/sudo ss -tulpn | /usr/bin/grep 8096

You should see something like:

tcp  LISTEN 0      512                *:8096            *:*    users:(("jellyfin",pid=1045,fd=443))

FWIW:

• *:8096 = accessible on all interfaces.
  
• 0.0.0.0:8096 = accessible on all interfaces.
  
• 127.0.0.1:8096 = only local access (you will need to fix the service config to bind to all interfaces)
  

Next you can check the service bind address.  I did not have great luck when testing this on my debian computer, but if you are familiar with the commands you should get the idea of what to look for, where "<LocalAddress>" is your local IP address ... either 192.168.0.x or maybe try 127.0.0.1:

Code:

/usr/bin/cat /var/lib/jellyfin/config/system.xml | grep -i <LocalAddress>

Another way to skin this:

Code:

/usr/bin/sudo /usr/bin/systemctl cat jellyfin.service

If you make any changes, be sure to restart the service:

Code:

/usr/bin/sudo /usr/bin/systemctl restart jellyfin

Make sure you know what you think you know:

Code:

/usr/bin/ip addr show

Here, find the network device that is actually plugged into the network you are trying to use.  (Side note here: I have on at least one occasion spent way too much time trying to troubleshoot a network issue only to discover I had the cable plugged into the wrong port(s).  So, maybe double check this as well.)

You are looking for something like:

inet 192.168.0.x/24

For testing purposes, disable the firewall:

Code:

/usr/bin/sudo /usr/sbin/ufw status
/usr/bin/sudo /usr/sbin/ufw disable
/usr/bin/sudo /usr/sbin/ufw status

Now, from another machine on the network try:

Code:

/usr/bin/curl http://192.168.0.x:8096

AND/OR try reaching your Jellyfin server from another machine's browser.

• If it works with firewall disabled, the issue is firewall rules.
  
• If it still doesn’t work, check service bind address again, or network issues.  (Maybe also read through this without doing the commands to perhaps spawn any ideas ... like a bad cable.)
  

Moving forward, as in it works, re-enable the firewall:

Code:

/usr/bin/sudo /usr/sbin/ufw enable

Then allow port 8096:

Code:

/usr/bin/sudo /usr/sbin/ufw allow 8096/tcp

Check the rule:

Code:

/usr/bin/sudo /usr/sbin/ufw status numbered

You are hoping to see something like:

[ 1] 8096/tcp                  ALLOW      Anywhere
[ 2] 8096/tcp (v6)              ALLOW      Anywhere (v6)

Now retry the get test:

Code:

curl http://192.168.0.x:8096

AND/OR from your browser.

If it fails, feel free to pour yourself a couple sips of whiskey before proceeding (assuming you are of legal age, et cetera)...

Then, check some logs:

Code:

/usr/bin/sudo /usr/bin/journalctl -u jellyfin --no-pager | /usr/bin/tail -n 50

From your client computer, ping the server:

Code:

/usr/bin/ping 192.168.0.x

If Windows:

Code:

c:\windows\system32\ping.exe 192.168.0.x

Also, here is where you check any routers, switches, gateways, or any network devices to ensure they are not the issue.  How to do this is beyond the scope of my response, but a hint is google.com .

If by this point you are still having an issue, maybe consider changing your cables out, trying different network adapters, different ports, different network devices, and so forth.

[stickybug]

@jravin

Thank you so much for the help.
When I saw this bit "inet 192.168.0.x/24" of your guide mine came back with /32.
I messed up the subnet haha.
Changed it to /24 and is up and working now. Just need to sort the AppleTV out for some reason it's not connecting yet my phone does.
Not a massive issue at the moment as the rest is working.

Thank you again. Should have realised I set something up wrong.