Change network adapter in vultr debian server in 3cx

[ElementalWindX]

When adding a private ip to a vultr instance for 3cx after everything has been running fine, what is the process to get the debian os to recognize and use the private adapter instead of the public adapter, and getting 3cx to utilize a different public static ip address?

When I run ip a, I see the adapter (enp5s0), but it doesn't appear to gain a dhcp address. I'm guessing I need to edit /etc/network/interfaces and reload the network, and specify a manual static ip under external ip configuration. Is there anything else past that I'd need to do to make sure everything will be fine in a 3cx instance?

Thanks

 

[Evolute IT]

When adding a private ip to a vultr instance for 3cx after everything has been running fine, what is the process to get the debian os to recognize and use the private adapter instead of the public adapter, and getting 3cx to utilize a different public static ip address?

When I run ip a, I see the adapter (enp5s0), but it doesn't appear to gain a dhcp address. I'm guessing I need to edit /etc/network/interfaces and reload the network, and specify a manual static ip under external ip configuration. Is there anything else past that I'd need to do to make sure everything will be fine in a 3cx instance?

Thanks

Don't use private adapters on Vultr, specially not after the setup.

The 3CX should get its IP from the main adapter, and if you need to change it, set it to Dynamic in Network Settings and reboot. It will grab the new Public IP.

 

[ElementalWindX]

Don't use private adapters on Vultr, specially not after the setup.

The 3CX should get its IP from the main adapter, and if you need to change it, set it to Dynamic in Network Settings and reboot. It will grab the new Public IP.

I'm trying to put it behind a pfsense vultr instance. How would you do that without using private ips?

 

[Evolute IT]

I'm trying to put it behind a pfsense vultr instance. How would you do that without using private ips?

I wouldn't do it. Vultr has a firewall already and it doesn't support not having a public IP anyway on a VM. The pfSense becomes useless at that point.

You would be better off spinning up your own datacenter for this and have more control.