Solved Debian self hosted cutsom FQDN issue

[AK-47]

Hi all, I'm trying to run up a self hosted debian 3CX image. Everything goes well except that no matter what configuration I try I always end up with a 3CX FQDN. I have setup DNS correctly both externally and internally, port forwards are in place, the Let's Encrypt SSL generates, and hostname and FQDN of local environment is all setup during the initial config. Yet after the post config tasks run, I end up with hostname.3cx.region.com.
I'll admit it's been perhaps a year since I've run up a self hosted deb image so I'm wondering if something has changed. Does anyone have any advice or help for this?

Thanks.

 

[AlexisV_3CX]

Hi Andrew,

Are you using the 3CX wizard ? If so, note that it only 3CX FQDNs not custom on hosted environment.

Also note that this can only be done on On-Premise machines and also with the correct license key (https://www.3cx.com/ordering/pricing/).

 

[AK-47]

Hi Andrew,

You cannot use a custom FQDN on a hosted instance.

This can only be done on On-Premise machines and also with the correct license key (https://www.3cx.com/ordering/pricing/).

Yep, first line of my post - Self Hosted ie: on premise.

 

[AlexisV_3CX]

Yep, first line of my post - Self Hosted ie: on premise.

May I ask if the key your are referring to, is Pro or Enterprise ?

 

[AK-47]

May I ask if the key your are referring to, is Pro or Enterprise ?

Using a trial standard key at present.

 

[AlexisV_3CX]

Using a trial standard key at present.

You cannot use a custom FQDN on a Trial key. This can be done only on Pro or Enterprise as can be seen in the link provided (https://www.3cx.com/ordering/pricing/ - expand Core PBX Features)

 

[AK-47]

Of course. Thanks for the reminder.