I have old hp thinpro 7.1 linux clients out there in the wild and when I renewed my cert from ssls.com for the vpx, they werent able to connect any longer, just a generic cert error. i should also add these are at users homes and i have no remote access to them at all so i test all changes from my home. i tried importing the CA into my test device here at home (t520), but it doesnt seem to be taking, so here's my question. if i add the CA to the NS virtual server which it currently does not have, (the vpx just has the server cert binded), would that solve my issue perhaps? I cant test any changes will after hours, so i'm trying to get a game plan together tonight...luckily my cert doesnt expire for 27 days..................................................Edit - I just found this so the CA won't help me it seems like, probably why it was never setup and I should add PC's had no issues connecting to the NS like the t520s, did------------------------are using a certificate issued by a trusted public CA (like Verisign or Let's Encrypt), you might not need to explicitly bind a CA certificate to the virtual server. The server certificate itself (issued by the CA) is sufficient for establishing a secure connection

Did you link the intermediate cert to the newly installed SSL certificate? And do your Linux client trust the CA/Issuer?

thanks for your reply, i wont like, i'm really bad with certs. here's what i did. i created a new rsa key and new csr, uploaded the csr to ssls.com, got a new cert, uploaded to vpx, and updated the existing cert with the new one i received. web clients work just fine, i can see the new cert expires in july 2026 so i know it worked properly.

I have had this issue before, you should be able to send the new intermediates and roots to the thin clients with the deploy tool.

i'm working with hp t520 thin clients on thinpro 7.1 i need to mess around with them, but at least for now, ssls.com gave me a domain cert to get me buy for another year