- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2025 10:46 PM
Hello everyone,
This is my first post here—thanks for having me!
Problem:
My PDI had a perfectly valid Entrust wildcard SSL certificate and showed a green lock icon. Then I added a small server-side script to a Record Producer. After that change, I suddenly started seeing the certificate as expired (expired May 13, 2025) in some browser sessions—even though I hadn’t changed any SSL settings.
When navigating to https://dev... I now see since yesterday a “Not secure” warning that states:
“The connection to this site is not secure. You should not enter any sensitive information such as passwords or credit card numbers on this site, because it could be stolen by attackers.”
I tried refreshing the instance via the Developer Portal, but that didn’t fix it.
I cleared my browser cache and pdi cache, used Incognito mode, and made sure I was on https:// , but the issue persisted.
I know it’s “just” a PDI, but I’m keen to understand and fix this. Any advice or shared experiences would be greatly appreciated!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2025 10:50 PM
It is happening as ServiceNow SSL certificate is expired so it is navigating you to http:// rather than https://. Many other people are affected by this and hope it will be fixed soon by ServiceNow.
Work Around: - Open developer.servicenow.com in incognito mode and sign in and launch PDI. It will display error, but it will also display Advanced option towards footer. Click on it and on next screen click on "Procced <PDI URL> unsafe" link and you will be able to access your PDI.
Regards,
Nikhil Bajaj
Regards,
Nikhil Bajaj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2025 10:47 PM
Hi @nicolasande
It’s a known issue today. You can either wait or release the PDI and request a new one.
The reason could be planned or unplanned maintenance on the ServiceNow side, which is usually not notified to PDI users.
So, it’s better to wait for a few hours before deciding to release the instance.
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2025 12:46 AM
I sincerely hope that ServiceNow learns from this incident and implements Let's Encrypt/ACME to get TLS certificates for PDIs.
If this answer was helpful, I would appreciate if you marked it as such - thanks!
Best
Daniel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2025 01:08 AM
I'm expecting same.
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2025 10:50 PM
It is happening as ServiceNow SSL certificate is expired so it is navigating you to http:// rather than https://. Many other people are affected by this and hope it will be fixed soon by ServiceNow.
Work Around: - Open developer.servicenow.com in incognito mode and sign in and launch PDI. It will display error, but it will also display Advanced option towards footer. Click on it and on next screen click on "Procced <PDI URL> unsafe" link and you will be able to access your PDI.
Regards,
Nikhil Bajaj
Regards,
Nikhil Bajaj