Selfhosted

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.

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?

Gotta censor out those local IP's

Any particular reason you felt you needed to blur the last octet? Lol it's a private IP, outside your broadcast domain and NAT it's not unique.

Pretty much every home ISP router is going to hand out IP's on a class C zero subnet (192.168.0.0/24), if I was trying to fingerprint a network I'd start there anyways but you'd need the public IP for that to even matter.

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?

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.

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.

I hade the same issue recently when I tried jellyfin server on my windows PC. In my case the private/public Windows Firewall setting was not successful.

But what helped was to open the windows firewall settings and to allow jellyfin do access the privat/public network. You can access the setting by opening the "allowed apps" section in the windows firewall settings.

Maybe this helps some other folks in the future 😊

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

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]

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

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)

Most of the time it would be DNS 😆, glad you figured it out, I have been in your situation before. Just a heads up! Cloudflare TOS does not allow video streaming unless you are a paid customer, they could ban you if you stream a lot through CF. I got away with less than 4GB per month.

I had that issue, but don’t remember what I did to fix it lol

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

Are you able to see the server when you hit choose server? It should show up if your on your local network