Hi!

I am finally dabbling in some self-hosting and I’m having trouble on the very final steps.

The setup:

I have a simple NUC that’s hosting caddy and a dynamic dns solution

I have port forwarded ports 443 and 80 to my local machine

I have a domain pointing towards my public ip

My router is a sercom 00200106 brought by my isp

The problem:

¿I can’t seem to get past the router?

Whenever I try to get in through my local network I get an “intercept.hmtl” from the router and anyone to get from outside just gets a timeout.

If anyone has any idea how’d I go about moving forward the domains “https://gonzako.com/” I have managed to get caddy to show the “hello world” through localhost so I know the service is working

Many regards!

Gonzako

Edit: I am not behind NAT as I did a traceroute towards my public ip and it did only a single hop

  • MangoPenguin@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    2
    ·
    14 days ago

    Are you trying to access the domain from inside your own network that it forwards to? If so that may not work due to the way NAT works.

    Try from your cellphone data plan to verify.

  • drkt
    link
    fedilink
    arrow-up
    1
    ·
    14 days ago

    Do you know the manufacturer and model number of the router?

  • darkan15@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    14 days ago

    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

    • Gonzako@lemmy.worldOP
      link
      fedilink
      arrow-up
      1
      ·
      14 days ago

      I think I am behind a double Nat as I’ve tested your higher than 1024 port option and it hasn’t worked

      • darkan15@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        14 days ago

        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.

        • Gonzako@lemmy.worldOP
          link
          fedilink
          arrow-up
          1
          ·
          14 days ago

          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

          • bigredgiraffe@lemmy.world
            link
            fedilink
            arrow-up
            3
            ·
            14 days ago

            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!

          • darkan15@lemmy.world
            link
            fedilink
            arrow-up
            2
            ·
            edit-2
            14 days ago

            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