Re: Firewall check always fails for a public IP?
Hi,
I get the feeling that "Firewall Check" is mislabeled (to be polite).
My 3CX system is BEHIND a firewall, but I assigned a public IP to the system. So it's protected, but I don't need to use NAT. Consequently, I don't need to use STUN? Correct? So I have "STUN" settings disabled.
The correct ports are open and the Firewall check shows them in "green".
The only "red" line is:
"Error (13) The machine is on a public IP. Please check the FAQ for more information. agentAddr = 87.230.29.162:4200 "
a) Why is having a public IP an "Error"?
b) Why does the Firewall Check "FAIL" - when all required ports were found open?
I get the feeling, the "Firewall Check" isn't reall a Firewall Check - it's a STUN/NAT check? And if STUN/NAT is not needed, then it treats that as an "fail/error"?
That seems like it's a bug?