# Stuck environment returning 500 error

**URL:** <https://openziti.discourse.group/t/stuck-environment-returning-500-error/6104>\
**Category:** zrok\
**Created:** [September 21, 2026, 5:18pm UTC](https://openziti.discourse.group/t/stuck-environment-returning-500-error/6104 "2026-09-21T17:18:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kurokatana94](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/kurokatana94/32/4348_2.png) [@Kurokatana94](https://openziti.discourse.group/u/Kurokatana94)\
**Post date:** [September 21, 2026, 5:18pm UTC](https://openziti.discourse.group/t/stuck-environment-returning-500-error/6104/1 "2026-09-21T17:18:51Z")

</div>

I got a stuck share after few attempts to restart it, I ran zrok2 disable in my terminal, which removed the environment locally. But on the web console it's still there. I tried to refresh the account token few times as it seems to be a workaround, but it didn't do nothing and every time I try to release it, I just get an error 500.  
Can you please help me? My environment is `DESKTOP-JJN5P7E\Kuro@DESKTOP-JJN5P7E`

 ![image](https://global.discourse-cdn.com/free1/uploads/netfoundry/original/2X/5/513b8b0f6b4755b29f12c2f5ad70c4d346c15ea2.png)

---

<div class="post-metadata">

**Author:** ![sistemas.corona.xalapa](https://avatars.discourse-cdn.com/v4/letter/s/c5a1d2/32.png) [@sistemas.corona.xalapa](https://openziti.discourse.group/u/sistemas.corona.xalapa)\
**Post date:** [September 21, 2026, 5:39pm UTC](https://openziti.discourse.group/t/stuck-environment-returning-500-error/6104/2 "2026-09-21T17:39:20Z")

</div>

I got the same... it is happening since friday.. There's a trouble with zrok server suppose. I hope they resolve soon

---

<div class="post-metadata">

**Author:** ![TheLumberjack](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thelumberjack/32/113_2.png) [@TheLumberjack](https://openziti.discourse.group/u/TheLumberjack)\
**Post date:** [September 30, 2026, 1:22pm UTC](https://openziti.discourse.group/t/stuck-environment-returning-500-error/6104/3 "2026-09-30T13:22:22Z")

</div>

> [@Stuck zrok2 account – enable and web console release both return 500 error](https://openziti.discourse.group/t/stuck-zrok2-account-enable-and-web-console-release-both-return-500-error/6041/21):
>
> I have been told by the team other zrok updates are due to come out today. We'll follow up in a bit and hopefully these problems will be fixed. Thanks for letting us know

Just following up here to let you know in case you haven't seen.. Please follow that thread for updates

---

<div class="post-metadata">

**Author:** ![TheLumberjack](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thelumberjack/32/113_2.png) [@TheLumberjack](https://openziti.discourse.group/u/TheLumberjack)\
**Post date:** [September 30, 2026, 7:19pm UTC](https://openziti.discourse.group/t/stuck-environment-returning-500-error/6104/4 "2026-09-30T19:19:57Z")

</div>

> [@Stuck zrok2 account – enable and web console release both return 500 error](https://openziti.discourse.group/t/stuck-zrok2-account-enable-and-web-console-release-both-return-500-error/6041/23):
>
> Hi everyone. If you had stuck sessions that cannot be deleted, I'm told you should now be able to delete them on your own again. I don't have any I can test myself personally but if someone does and if they could post a follow-up here with success (or failure but let's hope not) that would be appreciated. Thanks again for reporting the issues and bearing with us while we make zrok better!

Hi. Just following up here too. I made this post on the pinned topic but just FYI here to make sure I cover all the bases... [duplicating the summary of that post here follows]

* * *

If you had stuck sessions that cannot be deleted, I'm told you should now be able to delete them on your own again. I don't have any I can test myself personally but if someone does and if they could post a follow-up here with success (or failure but let's hope not) that would be appreciated.

Thanks again for reporting the issues and bearing with us while we make zrok better!
