@mriegler 

Just thinking out loud... do you have a router between the ER605 nad the WAN?   Some ISP router for example

If so have you port forwarded the traffic on it to the ER605?

@Philbert I get where you're coming from, but no - the ER605 is directly connected to the fiber line with pppoe.

And like I said it worked before when configured on the ER605, but apparently it has some quirks when setting up from the Omada Controller.

Hmmm!

@Virgo 

When configured directly on the ER605 as "Virtual Server" the port forwardings work. Now when configured through the Omada Controller, only 1 of my 3 port forwardings work.

To me it looks like something is preventing port 80 and 443 to be forwarded. It's either in the Omada Controller software itself or how the Omada Controller configures the port forwardings on the ER605.

@mriegler 

Well the problem appears to be the two ports associated to that other specific IP.

Is the firewall turned off on that virtual server? no idea what os etc you have but if it's win10 make sure its not set to a "public" network which can happen sometimes when swapping cables around. weirder things have happened and eluded the best of us lol.

@mriegler 

Hi There, I'v had similar issues like you have. Some of the ports were working some of them now.

Debug with all firewall, attack prevention, fllods ,detections are turned off.

In my case 443 was working correclty but other NAT-ed service port to same server not....

I'v got success in standalone mode, so my assumption was that there are issues in Omada - somehow.

Than I re-adopted ER605 and it started to work.... no clue what happened.

@mriegler 

Anyone find a resolution yet? I added 5 ports to be forwarded but only 1 works.