Self Hosted - Self-hosting your services.

14789 readers

23 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

No harassment
crossposts from c/Open Source & c/docker & related may be allowed, depending on context
Video Promoting is allowed if is within the topic.
No spamming.
Stay friendly.
Follow the lemmy.ml instance rules.
Tag your post. (Read under)

Important

Lemmy doesn't have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate. This is strongly encouraged!

Cross-posting

!everything_git@lemmy.ml is allowed!
!docker@lemmy.ml is allowed!
!portainer@lemmy.ml is allowed!
!fediverse@lemmy.ml is allowed if topic has to do with selfhosting.
!selfhosted@lemmy.ml is allowed!

If you see a rule-breaker please DM the mods!

founded 4 years ago

MODERATORS

Zoe8338@lemmy.ml

dogmuffins@lemmy.ml

testman@lemmy.ml

Way to get around ISP blocking port 80 (lemmy.today)

submitted 6 months ago by nothingcorporate@lemmy.today to c/selfhost@lemmy.ml

21 comments fedilink hide all child comments

I'm trying to host a few docker services from my house, but my IP appears to be blocking port 80, so the only way to get a domain working that I've found is domainname.com:portnumber (I have port forwarding set up in my router, and can reach a wide range of ports, but not 80).

It looks like cloudflare will point sites to my IP but not ports, and because I can't reach port 80, I can't figure a way to route things through NGINX proxy manager on the same box.

Is there a free external service I can use as a reverse proxy to point requests to specific ports on my self-hosted box? Or else, is there another way to make my sites useable without the enduser having to specify ports?

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

[–] nothingcorporate@lemmy.today 2 points 6 months ago (1 children)

Note: The ISP is Comcast, who at various points on the web has claimed to block and NOT block :80, but lots of other people online seem to have the same problem, indicating that they do. At least for some people.

[–] smpl@discuss.tchncs.de 4 points 6 months ago

First thing I would ask the ISP to open the port. I've done that without problems before.

If that's for some reason not a solution, I would, because I'm personally not very attracted to the idea of routing my selfhosting traffic though thirdparties, setup a simple static page with <meta http-equiv="refresh" content="0;url=https://web.domain.tld:8080/" />, somewhere and point the bare domain and www subdomain to that page and have it redirect to, like in this example, a web subdomain with the port number.

As a last remark, I personally would not find it problematic for a different port number to be part of the host scheme and also note that most web traffic now goes to 443 and not 80 because it's https.

Happy selfhosting!