ER707-M2 Port Forwarding 80 & 443 in controller mode
Has there been a solution yet to the port forwarding issue with ports 80 & 443? I am using the gateway in controller mode with the software controller. I have tried every suggestion i could find to change the gateways management ports to anything other than 80 & 443. I see this has been an issue going back several years. I can not use different ports for my server (NGINX Proxy Manager) as it needs those ports for the Let's Encrypt Certificate generation. I have multiple ports forwarded and the only ones that do not work are 80 & 443 they just point to the gateways page stating it is managed by a controller.
As far as im aware there is no designed auto-forward 80&443 to the gateway, i believe Jeremy is incorrect.
In my testing, this looks like a firmware bug in ER707-M2
On ER8411, i setup the following test
Port forward rules: 80&443 to internal IP (i chose a switch, destination doesn't matter)
Loading my public IP in browser results in the selected device in the forwarding rules loading
If you have remote sites adopted via port-forward method, you may have a port forward already set up to the controller for remote adoption and firmware updates, in controller 6.1 and later you can stop forwarding 80&443 to the controller as you can set a dedicated upgrade port in the controller
Global > System Settings
The only caveat i can think of is some insane design decision relating to gateways adopted under a software controller, but i wouldnt think this is the case as from the gateways point of view there is no difference between an SW Controller and a OC controller, and there would be no reason to internally change the forwarding rules in such a scenario. 80 and 443 are the most common ports to forward for things lke web servers, hence my feeling this is a firmware bug in the gateway