Just switched from Plex… but might be going back lol. Http:/localhost :8097 works on my PC where my JF server is hosted. But I can’t connect on any other devices on the same network. What I have tried:

  • enabled private connections in Windows Defender. Then tried public too.

  • went to settings and binded address to 0.0.0.0

  • changed my port from 8096 to 8097 just to see if a different port would work.

  • Made an inbound rule for port 8097 in advanced firewall settings.

Not sure what’s going on here. On Plex it was easy to discover other devices on the same network. I have JF localhost connected to my Cloudflare Tunnel and I have access on all of my devices that way… but I rather just use my internal ip when I’m at home. Any help?

UPDATE: Literally been at this for hours, and as soon as I post the question on Lemmy…I figured it out. 🤦🏽‍♂️🤦🏽‍♂️🤦🏽‍♂️🤦🏽‍♂️

On Windows, I had to go to settings > networks and internet > and select private network. Don’t know how it was on public. Smh. I’ll leave this here just in case anyone else has the same issue.

  • @Decronym@lemmy.decronym.xyzBEnglish
    6•2 years ago

    Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

    Fewer Letters More Letters
    CF CloudFlare
    DNS Domain Name Service/System
    IP Internet Protocol
    NAT Network Address Translation

    4 acronyms in this thread; the most compressed thread commented on today has 13 acronyms.

    [Thread #144 for this sub, first seen 17th Sep 2023, 17:45] [FAQ] [Full list] [Contact] [Source code]

  • @deafboy@lemmy.worldEnglish
    10•2 years ago

    Back in the windows 2012 era, we knew every time a major windows update was pushed, because the same set of customers would always create a ticket, complaining about inaccessible RDP. Windows firewall is just opinionated like that.

  • @russjr08@outpost.zeuslink.netEnglish
    16•2 years ago

    I’m assuming both listed IPs are the same IP address? Those are internal IP addresses so you don’t need to censor them.

    Also, is this the Jellyfin app? If so, what happens if you bring up either addresses through a web browser?

  • @ChicoSuave@lemmy.worldEnglish
    96•2 years ago

    You don’t need to put in the effort to hide those IPs. An IP starting with 192.168 is a private network and virtually useless as any way to compromise your network - an outsider would need access to your network (via your modems public facing IP) and know the device access credentials to make any use of the IPs.

    That being said, it appears your input devices are unable to connect because they can’t be found. That means a mismatch in network details somewhere. Check the IP address and confirm it’s using the same subject; does the device connecting use the same 192.168.1.x network as the input/source device?

  • @phx@lemmy.worldEnglish
    3•2 years ago

    I’ve had windows do this to me randomly before, especially if it’s an interface that comes up a bit late. Be careful that it doesn’t change back on you

  • @lal309@lemmy.worldEnglish
    5•2 years ago

    Try through the browser first as suggested by someone else. If you are running the Docker container, check you port mappings.

  • @doubletandard@lemmy.worldEnglish
    4•2 years ago

    you may try this: 1/make sure jellyfin is actually running and there is no error in logs and firewall is not blocking inbound connections

    2/double check LAN IP/port jellyfin service running on and make sure the device you want to connecting to jellyfin can reach that IP (simple icmp ping is a good start)

  • @KairuByte@lemmy.dbzer0.comEnglish
    144•2 years ago

    I always chuckle when I see someone censoring an internal IP. It’s like intentionally not naming the room you’re in (kitchen, bathroom, bedroom, etc) when you’re on the phone so the person on the other end can’t find you on a globe.

    • @dutchkimble@lemy.lolEnglish
      49•2 years ago

      If we pull in a team effort we can all collectively try 1 to 255 for the last octet and download all the money from this man’s bank account and split it between us what say?

      • tj
        14•2 years ago

        I’m in. We just need 253 more people

          • @VonReposti@feddit.dkEnglish
            -4•2 years ago

            The 192.168.x.x IP range doesn’t allow for subnet masks greater than 255.255.255.0. How that’s enforced I can’t remember, but I’m 99% sure he isn’t using larger subnets.

            • @SoaringDE@feddit.deEnglish
              1•2 years ago

              The .x.x literally shows that you can fit a /16 (255.255.0.0) in there. 192.168.0.0 255.255.0.0

            • aardEnglish
              6•2 years ago

              The 192.168.x.x IP range doesn’t allow for subnet masks greater than 255.255.255.0

              This is nonsense. In that space you get a /16, and you can do with it whatever you want.

              • @VonReposti@feddit.dkEnglish
                -4•2 years ago

                No it’s not. 192.168.x.x is a reserved class C range which per specification is limited to 255.255.255.0

                • aardEnglish
                  2•2 years ago

                  Stop sprouting that kind of bullshit.

                  Class based networking has been obsolete for 3 decades now - and RfC 1519 was quickly implemented, so pretty much by the mid 90s any device looking up network masks by classes could be considered some broken legacy device.

                  RfC 1918 - which allocates the private IP ranges - came 2.5 years after the introduction of CIDR, specifies the networks in bit notation, and only references what the equivalent networks were in class notation as reference for people who have been asleep for a few years.

  • @Appoxo@lemmy.dbzer0.comEnglish
    8•2 years ago

    Regarding your edit and public vs private network:
    Windows really likes to do that.

    Tbh: As soon as I read it, I was assuming it was Windows Firewall related.