PDI dev315836 offline for 5+ days - TLS Bad Request error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
My Personal Developer Instance dev315836 has been offline for more than 5 days.
When I try to open the instance, I get:
Bad Request - This combination of host and port requires TLS.
I have already tried refreshing/waking the instance from the Developer Portal, but the status still shows Offline.
The instance contains important Change Management configuration and existing Change Requests that I need to preserve, so I do not want to release or reset it.
Please help restore the existing PDI without data loss.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @amitachavan
this might help you
https://www.servicenow.com/community/developer-forum/my-pdi-dev183008-is-offline/td-p/3600623
This helps other users find accurate and useful information more easily
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
PDIs don't come with any support from ServiceNow.
So the only option for you is to wait.
💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏
Ankur
✨ Certified Technical Architect || ✨ 10x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello @amitachavan ,
Don’t worry, buddy. This has been happening with multiple users these days. My instance also went offline after some time, but it came back online on its own.
You just need to wait for some time and then try logging in again. In rare cases, the instance may not come back online. If it still doesn’t come back after waiting for a while, you can release the instance and request a new one. Always remember if you are working on business requirement in pdi then always take its backup even work is done or in progress , so if unfortunately pdi get offline it will not affect your work .
If this helps you then mark it as helpful and accept as solution.
Regards,
Aditya
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @amitachavan
I’ve been using my PDI without any issues since this morning, but I’ve noticed several posts in the ServiceNow Community today reporting PDI failures or unavailability. Based on the responses and recent experience, this appears to be a known issue affecting multiple users.
A few points to consider:
- There is currently no dedicated support available for PDI, so there isn’t much we can do from our side while the issue is ongoing.
- If you can wait, I would recommend waiting a little longer. Some users have reported their PDI coming back online after a few hours, although there is no guaranteed timeframe. Based on recent reports, it may take anywhere from a few hours to 1–2 days.
- You can release the current PDI and request a new one, but be aware that you will lose any data or configuration stored in the existing instance.
There have been around 3–4 community posts today about PDI failures or unavailability, so you’re not the only one experiencing this.
The issue might be related to ServiceNow's ongoing transition to a new release and the rebuilding/provisioning of PDIs, which could be contributing to instances being temporarily unavailable.
For now, patience is probably the best approach. If you have important data in the current PDI, I would avoid releasing it and give it some more time. If there is no important data and you need a working environment urgently, requesting a new PDI could be an option.
Backup and restore you PDI data
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
******************************************************************************************
