this post was submitted on 02 Jan 2025
0 points (NaN% liked)

Self Hosted - Self-hosting your services.

11680 readers
26 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

Important

Beginning of January 1st 2024 this rule WILL be enforced. Posts that are not tagged will be warned and if not fixed within 24h then removed!

Cross-posting

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

founded 3 years ago
MODERATORS
 

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?

top 20 comments
sorted by: hot top controversial new old
[–] [email protected] 0 points 1 week ago* (last edited 1 week ago)

Since it sounds like this is your home router since you mentioned you use Comcast. If you are testing the site from within your network using your external ip then you are possibly running into a loop back block. Comcast does not allow traffic that originates from within your network back into your network.

Try the ip/site from a Hotspot and that might work.

[–] [email protected] 0 points 1 week ago (1 children)
[–] [email protected] 0 points 1 week ago

Not an issue if one uses VPN for HTTPS traffic like in the blog post.

But I guess similarly one should be mindful about the VPN traffic too. The cloud provider would technically be able to sniff unencrypted traffic - like HTTP.

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

Why not switch to a non-shit ISP?

[–] [email protected] 0 points 1 week ago (1 children)

Rural and suburban areas often only get one ISP in the US. Comcast specifically is infamous for using scummy practices to get (and then legally enforce) local monopolies. So the odds are not in OPs favor.

[–] [email protected] 0 points 1 week ago

ding ding ding! It's the only option, and I hate it.

[–] [email protected] 0 points 1 week ago (1 children)

In certain countries, no ISP offers this.

[–] [email protected] 0 points 1 week ago (3 children)

The OP mentions he uses Comcast, which is an American ISP. I myself live in ‘socialist’ Europe and I can choose from 13 different ISP on fiber alone. Surely OP who lives in ‘free-market’ USA must have an unimaginable number of options.

[–] [email protected] 0 points 1 week ago (1 children)

You're just jealous of our freedom to choose between different health insurance companies to deny our claims for care and bankrupt us

[–] [email protected] 0 points 1 week ago

Oh, I get to choose health insurance too. Only it’s not linked to my employer. And they all have to offer the same coverage. And they can’t refuse you for the basic health insurance.

[–] [email protected] 0 points 1 week ago

America ISP options for any given address are listed at https://broadbandmap.fcc.gov/ , and you can filter it to only show high-speed ISPs. It gets updated a few times every year

[–] [email protected] 0 points 1 week ago

@nothingcorporate You can also purchase a static IP address

[–] [email protected] 0 points 1 week ago

If you - like me - dont like to use large companies if you can avoid it, I suggest a proxy server. You open port 8089 or something on your router, (security bonus: accept only connections from proxy‘s ip,) install nginx proxy manager and reroute the domain in question to said ip and port.

This probably works in many ways but thats the first that comes to my mind.

Of course you can use cloudflare free tier afaik. But remember, if you dont pay for it, you‘re the product.

[–] [email protected] 0 points 1 week ago

Why do you need port 80 specifically? If it's for your own use, you can run http on any port. And you should be using https on 443 if at all possible anyway.

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

Cloudflare tunnels are the thing you're looking for, if you're not opposed to cloudflare.

You run the daemon on your local system, it connects to cloudflare, and presto, you've bypassed this entire mess.

[–] [email protected] 0 points 1 week ago

For anyone who would prefer not to use Cloudflare, the solution is a free Oracle VPS, a Wireguard tunnel into your homework, and a reverse proxy on the VPS (Caddy is my personal preference).

[–] [email protected] 0 points 1 week ago

SOLVED! I had to learn how Cloudflare tunnels work, but 45 minutes later and it's doing exactly what I need, thank you so much, kind internet hero!

[–] [email protected] 0 points 1 week 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.

[–] [email protected] 0 points 1 week 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!