Issues Connecting to Server

[stucklucky]

I have been having issues connecting two clients (LG TV App and android app) to my server (Debian Linux) within my local network. I have uninstalled and installed all clients and server and still having issues. When I access the web client on the same computer that Jellyfin server is installed on everything works fine. It is only an issues when trying to connect from other devices. There will be times when the clients do connect but it seems very random and the problem will start up again very quickly. 

When I try to connect to the server on android app I am greeted by a screen where I can type in the host. I make sure to type my IP in this format "http://MY_IP:8096". When I do I get an error that says:

Tried 2 candidates for input, without success.

Unable to reach server:

• https://MY_IP:8096
  
• http://MY_IP:8096
  

Then I tap on "Choose server" but when I do there is nothing coming up under Available Servers. Same thing happening on LG TV WebOS app installed from the content store. I open up a terminal and type 

Code:

sudo service jellyfin status

The service is active. At this point I am not sure what to do. I know there are logs in the dashboard but to be honest I am not sure what parts of the log are useful or what I should be looking for.  With some guidance I am able to provide logs necessary. Here is some relevant information:

• Jellyfin Server version 10.8.13.0
  
• Installed using debian repository and instructions outlined in the official downloads page
  
• Running Debian 12 GNU/Linux
  
• Jellyfin clients installed from the respective device's content store
  

I used to run Jellyfin a while back and it was amazing using the same linux distro and installation methods. Now, I am not really sure why it is giving me such a hard time. I have seen other people having similar problem as mine on this forum but either they don't have a solution (it just started working with no known solution) and/or they are running Jellyfin on Windows machines. Anyway, thanks in advance.

[TheDreadPirate]

Did you open a port on your firewall?

Code:

sudo ufw enable (if not enabled already)
sudo ufw allow 8096

[stucklucky]

I ran the commands you provided reset but still having issues. Getting an error saying either "Request timed out" or "There was an error. Are you sure you are connecting to a Jellyfin Server?" Tried it on LG WebOS app.

[TheDreadPirate]

Are you trying to "auto discover" your jellyfin server? Have you tried typing in http://yourJFIP:8096

[stucklucky]

I usually try both. First I will try to type the IP and usually that doesn't work. After trying that I will try the "auto discover" but it will just load and load and not discover my jellyfin server even though it is active. The strange thing is that sometimes at very random times on my tv and android phone the client will sometimes manage to discover the server and detect it. When I select the server it is hit or miss whether it will actually connect or not. Even if it does connect it will not last long and the issue will arise again.

[TheDreadPirate]

Can you share your Jellyfin logs with us? Upload to sourcebin and link back here.

[stucklucky]

Hey just attempting to get jellyfin working again. I uploaded the logs to sourcebin at this link https://sourceb.in/FV5kfilP2f. Thanks for your patience.

[TheDreadPirate]

Can you share this file with us via sourcebin?

/etc/jellyfin/network.xml

I am seeing these messages that makes me think something is off, but I don't know what.

Code:

[2024-02-06 13:40:47.377 -07:00] [ERR] No interfaces information available. Resolving DNS name.

[tmsrxzar]

Can you share this file with us via sourcebin?

/etc/jellyfin/network.xml

I am seeing these messages that makes me think something is off, but I don't know what.

Code:

[2024-02-06 13:40:47.377 -07:00] [ERR] No interfaces information available. Resolving DNS name.

slightly more interesting

Defined LAN addresses : "[10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]"

but there was a request from

[INF] WS "192.168.1.173" request


which looks to me like the LAN is actually on 192.168.1.x and not the defined 192.168.0.x

what's your thought on that one?

[TheDreadPirate]

slightly more interesting

Defined LAN addresses : "[10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]"

but there was a request from

[INF] WS "192.168.1.173" request


which looks to me like the LAN is actually on 192.168.1.x and not the defined 192.168.0.x

what's your thought on that one?

Because the subnet mask is /16 that will cover any address after 192.168.   192.168.0.X through 192.168.255.X.