Solved Cannot detect IPv4 address when External IP is set to Dynamic

[ED K]

New system, running latest v18 update 9 build 31 on Windows 11 Pro.

When I first commissioned the system it correctly "detected" my current public IP and set that as a static value. Firewall test passed with no issues.

BUT this site does not have a static IP address, so I set it to "dynamic" in Network settings >>> Public IP. Now the dashboard just always says "detecting".

As I mentioned earlier If I run the firewall test with my current public IP entered in the "static" field, it passes just fine. If I change it to dynamic and re-run the test it pops up a (500) error that says "Value cannot be null. (Parameter 'address')"

What am I doing wrong?

 

[OlegR_3CX]

It seems that something is blocking the 3CX System when using dynamic IP, to contact its remote servers.
Have you tried bypassing your networking firewall and see if this issue is still there?

 

[ED K]

Thank you for the reply. Windows firewall is completely disabled and there is no network firewall, just a basic router.

The public IP does not change when 3CX is set to dynamic. It is still the same public IP and everything else also remains the same. I don't see how a firewall setting could impact that, but again, everything resembling a firewall is bypassed.

The ONLY difference this setting should make is that 3CX SHOULD be automatically updating the FQDN record if and when the site's public IP does change, which could be weekly or monthly. We even let it sit overnight to see if it would "detect" the IP and no luck.

 

[ED K]

After much head-scratching, hand-wring, cursing, and exasperation, we found this forum post:
https://www.3cx.com/community/threa...lic-ip-address-from-static-to-dynamic.113206/

Their fix was to disable the UNUSED and NOT-CONNECTED wireless adapter, so we decided to try it even though it makes zero sense. Well I am happy to report that our system started working immediately! There is clearly something wrong in the 3CX software, and it looks like the bug has existed for at least a couple of years.

But this worked, so we wanted to post it so that hopefully it helps someone else if they have the same issue. Good luck!

 

[OlegR_3CX]

Thank you for the feedback provided and glad your issue is resolved.
Just for your information, as per our manual, it is essential and important to disable unused networking adapters as it sometimes causes the issue.
This thread will be closed.
Have a nice weekend ahead