this post was submitted on 17 Sep 2023
143 points (93.9% liked)

Selfhosted

40357 readers
391 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

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

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

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
[–] c0mbatbag3l 3 points 1 year ago (1 children)

I suppose I'm being a little harsh, I just deal in networks and it made me pause but I forget not everyone knows what I know. I apologize for being rude.

Essentially your internal private network operates on three ranges of numbers depending on your specific needs. Homes usually never need more than a couple dozen but even the most advanced home network probably only uses half a dozen subnets at most and need fewer than 253 devices per, so usually you get 192.168.0.0-192.168.255.255/24 because it's more than enough. The "/24" denotes (out of 32) where the subnet ends, essentially how we are dividing up the allotted space in the IP scheme we are given. The "Class C" range (mentioned above) has an available 65,000+ addresses. Usually more than enough for any way you want to slice it up. Mostly you'll just see people sling /24's around because it's an even interval of 1 in the last octet which makes things simpler.

People who build more robust "networks" (in the commercial sense) at their houses will usually operate a few different ones, some for internal and others set aside in "DMZ" zones for outward facing servers. Such as gaming servers or self hosting jellyfin!

[–] [email protected] 2 points 1 year ago (1 children)

I read this and got all the way lost in the sauce. Is this English? Lol but for real, I appreciate the info.

[–] c0mbatbag3l 2 points 1 year ago

No problem, networks are an interesting development in computer technology and plenty of people (even those with computer knowledge) have never seen how complex they can get.