PDI got 502 Bad Gateway while developing, instance now offline
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wednesday
Hi,
My Personal Developer Instance suddenly returned a 502 Bad Gateway error while I was actively developing.
This started around 4 PM JST today when I refreshed the page to see updated data.
Now in the Developer Portal the instance shows as "offline", and there is no Wake up / Start / Resume option available.
Unfortunately, I had ongoing development and some changes were not saved yet, so I am quite worried about the data.
I saw some other Community posts mentioning that for 502 errors there is nothing users can do except wait, so I wanted to ask:
- Is there any ongoing maintenance or known issue right now?
- Has anyone else experienced the same problem today?
- Is waiting the only option in this situation, or can the instance be checked / restored from the backend if possible?
The instance has been actively used in the past couple of weeks.
Any guidance or help would be greatly appreciated.
Thank you very much.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi @金晶陶,
you inspired me to create this: [GF#5] PDI in Offline state: Resolving Error 502
No AI was used in the writing of this post. Pure #GlideFather only
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wednesday
The instance is back online now.
After the issue occurred, the Developer Portal showed unscheduled maintenance,
and the instance became available again once maintenance was completed.
Thank you all for your input.
