Reinstalling server > SetupConfig.xml gives error

[JW Web Services]

Due to a RAID crash on my vmWare ESXi server, the data containing my server was lost. And stupid me I do not have any server backup.

I have rebuilt the RAID with new drives, and am reinstalling the 3CX server. It initially took 3 attempts using the provided ISO to get it installed, but now it is installed and ready. However, when asking for the SetupConfig.xml file, I provide the link from my portal and it gives an error "Invalid option selected".

The server is located on premise, using a custom domain.

When viewing the XML file, I fear that the error is this section:

<option>
<code>NeedFqdn</code>
<answer>no</answer>
</option>
<option>
<code>Hostname</code>
<answer>pbx-*removed for security*-nl</answer>
</option>
<option>
<code>DnsSuffix</code>
<answer>a-gl</answer>
</option>
<option>
<code>DomainGroup</code>
<answer>Other</answer>
</option>
<option>
<code>HasLocalDns</code>
<answer>no</answer>
</option>

When I run the SetupConfig.xml through the console instead of the Web version, I get the following:



It is simply not allowing me to use a custom FQDN using the config received from 3CX portal. Even though the "NeedFqdn" is set to no, it is still running the script as if I need a FQDN from 3CX. Is there any way around this? I have been at it now for about 6 hours.

 

[JW Web Services]

Installing version 18 (with the plan to upgrade to version 20 afterwards) gives a invalid license error. I expected that, seeing as I already had it upgraded to version 20.

 

[Guillaume Bourgeois]

Hello,
Have you verified the FQDN bind with your license on your portal at customer.3cx.com ?

Is this the correct FQDN?

If yes, go to
https://install.3cx.com/?license={{Your_License}}

Replace "{{Your_License}}" with your license key in the format xxxx-xxxx-xxxx-xxxx.

Generate a new setup config file.

Please ensure to select "New Installation" with the configuration file.

If this does not work, modify the configuration file to redact private informations (e.g., License, FQDN, email...) and post the file here.

 

[Guillaume Bourgeois]

I have personally tested it by starting fresh with a custom FQDN, and it works perfectly.

Here is a copy of my SetupConfig file with some values redacted. I uploaded the unmodified version to new 3CX installation and had no issues.

 

[JW Web Services]

FQDN is correct, and have also verified by going to the address.
I followed the install.3cx.com link with the license. Each install attempt I do these steps again and generate a new SetupConfig.xml. It always comes with the same. I have attached the file here. It is, as recommended, redacted. I X'd out any private information. Email, passwords, website address, etc.

 

[NicholasP_3CX]

The setup config XML which is created is only for Version 20. So when you go to deploy, it is best to just go straight to Version 20, not Version 18.

 

[JW Web Services]

I have tried it on both 18 and 20 to no success.