Error importing a custom certificate

[cdutz]

Hi all,

I'm currently trying to resolve the certificate issues I'm having and following the documentation ctrlX_AUTOMATION_self-signed_SAN_certificates_V0_3.pdf (referenced in this forum article: https://developer.community.boschrexroth.com/t5/Smart-HMI-WebIQ-Designer-and/How-to-create-a-certifi...)

I am able to import the "webserver_custom_cert.pem", however when I try to import the "webserver_custom_key.pem" I get an error: 
HTTP client error

Bad request (400) · Error during import. The file content is invalid: webserver_custom_key.pem · 080E0200 · 0C7A0202

Is the document possibly slightly outdated and the settings need to be different for my CtlX Core running on the latest (not officially released) version of the OS?

[Sgilk]

Hi,

There should not be a problem with that process as it pertains to Chrome browsers. Do you have another webserver_custom_key.pem currently installed on the ctrlX CORE? It sounds to me like there is a problem with the generated key. Are you positive you renamed the correct key?

I am in the process of releasing a How-To article on this exact topic to provide certificates for both Chrome and Firefox. I will comment with a link here when it is released.

[cdutz]

Well the article expliained how to create the self-signed certificate and it said:
"Using the web UI of the ctrlX CORE, navigate to the certificate manager (see Settings>Certificates &
Keys>Web Server) and replace files webserver custom cert.pem and webserver custom key.pem
with the similarly named files created in the previous steps".

So I removed the existing ones and started uploading the only two pem files the directory had ... the one worked and for the second I got that error.

[Sgilk · Accepted solution]

Yes, I understand your problem. I'm confident there is an issue with the format of the certificate and key you are using. I just used the same process on a virtual CORE running v2.02 and uploaded the .pem files with no issue.

I'd recommend trying to follow the instructions again and make sure you didn't accidently miss a step or make a typo. Like I said before, there should be an article published shortly that has instructions for Firefox compatible certificates as well. I'll link that here.

[Sgilk]

Here is a link to the Chrome and Firefox compatible process.

How-to-make-an-HTTPS-connection-with-ctrlX-OS-Web-Server