Solved Problems activating new install - license_error.HTTP/1.1 400 Bad Request

[MikkelAnd]

Hi,
Having just recently installed a new debian 3cx v. 18u2 on HyperV at a client site I'm experiencing som problems activating the license.
We keep seeing "license_error.HTTP/1.1 400 Bad Request"

I cannot seem to find any logs on the server and I've verifiied correct internet access (using curl). I do not control the firewall so I'm wondering if there's any tests I can perform using cURL or log files to read which may help me solve this issue.

Btw. the server updates just fine - just installed U2 today, but the problem persists.

Logs from /var/lib/3cxpbx/Data/Logs/PbxWebConfigTool.log



/mikkel

 

[ChrisC_3CX]

As a quick test try running this from the server:

wget https://activate.3cx.com:443

What do you get when you try this?

Can you also verify if you followed our guide when deploying this instance: https://www.3cx.com/docs/installing-microsoft-hyper-v/

Note: Including installing the ntp client.

 

[MikkelAnd]

As a quick test try running this from the server:


What do you get when you try this?

Can you also verify if you followed our guide when deploying this instance: https://www.3cx.com/docs/installing-microsoft-hyper-v/

Note: Including installing the ntp client.

Hi

Doing wget https://activate.3cx.com:443 yields an empty index.html file

I've followed the HyperV instructions and NTP is installed, enabled and running.

 

[ChrisC_3CX]

Could you please send me the first 8 characters of your license Key via PM?

 

[MikkelAnd]

Could you please send me the first 8 characters of your license Key via PM?

Will do! Was a bit busy ...
/mikkel

 

[MikkelAnd]

Thank you for excellent support, @ChrisC_3CX - it turned out to be incomplete registration information on our part.
Once that was completed the install activated just fine.

/mikkel

 

[ChrisC_3CX]

As per our PM conversation it seems that the issue was that not all fields under "Settings >> License" were populated. After filling in all fields, applying the settings and then refreshing the license key information, it now seems to be resolved.