Unsupported 3CX self hosted VM on Proxmox web and app client stop connecting

[Lance Harvie]

Hi Folks,

I have recently self hosted 3CX on a VM on my Proxmox server.

12GB RAM
120G SSD
10 cores

So loads of resource are given to the VM for 3CX.

Everything has been running smoothly except that I noticed after a few hours the web client and OS clients including mobile clients can't connect to the server anymore.

The only fix is to reboot the VM.

Ports 5001, 5090 and all the other required ports are open.

Any help would be greatly appreciated.

 

[ChrisC_3CX]

As Proxmox is not a 3CX supported virtualization platform I would recommend that you consider switching to one that is: https://www.3cx.com/docs/recommended-hardware-specifications-for-3cx/

Even if you do go through the trouble of investigating and determining that the hypervisor was not the cause, I would still strongly recommend that you migrate the instance to ensure future compatibility and to generally keep your 3CX configuration a fully 3CX supported deployment.

 

[SweetAction]

If you want to troubleshoot I'd start with steps like...

Using the same device that can't connect to webclient
-Can it resolve the IP from the FQDN? (nslookup fqdn)
-Can it connect to the management port? (Test-NetConnection -Computername FQDN -Port 5001)
-If remote, what about devices on local lan?
-Is the Server still listening on the port (netstat -an)
-Is the services still running on the server? (Get-Service 3CX*)

Figure out what's broken and then you can figure out how to fix it.

But using supported setup is always a good idea and I'd encourage that. Many times that will fix the issue.

 

[Lance Harvie]

If you want to troubleshoot I'd start with steps like...

Using the same device that can't connect to webclient
-Can it resolve the IP from the FQDN? (nslookup fqdn)
-Can it connect to the management port? (Test-NetConnection -Computername FQDN -Port 5001)
-If remote, what about devices on local lan?
-Is the Server still listening on the port (netstat -an)
-Is the services still running on the server? (Get-Service 3CX*)

Figure out what's broken and then you can figure out how to fix it.

But using supported setup is always a good idea and I'd encourage that. Many times that will fix the issue.

Awesome advice SweetAction - will definitely debug according to your suggestions. - Will report my findings

 

[Lance Harvie]

As Proxmox is not a 3CX supported virtualization platform I would recommend that you consider switching to one that is: https://www.3cx.com/docs/recommended-hardware-specifications-for-3cx/

Even if you do go through the trouble of investigating and determining that the hypervisor was not the cause, I would still strongly recommend that you migrate the instance to ensure future compatibility and to generally keep your 3CX configuration a fully 3CX supported deployment.

Thanks ChrisC_3CX - appreciate your help. Proxmox uses KVM as the hypervisor which is supported on the recommended hardware page.

• KVM 2.8 and up

The VM is running the 3CX iso as it would do on any other intel CPU compatible VM or bare metal machine.

Is there a reason why future versions of 3CX will not work in an intel CPU compatible VM?

I have invested in a 64 core, 256GB dedicated server which runs all our biz apps including 3CX and I don't really want to fork out for yet another server just to run 3CX.

 

[10m]

I use Proxmox to run my 3CX SBC and it has always worked without any issues. I have not used PVE to host my 3CX PBX but I imagine it would work just fine because as you pointed out PVE runs on KVM and KVM runs 3CX. I would run the tests as @SweetAction suggested when you have these connectivity issues. It sounds to me like connectivity issues. Or maybe an IP address conflict? Running those tests when the failure occurs will help identify where the problem is coming from.

 

[Lance Harvie]

I use Proxmox to run my 3CX SBC and it has always worked without any issues. I have not used PVE to host my 3CX PBX but I imagine it would work just fine because as you pointed out PVE runs on KVM and KVM runs 3CX. I would run the tests as @SweetAction suggested when you have these connectivity issues. It sounds to me like connectivity issues. Or maybe an IP address conflict? Running those tests when the failure occurs will help identify where the problem is coming from.

Thanks 10m ! I agree it seems like a connectivity issue - will run through the tests - so far it's been up without issues. Will post my findings here.

 

[ChrisC_3CX]

Proxmox uses KVM as the hypervisor which is supported on the recommended hardware page.

To avoid any misunderstanding, just want to make clear that the fact that we support KVM as a virtualization platform does not imply that we support any other KVM based hypervisor such as ProxMox. For ProxMox specifically this was also discussed here: https://www.3cx.com/community/threads/sip-server-wont-start.80645/post-371569

On the other hand, it also does not necessarily mean it will not work, however, it has not ever been tested by 3CX and will therefore remain an unsupported configuration unless stated otherwise.

That said, our recommendation continues to be to switch to a 3CX Supported hypervisor but no matter the path you choose I hope you find a swift solution to your issue.