My PDI (Personal Developer Instance) is Inaccessible Due to Certificate Issues

[treewhy]

Hello ServiceNow Developer Community,

I am currently experiencing an issue accessing my Personal Developer Instance (PDI) and believe it is related to a certificate problem. I have tried several troubleshooting steps without success and would greatly appreciate any guidance or assistance.

Troubleshooting Steps Already Taken: I have already performed the following steps, but the issue persists:

1. Tried multiple browsers: Attempted access using Chrome, Edge, and Firefox.

2. Used Incognito/Private mode: Tried logging in via incognito/private Browse modes to rule out browser extensions or cached data.

3. Cleared browser cache and cookies: Cleared all Browse data for all time on all tested browsers.

4. Changed network environments: Attempted access from different networks (e.g., home Wi-Fi, mobile hotspot) to rule out network-specific issues or firewalls.

5. Checked local system date/time: Confirmed that my computer's system date and time are accurate.

Additional Information:

• My PDI has been active and in use recently 

Given that I've exhausted common troubleshooting methods, I suspect the issue might be on the instance side, possibly related to an expired or corrupted SSL certificate for my PDI.

Could anyone in the community offer further suggestions, or is there a known issue with PDI certificates currently? Any help or advice on how to proceed would be greatly appreciated.

Thank you in advance for your time and support.

Sincerely,

Jongsu

 

[Dr Atul G- LNG]

Hi @treewhy 

This has been a known issue since yesterday.

It may be due to planned or unplanned maintenance on ServiceNow's end, which typically isn’t communicated to PDI users.

You have a few options:

1. Wait it out – often, the issue resolves itself after a few hours.

2. Release and request a new PDI – if urgent.

3. Try accessing through alternate methods:

   • Log in to developer.servicenow.com and launch the PDI from there. Some users have reported success using this approach.

   • A workaround suggested by my friend @Nikhil Bajaj9 
     Open developer.servicenow.com in incognito mode, sign in, and launch the PDI. While it may show a security error, scroll down and click the ‘Advanced’ option in the footer. Then, click on the ‘Proceed to <PDI URL> (unsafe)’ link to bypass the warning and access your PDI.

Unless it's urgent, it’s recommended to wait a bit before deciding to release the instance.

[GlideFather]

Hi @treewhy some of the people reported that it worked for them, maybe you want to try in your end