this post was submitted on 30 Jul 2023
6 points (75.0% liked)

Selfhosted

40041 readers
873 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
 

Edit: I did some research on the Google Fiber reddit and it seems like broken port forwarding is a common issue with the provided hardware. Most say just BYO router. Sigh.


Tl;Dr: port forwarding isn't working after a network hardware upgrade, even after enabling it and rebooting all equipment, and without a firewall enabled.

I've been running a public-facing Jellyfin server on Ubuntu 22.04 for the past few months without too much trouble. Today I upgraded my networking equipment to a Google Fiber Network Box. I ended up having to set a new static IP address for my server device. I also had to switch from using the Google Home app to using the Google Fiber app or website to configure my network. Everything's working now except for port forwarding. The network settings give me the ability to forward ports, but port checkers keep telling me the ports I've opened are not open.

I've tried rebooting the server, router, and modem (and closing and reopening the ports) multiple times to no avail. UFW is installed on the server but it's inactive, and I don't have any other firewalls. I don't know what else could be blocking the ports.

I'm still sort of a newbie to self hosting, so maybe there's something I'm overlooking. But I've done several web searches and couldn't find any solutions I haven't already tried.

I did notice though that it seems every device on the network has the same public IP address. I don't know for certain that wasn't the case with my old setup, but it did seem strange. Again I'm not an expert on this stuff, so maybe it's nothing. I couldn't find anything in network settings that would let me change that either.

you are viewing a single comment's thread
view the rest of the comments
[–] funkajunk@lemm.ee 1 points 1 year ago* (last edited 1 year ago) (1 children)

Pretty sure that's just a legal formality to cover their butts. I've personally never heard of anyone having issues with it.

Edit: Also, that can't be true as the tunnelling is part of the zero-trust tools, which is made for accessing any kind of data.

[–] keenworld@midwest.social 1 points 1 year ago (1 children)

Fair enough. Seems to be working, so thanks again!

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

Awesome! Glad to help you on your self hosting journey 😁