Selfhosted

37774 readers

1138 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:

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

143

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

submitted 9 months ago* (last edited 9 months ago) by [email protected] to c/selfhosted

58 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.

you are viewing a single comment's thread
view the rest of the comments

[–] ProjectPatatoe 1 points 9 months ago (1 children)

I know it because of Half-Life 1. If your tried to connect to a network game as lan while giving a non-class c ip, it specifically mentioned class c.

[–] [email protected] 0 points 9 months ago

Interesting, I never encountered that - though that also fits the "2.5 decades" timeframe.

It still shows the author of the error message has no idea about networking: even if we assume network classes apply to RfC 1918 addresses (which they don't) the majority of those addresses are class A or class B networks.

And looking at it the other way round (using "class C" synonymous with "private addresses) doesn't work - the majority of addresses in class C space are public addresses.