Whitelisting IP doesn't seem to be working

[TylerM]

I'm trying to access https://{mydomain}.3cx.us:5001/webclient/#/people from a new virtual machine and therefore a new IP address. The new virtual machine uses a static public IP address so I added that to the IP Blacklist with the "Allow" Action. I restarted my 3CX instance, but I'm still getting this error:

I also tried restarting all of the services through the 3CX admin portal and I also added the IP via Console Restrictions. As far as I can tell, there's nothing more in my firewall settings that should be blocking this traffic. I can still access the admin portal and web client from my normal computer, so the problem is specific to this new VM/IP.

 

[NikolasA_3CX]

Hi @TylerM

Adding an IP to the IP Blacklist and setting it to "Allow" does not impact the FQDN's accessibility itself. Instead, it simply ensures that when accessing the FQDN from the specified IP, the PBX will permit login and access to PBX services.

In summary, the IP Blacklist section controls whether an IP can access the PBX services but does not affect the IP’s ability to reach or resolve the FQDN.

 

[TylerM]

Turns out, it was an inbound rule on my network security group attached to my network interface that was blocking my traffic.

 

[NikolasA_3CX]

We are glad the issue has been resolved