2
[Help request] How do I go about debugging my router?
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 04 Aug 2025
2 points (75.0% liked)
Self-hosting
3010 readers
8 users here now
Hosting your own services. Preferably at home and on low-power or shared hardware.
Also check out:
founded 3 years ago
MODERATORS
If your ISP (Internet service Provider) doesn't have you behind CGNAT or Double NAT (meaning that multiple homes share the same public IP), some ISP block the first block of 1024 ports, so any port below that number is blocked.
If the problem is that ports below 1024 are blocked, but you do have a public IP reaching your home router, you could contact your ISP so they unblock these ports for you (I had to do that once, so at least with my ISP it was as simple as asking).
The way you could test if your public IP reaches your home router is by exposing something on a higher port than 1024 like let's say 8080, if you can reach a simple web or caddy or any other service from 8080, you can at least confirm, that is the issue.
Be aware that most ISP even if they assign a single IP per house, this IP can be dynamic and can rotate on a regular basis, like daily or weekly
Hey! I finally got the site up!
I think I am behind a double Nat as I've tested your higher than 1024 port option and it hasn't worked
For the record, I was able to see "hello world" on https://gonzako.com/ earlier. It was reachable from the outside.
Thank you! Site is finally up and going!
Well, if you are forwarding the ports from your home router, and you can't reach, it's the most probable cause, if you are, that means that there is no public IP reaching your home router.
You could contact your ISP and confirm if this is the case, they could offer to assign a public IP for an extra fee, your only other option is to rent a cheap VPS and tunnel traffic between it and your home, but at this point you could also decide to host stuff on the VPS.
Oh! I am actually not behind Nat as I did a traceroute towards my public ip and it only did one hop. So it's seems to be the port forwarding in itself not working
To add some more info to what the others are saying, if your public IP address is in the range
100.64.0.0/10(so between 100.64.0.0 and 100.127.255.255) then it is a CGNAT IP and you will not be able to make port forwarding/NAT work to/from the public internet because your public IP is not actually a publicly routable IP on the internet no matter what your ISP calls it. Hope that helps!Traceroute can be a good hint but try to do one to an IP like 1.1.1.1 and see the initial jumps, another way to confirm is on your router config interface, there should be an IP address it has assigned, subnet and gateway it connects to, with these values you could also verify it depending on what IP ranges it shows, and see if the assigned IP or Router's WAN IP is the same as shown when you search for "what is my IP" online.
If you can confirm that your router assigned WAN IP is the same as your public IP, then it could be a misconfiguration of the port forwarding on the router or a firewall block either on the router or the computer