this post was submitted on 06 Sep 2023
4 points (75.0% liked)

Selfhosted

40218 readers
1259 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
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
HybridSarcasm@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
4
Port 80 inexplicably working again (lemmy.crimedad.work)
submitted 1 year ago by CrimeDad@lemmy.crimedad.work to c/selfhosted@lemmy.world
8 comments fedilink hide all child comments
 

On August 21, my Yunohost server, which I keep in my house, started warning we that port 80 was inaccessible from the Internet. None of my sites use port 80, so everything kept working, but I was concerned because I knew that my Let's Encrypt certificate would fail to automatically renew if I didn't fix the problem. Canyouseeme.org confirmed that the port was inaccessible. Today, with this evening's diagnostic report, my server's warning was gone and Canyouseeme.org confirms that the port is accessible again. I'm pleasantly surprised, but baffled.

Has anyone else run into a similar problem? I am on a residential FiOS connection.

you are viewing a single comment's thread
view the rest of the comments
[–] CrimeDad@lemmy.crimedad.work 3 points 1 year ago (2 children)

From the TOS:

You may not knowingly or unknowingly exceed the bandwidth usage limitations that we may establish from time to time for the Services, or knowingly or unknowingly use the Services to host any type of server or commercial network or subnetwork.

Lol I guess not then! I would think that many customers violate this rule because many consumer products contain some type of server.

[–] DeltaTangoLima@reddrefuge.com 2 points 1 year ago

I feel like this is antiquated language in their TOS. It probably dates back to the introduction of broadband residential services, when the cost of delivering network bandwidth was much higher.

But they keep it there as it gives them a nice, ambiguous set of terms they can either hide behind, or use to beat you over the head for a variety of reasons.

I'm guessing they, for whatever reason, temporarily blocked incoming packets going to common ports on your service. Maybe, at some point, the underpaid, overworked network tech on night shift realised they'd inadvertently turned on/off some inbound rule when troubleshooting another customer's problem, and changed it back.

But, you can't complain to them about it because you can't "hOSt a SeRVeR". Bloody ISPs.

[–] stown@sedd.it 2 points 1 year ago

Plenty of multiplayer games need to run a server so you can play with your friends, not always cloud based. Would Verizon require a business class account to host a multiplayer session for Halo on your Xbox?