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.
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!
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).
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.
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.
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.
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.
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, 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!
@nothingcorporate You can also purchase a static IP address
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.
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!