- Joined
- May 3, 2022
- Messages
- 4
- Reaction score
- 0
Hello everyone,
I have a question regarding the officially supported installation methods for 3CX in cloud/VPS environments.
I’m working with a VPS provider that does not allow booting from custom ISO images and does not provide KVM/ISO mounting. Because of this limitation, installing 3CX via the official ISO is not possible.
I know that:
3CX provides a Debian-based ISO for bare metal / hypervisors
There is also a 3cxpbx package available via the 3CX Debian repository, which can be installed using apt on a supported Debian OS
My questions are:
Is installing 3CX via the official Debian repository (apt install 3cxpbx) considered an officially supported installation method by 3CX?
If yes, are there any functional or support limitations compared to an ISO-based installation?
If not, what is the recommended and supported approach for installing 3CX on VPS providers that do not allow custom ISO boot?
I would like to follow a fully supported setup, especially for production use, and avoid unsupported or risky workarounds.
Thank you in advance for any clarification.
Best regards
I have a question regarding the officially supported installation methods for 3CX in cloud/VPS environments.
I’m working with a VPS provider that does not allow booting from custom ISO images and does not provide KVM/ISO mounting. Because of this limitation, installing 3CX via the official ISO is not possible.
I know that:
3CX provides a Debian-based ISO for bare metal / hypervisors
There is also a 3cxpbx package available via the 3CX Debian repository, which can be installed using apt on a supported Debian OS
My questions are:
Is installing 3CX via the official Debian repository (apt install 3cxpbx) considered an officially supported installation method by 3CX?
If yes, are there any functional or support limitations compared to an ISO-based installation?
If not, what is the recommended and supported approach for installing 3CX on VPS providers that do not allow custom ISO boot?
I would like to follow a fully supported setup, especially for production use, and avoid unsupported or risky workarounds.
Thank you in advance for any clarification.
Best regards