Wildcard cert on Terminal Server

[pureobscure]

Hi,

I’m trialing NoMachine Terminal Server before buying a few licenses. I’ve been trying (unsuccessfully) to use my company’s wildcard cert for the web interface and NX connections. Regardless of what I do I am getting errors that keep the web interface and NX connections from working properly.

Anyway, I just noticed in the knowledgebase page (https://www.nomachine.com/DT03O00127) there’s a small item that says:

CA certificates will be supported with the implementation of https://www.nomachine.com/FR02L02810

It’s a pretty old knowledgebase entry. Has the ability to install CA certs been implemented?

Thanks!

[irek]

Hello pureobscure,

currently for a Web session you can use self-signed certificates, as explained in:

https://www.nomachine.com/DT03O00127#3

CA certificates are effectively not supported yet.

[Xoltus]

Hi *,

I am afraid, I need to disagree with irek. At the moment, I evaluate NoMachine Terminal Server as well and I successfully set up the web interface using one certificate from LetsEncrypt. However, this cert is not a wildcard certificate.

What errors do you get? Have you added the chain certificate as well?

Best,
Lars

[irek]

Hello Lars,

not sure if you’re referring to the certificate for the web server. If so, edit the nxhtd configuration file to point to the new certificate.

If, on the other hand, you’re referring to the certificate for NX authentication, it still has to be implemented

[pureobscure]

Thanks everyone for the help.

I was trying to do nxhtd and nx at the same time. When I focused only on nxhtd I was able to use the wildcard cert successfully.

[Britgirl]

OK pureobscure! Thanks for letting us know 🙂

[Author]

Posts