Solved license_error.HTTP/1.1 400 Bad Request

[rldv9281]

Inbound rules pointing to call queues suddenly notify the caller of a license issue (Enterprise or Professional required). The PBX is using a valid Professional 4 license with an expiration date in the future. When refreshing license key information the following error is displayed: license_error.HTTP/1.1 400 Bad Request. I suspect the issue has something to do with invalid characters being used in de Customer details fields (Company Name and Contact Name). Unfortunately I'm unable to remove the invalid character in the Contact Name, because the field is not editable.

Product: Professional Annual
Version Number: 18.0 (Build 16)

 

[JohnS_3CX]

Please read here:

https://www.3cx.com/blog/releases/fqdn-endpoint-change/#:~:text=To improve our cloud services,term support, compatibility and security.

You are stuck on an older version and can no longer activate. Emails were sent out informing about this ahead of time, and we also published it on our blog.

The solution now is to take a backup, reinstall 3CX and restore in the latest version, and you should be able to activate going forward.

 

[rldv9281]

John thanks for getting back to me so soon. I realize now the version number on the License Settings page is different than version number shown in the 3CX management console dashboard. The version shown in the dashboard is 18.0 Update 3 (Build 461).

dpkg -l | grep 3cxpbx
ii 3cxpbx 18.0.3.461 amd64 3CX PBX

The 3CX instance was updated from 16.0.8.16 to the latest version of v18 (18.0.3.461) just yesterday.

 

[NickD_3CX]

Can you send me the FQDN of this system in a PM please so I can check?

 

[rldv9281]

Nick solved the issue. It was caused by invalid characters and multiple e-mail addresses is the E-Mail field in the Customer details.

 

[NickD_3CX]

Indeed this happens in rare cases and usually on accounts that may have been around for some years, as over the years the validations and what each field can accept as values has changed.

For anyone else having this issue, which shouldn't be too many, either drop me a PM explaining the situation or contact our CRS team via Live Chat from www.3cx.com who should also be able to help you.