4 Answers, 1 is accepted
Hello Ihor,
Reinstalling the Fiddler application does not change the already installed certificate. Instead, delete any pre-existing Fiddler certificates (either manually while using the Windows certificate manager or through Fiddler > Tools > Options > HTTPS > Actions > Reset Certificates) and then generate a new one from Tools > Options > HTTPS > Actions > Trust Root Certificate.
If you are using older certificate generators, then consider changing the default Fiddler's certificate generator with BCCertMaker (Bouncy Castle).
Regards,
Nick Iliev
Progress Telerik
Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.
When you encounter this error, your browser may also display a warning message Your Connection is Not Private. This pop-up serves as a cautionary note about potential security risks, and ignoring it can expose you to “n” number of security vulnerabilities. The different causes can be such as:-
1) Problem with the User’s Computer
2) Browser-related issues
3) Issues with the SSL Certificate Itself
Even many different methods can be there for the error solution, which need to be understood properly in detail.
There are many things that can cause this error. It could be incorrect system date/time or outdated root certificates.
Sync your system time and ensure your system OS is up to date. Also, check for antivirus interference and clear the SSL cache.
This guide on NET::ERR_CERT_DATE_INVALID is also helpful.
This error can also occur outside of Fiddler - in Chrome itself - due to expired SSL certificates, incorrect system date/time, or outdated OS root certificates. Beyond resetting Fiddler's certificates as Nick suggested, it's worth checking your system clock sync and clearing the browser's SSL state.
I found this detailed guide on NET::ERR_CERT_DATE_INVALID quite helpful - it covers both browser-level and server-side fixes step by step.
