Host intermittently blocked because "port isn't opened on my WAN" despite being set up in NAT.

Follow

Erik Dasque

• June 23, 2026 16:56
• Edited

I'm running a home server (Ubuntu 22.04 + Docker + Traefik) called Watcher2.5G behind my Firewalla Gold Pro (v1.983) with port forwards for TCP 80 and 443. External HTTPS access fails intermittently in a pattern that might point to Firewalla expiring NAT conntrack entries for established TCP connections after approximately 60 seconds of idle time. I can see that through an external Uptime Kuma server.

This is intermittent; it mostly works but sometimes doesn't...

 

Pictures are worth a thousand words. Firewalla shows my external Uptime Kuma being blocked despite being allowed:

 

I would love to get some advice on how to diagnose the issue.

0

• 

  Firewalla

  • June 23, 2026 17:32

  Firewalla shouldn't expire TCP connections after 60 second; May I know if your container is behind another switch? is there another software switch (from hypervisor) on your server? The docker container has a valid LAN or behind another NAT layer?

  0

  Comment actions Permalink
• 

  Firewalla

  • June 23, 2026 22:49

  Our developer said this: "From the screenshots, it looks like port-forwarding NAT is not working when the WAN block flow is triggered." He wants to look at your configuration. I have created a ticket for you. 

  0

  Comment actions Permalink

Please sign in to leave a comment.