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 may want to read this:
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.
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.
You're just jealous of our freedom to choose between different health insurance companies to deny our claims for care and bankrupt us
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.
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
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.
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.
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.
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, awebsubdomain 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!
