My Personal Developer Instance refuses to start

gersonfreir
Tera Contributor

My PDI (Personal Development Instance) is offline, and even after I attempt to start it and click the refresh button, it remains offline. When I try to access it via the URL, a "502 Bad Gateway snow_adc" error appears.

3 ACCEPTED SOLUTIONS

Tanushree Maiti
Tera Patron

Hi @gersonfreir 

 

 

When I got  502 Bad Gateway error 4 months back for few hours ,after waiting for some time, the issue resolved itself automatically.

You can also try accessing it again after regular intervals. PDIs recover automatically when background tasks or refreshes finish.

 

 

If the error persists past 4-5 day, you can think of to  release the broken instance from your developer portal and request a brand new PDI.

 Note: Releasing an instance deletes all previous data stored on it

 

Please note , there is no support available for PDI.

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti

View solution in original post

Simon Hendery
Tera Patron

ServiceNow developers deserve better than the current PDI infrastructure mess they being forced to put up with.

 

I'd appreciated your support liking, sharing or commenting on my recent LinkedIn post (below). It's time to get the company to listen and take action .

 

https://www.linkedin.com/feed/update/urn:li:activity:7516892562805293058/

View solution in original post

kh_safal
Administrator

Hi @gersonfreir,

We checked with the PDI team and learned that new software installations across their infrastructure have temporarily taken several PDIs offline. This could explain why your instance isn't starting. The affected instances will remain unavailable until the installations are complete.

View solution in original post

4 REPLIES 4

Tanushree Maiti
Tera Patron

Hi @gersonfreir 

 

 

When I got  502 Bad Gateway error 4 months back for few hours ,after waiting for some time, the issue resolved itself automatically.

You can also try accessing it again after regular intervals. PDIs recover automatically when background tasks or refreshes finish.

 

 

If the error persists past 4-5 day, you can think of to  release the broken instance from your developer portal and request a brand new PDI.

 Note: Releasing an instance deletes all previous data stored on it

 

Please note , there is no support available for PDI.

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti

Thanks a lot! I will wait

Simon Hendery
Tera Patron

ServiceNow developers deserve better than the current PDI infrastructure mess they being forced to put up with.

 

I'd appreciated your support liking, sharing or commenting on my recent LinkedIn post (below). It's time to get the company to listen and take action .

 

https://www.linkedin.com/feed/update/urn:li:activity:7516892562805293058/

kh_safal
Administrator

Hi @gersonfreir,

We checked with the PDI team and learned that new software installations across their infrastructure have temporarily taken several PDIs offline. This could explain why your instance isn't starting. The affected instances will remain unavailable until the installations are complete.