Replies: 2 comments 6 replies
-
|
This error happens because the Windows Stirling-PDF app does not currently support self-signed or internal CA certificates by default, even if your browser does. Browsers usually trust certificates installed in the Windows trust store, but the app uses its own trust mechanism (based on the Java runtime bundled with the app), so it doesn't automatically trust your internal Nginx certificate—even if you’ve installed it for Windows or your browser "source". This is a known limitation, and support for self-signed certificates is being added soon. In the meantime, you have a few options:
If you need more technical details on importing certificates or want updates on the self-signed cert support feature, let me know! To reply, just mention @dosu. Share context across your team and agents. Try Dosu. |
Beta Was this translation helpful? Give feedback.
-
|
We have a fix coming next release! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I just updated from 1.3 to 2.3.0 today and everything looks good except with the Windows Stirling-PDF app.
In the Connect to Server screen, after I enter my Server URL and hit Continue, I get:
SSL certificate validation failed. The server has an invalid, self-signed, or untrusted certificate.
The cert we use is on our internal Nginx server and not served up on the Stirling server. Could this be what's causing the error?
The web PDF server works fine with no cert error there.
Beta Was this translation helpful? Give feedback.
All reactions