Management Interface - Login Error when 3CX server is on specific VLAN

[rogan]

Hi,

I've got a strange (likely Firewall) issue - I've setup our test 3CX server and can access management console on 5000 and 5001 without issues when in the development vlan.

After moving the server to it's intended separate vlan I can see it come up on the correct IP, I can browse to the management console on 5000 and 5001 however I cannot login.
The screen sits on "Loading..." for longer than usual and once loaded I enter username and password (if incorrect it tells me) and then after a minute or so (timeout duration) it gives a very generic "Server Error" message in red above the login box.

Any theories as to what ports this means I'm missing? Given I can browse and telnet on 5000 and 5001 to the box I'd have assumed I could login...

Moving back to other vlan and rebooting the unit is accessible and works fine.
Additional info - Debian ISO install hosted locally in VMware, not resolved by restart, all services running correctly, nothing obvious in the logs I've looked at.

 

[rogan]

Have confirmed there is no firewalling between my desktop and this server - It is on a different subnet, is there some NGINX config that may be affecting this?

 

[Marmite]

Can you put your desktop on the same (intended) VLAN as the PBX server?
If not - may be client related - try different browser/in-private etc
If so, may be firewall related, had a "similar" issue the other day moving a windows host to a different VLAN and some things stopped working, and it was the scope on the firewall set to "local subnet only" - and as VLAN was a different range (fully routed) it got missed. (192.168.1.x & 192.168.2.x).

 

[BrenttG]

Are you specifying that VM onto a specific virtual network which is tagged on the vmware host, or are you moving the vmware host as a whole to another vlan?

VLAN config on vmware can be tricky, you may have a config issue there.