• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support Troubleshooting SOLVED: Unable to connect via IP address. Only connects via loopback.

     
    • 0 Vote(s) - 0 Average

    SOLVED: Unable to connect via IP address. Only connects via loopback.

    Unable to connect via IP address. Only connects via loopback.
    jayjay
    Offline

    Junior Member

    Posts: 3
    Threads: 1
    Joined: 2023 Aug
    Reputation: 0
    Country:New Zealand
    #1
    2023-08-28, 09:07 PM
    Hi, I have an HP Thin Client T530 running Ubuntu 22.04.3 LTS.

    Installed and running Jellyfin. Device IP address & port 192.168.1.33:9222.

    Connected via the IP address locally and configured Jellyfin. Connected via Jellyfin app and Swiftfin app. Confirmed able to connect via tailscale using tailscale IP address and same port.

    Unfortunately I can now only connect via the loopback address locally on Ubuntu - 127.0.0.1:9222. I can no longer connect via the IP address 192.168.1.33:9222 from Ubuntu or any other device, locally or via tailscale with the 100.x.

    Jellyfin web

    Local HTTP port number:
    9222

    Bind to local network address:
    127.0.0.1/8, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, 100.0.0.0/8, 192.168.1.33/24

    I added the last entry just now but still no luck.
    rebooted Ubuntu, no luck.
    stopped and started Jellyfin service, no luck.

    sudo ufw status
    Status: inactive

    sudo systemctl status jellyfin
    jellyfin.service - Jellyfin Media Server
    Loaded: loaded (/lib/systemd/system/jellyfin.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/jellyfin.service.d
    └─jellyfin.service.conf
    Active: active (running) since Sun 2023-08-27 23:33:28 NZST; 1 day 8h ago
    Main PID: 1071 (jellyfin)
    Tasks: 21 (limit: 8162)
    Memory: 635.6M
    CPU: 4min 51.907s
    CGroup: /system.slice/jellyfin.service
    └─1071 /usr/bin/jellyfin --webdir=/usr/share/jellyfin/web --restartpath=/usr/lib/jellyfin/restart.sh --ffmpeg=/usr/lib/jellyfin-ffmpe>
    Aug 29 08:01:10 MediaServer jellyfin[1071]: [08:01:10] [INF] Using LAN addresses: [10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]
    Aug 29 08:02:35 MediaServer jellyfin[1071]: [08:02:35] [INF] Defined LAN addresses : [10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]
    Aug 29 08:02:35 MediaServer jellyfin[1071]: [08:02:35] [INF] Defined LAN exclusions : []
    Aug 29 08:02:35 MediaServer jellyfin[1071]: [08:02:35] [INF] Using LAN addresses: [10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]
    Aug 29 08:04:17 MediaServer jellyfin[1071]: [08:04:17] [INF] Defined LAN addresses : [10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]
    Aug 29 08:04:17 MediaServer jellyfin[1071]: [08:04:17] [INF] Defined LAN exclusions : []
    Aug 29 08:04:17 MediaServer jellyfin[1071]: [08:04:17] [INF] Using LAN addresses: [10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]
    Aug 29 08:06:56 MediaServer jellyfin[1071]: [08:06:56] [INF] Defined LAN addresses : [10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]
    Aug 29 08:06:56 MediaServer jellyfin[1071]: [08:06:56] [INF] Defined LAN exclusions : []
    Aug 29 08:06:56 MediaServer jellyfin[1071]: [08:06:56] [INF] Using LAN addresses: [10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]

    sudo ss -tulwn | grep LISTEN
    tcp  LISTEN 0      4096                              127.0.0.53%lo:53        0.0.0.0:*         
    tcp  LISTEN 0      4096                            100.107.252.135:50657      0.0.0.0:*         
    tcp  LISTEN 0      10                                      0.0.0.0:36614      0.0.0.0:*         
    tcp  LISTEN 0      128                                    127.0.0.1:631        0.0.0.0:*         
    tcp  LISTEN 0      10                                      0.0.0.0:7070      0.0.0.0:*         
    tcp  LISTEN 0      512                                    127.0.0.1:9222      0.0.0.0:*         
    tcp  LISTEN 0      128                                        [::1]:631          [::]:*         
    tcp  LISTEN 0      4096  [xxxxxxxxxxxxxxxxxxxxxxxxxx]:50657        [::]:*

    ip a
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
    valid_lft forever preferred_lft forever
    2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether xxxxxxxx brd xxxxxxxx
    inet 192.168.1.33/24 brd 192.168.1.255 scope global dynamic noprefixroute enp1s0
    valid_lft 48814sec preferred_lft 48814sec

    Ubuntu Firefox
    Unable to connect
    Firefox can’t establish a connection to the server at 192.168.1.33:9222.

    If I connect using a different computer on the LAN, I get the following error.
    This site can’t be reached192.168.1.33 refused to connect.
    Try:
    Checking the connection
    Checking the proxy and the firewall
    ERR_CONNECTION_REFUSED

    I'm unsure where I can find the logs for this. Can anyone advise where the logs can be located.

    Any suggestions on what I can do to access Jellyfin again via the IP address and why it has stopped responding to it.
    Go to solution
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #2
    2023-08-28, 09:17 PM
    You should see 0.0.0.0:9222 in your ss command. Meaning it binds to all available addresses. It is only binding to the loopback. Can you give us your full jellyfin log? And your network.xml.

    /etc/jellyfin/network.xml
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    jayjay
    Offline

    Junior Member

    Posts: 3
    Threads: 1
    Joined: 2023 Aug
    Reputation: 0
    Country:New Zealand
    #3
    2023-08-28, 10:17 PM (This post was last modified: 2023-08-28, 10:58 PM by jayjay. Edited 3 times in total.)
    (2023-08-28, 09:17 PM)TheDreadPirate Wrote: You should see 0.0.0.0:9222 in your ss command.  Meaning it binds to all available addresses.  It is only binding to the loopback.  Can you give us your full jellyfin log?  And your network.xml.

    /etc/jellyfin/network.xml

    Thanks, added 0.0.0.0:9222, restarted jellyfin service, still unable to connect via IP address. I haven't rebooted the Thin Client, wondering if that is necessary?

    Log file attached.

    Thanks for your help.


    EDIT: Jellyfin permissions seem to be root and access file only. From my previous troubleshooting for getting the external storage working, I learnt that the others access need tob e create and delete files. Would this be the case here as well? Image attached

    EDIT2: Emailed you the log.


    Attached Files Thumbnail(s)
       
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #4
    2023-08-29, 12:15 AM (This post was last modified: 2023-08-29, 12:20 AM by TheDreadPirate. Edited 2 times in total.)
    You shouldn't add 0.0.0.0 as a binding address. "Bind to local address" should be blank unless you have a specific reason for specifying something else. 0.0.0.0:9222 in ss just indicates that it is listening on that port on all interfaces.

    Otherwise your log doesn't show anything obviously wrong.

    Also, just because ufw is not active doesn't mean that iptables is off. ufw is just a tool to simplify iptables. It is probably blocking your connections, which is the default behavior (except localhost).

    Code:
    sudo ufw enable
    sudo ufw allow 9222
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    jayjay
    Offline

    Junior Member

    Posts: 3
    Threads: 1
    Joined: 2023 Aug
    Reputation: 0
    Country:New Zealand
    #5
    2023-08-29, 03:43 AM
    (2023-08-28, 10:17 PM)jayjay Wrote:
    (2023-08-28, 09:17 PM)TheDreadPirate Wrote: You should see 0.0.0.0:9222 in your ss command.  Meaning it binds to all available addresses.  It is only binding to the loopback.  Can you give us your full jellyfin log?  And your network.xml.

    /etc/jellyfin/network.xml

    Thanks, added 0.0.0.0:9222, restarted jellyfin service, still unable to connect via IP address. I haven't rebooted the Thin Client, wondering if that is necessary?

    Log file attached.

    Thanks for your help.


    EDIT: Jellyfin permissions seem to be root and access file only. From my previous troubleshooting for getting the external storage working, I learnt that the others access need tob e create and delete files. Would this be the case here as well? Image attached

    EDIT2: Emailed you the log.

    Thanks. Removing all binding ip addresses fixed the issue. Thanks for your help.
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode