Conflict with Slack's Nebula

[GordonShumway]

• 3CX Version: Standard Annual 16.0.4.493
• Server OS: Debian 9.11
• 3CX Server Hosted: Google Cloud (micro-f1)

I have freshly provisioned this VM (thru 3cx deploy feature) and restored a previous VM backup (without the key/FQDN), but I'm pretty sure any existing 3cx instance would be affected.

When I run the Slack's Nebula node (https://github.com/slackhq/nebula, the binaries are lightweight) on port 4242 on the same VM, the 3CX SIP Server component stops and cannot be successfully started/restarted until the Nebula service is stopped.

Is that a port collision? Can I just run Nebula node on a different port to keep the 3CX SIP Server component happy?

I'd like to run Nebula to hide the SSH behind it, while leaving every other port open.

 

[cobaltit]

Not sure if it's a port conflict, but Nebula is essentially a VPN and 3CX does not support having VPN on the 3CX instance. As far as a port conflict. Just look at the ports when 3CX is running and Nebula isn't.

 

[GordonShumway]

Well, I haven't seen anything on 3cx to suggest it is using port 4242 which is being used by the Nebula node.

Can I tag any of the 3cx people in this thread to get an official reply? Since 3cx is commonly run on the internet-facing VMs, hiding SSH port behind the Nebula node sounds like a great idea.

 

[JohnS_3CX]

Also just FYI micro-f1 is too small, we recommend G1 as a minimum
https://www.3cx.com/docs/recommended-hardware-specifications-for-3cx/#h.4z53dfbtxlno

Services may shut down when there aren't enough resources so you should build a bigger machine that doesn't have a shared CPU (if you want to test it).

We do not support having any other services on the machine, we don't know how they will interact or affect your instance.