Unable to reach 3cx Updates server

[gigaboy]

I don't know if this is our standalone Debian system or outside our PBX. Really wierd this morning. Internet running normal. Can't dial out, intermittent drops, can take 30 seconds to connect to an outside caller. When I log into the system, shows not connected, activation failed, and can't connect to Update Server, yet I wait a few moments and status for everything is green. Running 16.0.4.504. Would a system reboot fix this, or is something else going on?

 

[Alphabetic]

Check your network settings, gateway and DNS servers. Run some ping tests from terminal of PBX.

A reboot wont harm I suppose in the first instance. But, could just be DNS related.

what are your DNS servers? Try changing to Googles.

 

[gigaboy]

1.1.1.1 for DNS, all traffic is normal. Debian is snappy again.

 

[Alphabetic]

snappy again? Sorry, dont know what youre trying to say here.

Ping test are fine? Continuous ping tests out to the internet and gateway are you getting any drops? What about a continuous ping from a local device to PBX?

Do a license refresh too, cant hurt.

 

[gigaboy]

Pings to 1.1.1.1 are less than 26ms
Pings to Debian PBX are less than 1ms

 

[gigaboy]

Refreshed the license, looks OK.
Seems to be ok

 

[Alphabetic]

Can you provide this

https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

 

[Alphabetic]

Refreshed the license, looks OK.
Seems to be ok

Ok goodo.

 

[gigaboy]

Found the problem. Two weeks ago, I set up a new debian instance on a stand alone appliance. I had an instance on Windows Hyper-Visor. And when I did the move, I set the VM instance to OFF. However, this past weekend, I did a Windows update which required a reboot. And unbeknownst to me, the VM started as well. So there was a conflict running two instances at the same time. Simple solution: prevent the VM instance from restarting when the Windows box is power cycled.
All now works as expected. Thanks for your help.