Selfhosted

40359 readers

347 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Can't connect to devices on the same network on Jellyfin (lemmy.ml)

submitted 1 year ago* (last edited 1 year ago) by techgearwhips@lemmy.ml to c/selfhosted@lemmy.world

4 comments fedilink hide all child comments

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.

top 4 comments

sorted by: hot top controversial new old

[–] Swarfega@lemm.ee 1 points 1 year ago

Gotta censor out those local IP's

[–] KairuByte@lemmy.dbzer0.com 1 points 1 year 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.

[–] ChicoSuave@lemmy.world 1 points 1 year ago* (last edited 1 year ago) (1 children)

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?

[–] Steveanonymous@lemmy.world 1 points 1 year ago

No I have his ip and now I will hax!!!