When installing a failover PBX using the same FQDN and same HTTPS certificate files from the active PBX I ran into this issue.
The certificate was generated by Lets Encrypt
The web interface does not accept the Elliptic Curve private key file, it throws the following errors:
key file begins with -----BEGIN EC PRIVATE KEY----- and openssl says it is valid
I worked around this by using a previous certificate and key pair that was using RSA and was expired, but the web interface accepted it and the installation continued. Once it was complete I replaced the certificate in the file system with the EC cert and key and restarted nginx and everything works fine. So nginx can handle the key just fine, but the installation web interface is rejecting it. I probably could have just changed the header to -----BEGIN RSA PRIVATE KEY----- since it appears the config tool is only checking the header and doesn't care much about the actual key but not sure how nginx would have liked that.
The certificate was generated by Lets Encrypt
The web interface does not accept the Elliptic Curve private key file, it throws the following errors:
Code:
PbxWebConfigTool web says: Invalid Certificate Key
PbxWebConfigTool.log says: |Dbg|0024| No valid certificate key headerkey file begins with -----BEGIN EC PRIVATE KEY----- and openssl says it is valid
I worked around this by using a previous certificate and key pair that was using RSA and was expired, but the web interface accepted it and the installation continued. Once it was complete I replaced the certificate in the file system with the EC cert and key and restarted nginx and everything works fine. So nginx can handle the key just fine, but the installation web interface is rejecting it. I probably could have just changed the header to -----BEGIN RSA PRIVATE KEY----- since it appears the config tool is only checking the header and doesn't care much about the actual key but not sure how nginx would have liked that.
Last edited:
