Standard Port Forwarding not working

[Bondy86]

EE Full Gig broadband using a EE Smart Hub Wifi 7 router
Followed the User Guide and a YouTube video but CANNOT get port forwarding to work.

https://youtu.be/LJ3X3dD3DFU?t=648

I can 100% access those devices via my LAN on those ports and they work 100%
Cannot access them via my WAN IP address on those ports.
PortChecker shows the ports are closed.

However when I put the server into a DMZ (DO NOT RECOMMEND) I can then access the ports from my WAN which must mean the Router/Firewall is not working correctly.

Please can someone recommend a fix for me.
Kind regards,

[bobpullen]

@Pecbeck - exactly how have you got things configured?

I have port 80 and 443 successfully forwarded on a 7 Plus, pointing to a Caddy reverse proxy server that's doing SSL/renewing certs via Cloudflare. All working fine and dandy. Not quite the same but an indicator that it can't be entirely broken 🤔

How are you renewing the certs? If you put a file on your server where the renewal http challenge is looking, can you get to it from outside your network?

[Pecbeck]

Same, 80 and 443 forwarded to static ip on raspberrypi. Had lots of ch errors configuring, after several tries reboots factory reset got port configured. Tried nginx (was working fine on previous bt hub) and also tried caddy. Both had problems renewing certs. Logs tend to indicate it can send out of 80, but letsencrypt can't talk back through 80. 443 sometimes works for http only, but flaky.

I guess I'm not on cgnat, so have to assume port 80 incoming is issue 

How did you get it working? I've been on this all week since Monday when I got the 7 plus

They insisted on sending an engineer after 2 hours on support call, coming tomorrow 

[Pecbeck]

BTW port checker yougetsignal says ports open. This is all very bizarre. I've tried trashing npm and reinstalling, constantly fails to get certs, same on caddy

[Pecbeck]

Something changed overnight. Yesterday I saw dns timeout problems and certificate wouldn't renew. Woke up today and all,is working!

I changed nothing

[bobpullen]

---

@Pecbeck wrote:

How did you get it working? I've been on this all week since Monday when I got the 7 plus

---

I didn't do anything, just configured the port forwarding rules and pointed them to my server. Similar to you, I came from a different hub where it was already set up and working. My static LAN IP is configured directly on the server and not assigned via the hub if that makes a difference 🤷

Odd that it's just sprung back into life. I know there's a firmware upgrade doing the rounds so wonder if you were upgraded overnight?

[Joycee501]

I was upgraded overnight and can now assign Static IP's, but for the life of me, non of my Port Forwarding Rules are working. Going to take a break and come back to it in a few hours with a fresh head; otherwise it'll all get thrown out the window.

[Pecbeck]

Yesterday I had dns timeouts and still couldn't renew ssl certificates.  I have a feeling it may have upgraded f/w overnight to 4001, if not maybe dns propagation

I'll never know, just glad it suddenly started working

[Joycee501]

Been at this for hours and hour and just can't get port forwarding to work. It feels like EE are intercepting both 80 and 443 as after opening both ports; setting up NGINX to handle the reverse proxy and using cloudflare to deal with DDNS; it just doesn't work. 

curl -v http://<my public ip address> - Connection timed out 

curl -v https://<my public ip address> - Connection timed out

Does anyone have any advice as I'm losing my mind here. I've never experienced anything like this in all my years of setting up networks.

[Pecbeck]

I had similar problems . Was using duckdns and dynu . Even th9ugh ports 80 and 443 showed open, I could not get letsencrypt to create certificates. Suddenly on Friday it started working, I think the was a hub firmware update Thursday night.  I'm now on f/w 4001 and everything works fine now. I moved to dynu from duckdns as duckdns is flaky. I don't use the ddns on the hub, just have a program on my raspberrypi to update ip

Hope that helps, I was also tearing my hair out all week since I moved from BT hub to EE. BT hub was working fine on NPM (nginx gui, brilliant app), but failed with EE hub until friday

[Joycee501]

I'll give dynu a try. Like you, I moved from duckdns to Cloudflare because the reliability of duckdns wasn't good enough for me... Also on 4001 since Thursday, so hopefully can get this resolved.