My hosted zrok2 environment is permanently deadlocked on the backend database.
When I try to run the client executable locally, I get the following error:
[POST /enable][500] enableInternalServerError
I logged into the web API Console dashboard to manually delete and release the stale environments and shares, but the website throws a "request failed (500)" server error as well.
Please completely purge and reconcile the dangling environment mapping, stale OpenZiti resources, and deadlocks tied to my account profile so I can complete a clean configuration reset.
I can provide my account email address privately to the responding admin. Thank you!
I have exactly the same problem. For months, I could start a share with a reserved subdomain with
".\zrok2 share public -n public:mysubdomain http://localhost:8080 --backend-mode proxy"
but now that gives
"unable to create share (unable to create share: [POST /share][500] shareInternalServerError "")"
as an error message.
Entering ".\zrok2 list shares" does not show hanging shares / tokens, so that's not the problem. It must be on the server side.
Even more confusing, on "https://myzrok.io/dashboard", sent and received data of the last days is shown as 0 GB, which is incorrect. It's as if my whole account has vanished.
It's kind of frustrating that such a good and transparent service is totally hobbled by such a basic problem. I really hope this gets fixed soon. I would never use Cloudflare instead, because I could never agree to them inspecting every package I transfer.
Me too, on hosted zrok (api-v2.zrok.io) with zrok2 v2.0.4 on Linux (WSL2), since about 2026-09-26 05:30 UTC.
Every share public attempt returns [POST /share][500] shareInternalServerError "", both with a reserved name (-n public:) and without one. I tried it through the agent and with --subordinate directly.
Before that, the controller still listed a share holding my reserved name with nothing running behind it, so the public URL returned 502. The agent's retries against it failed with 409 shareConflict "name ... is already in use by another share". zrok2 delete share removed it, and after that every create attempt gets the 500.
api-v2.zrok.io itself responds, and zrok2 overview and list names work. Only creating a share fails.
I can send my account and environment details privately if that would help with the logs.
Same here, i strongly feel its permanent or forever error (due to most probably using their services "TOO MUCH") I used their services for one day and next day the same thing isn't working, its been a few days of halt in my work... I will likely switch to other providers, would suggest same instead of waiting for their fix...
Edit: next day after this comment, it worked or you can say fixed. Thanks!
Same for me, I've been stuck for more than a week, which slowed down considerably my work.
I've see the last update on the status page has been 3 days ago, any concrete idea on how long could this take to resolve?
I’m also getting the error [POST /enable][500] enableInternalServerError, even though update 2.0.5 was released yesterday.
On top of that, I can't delete the old, corrupted environments (root@d0dc3a3ed204 and root@fb69af4ef628). I don't know what to do about this; it's really disheartening and frustrating.
Yoo, am getting 502/bad gateway is it because of the performance issues? i looked into my locally hosted zrok and other things i am running, it functions smoothly.
Hi everyone, thanks so much for continuing to report problems here. We have had numerous problems all stack up late last week. People were working through the weekend to try to recover but we ended up hitting some novel problems we just hadn't seen before so it has taken longer than anyone wanted. We thought we had fixed the root problem but any time software changes, sometimes it exposes other issues.
We are continuing to work on zrok-related updates, if you're watching the repo you'll see those as they come in and we are continuing to try to resolve the remaining issues.
Again, we apologize for this disruption, we know it's painful but we appreciate you sticking with us as we sort through this.
Please continue to let us know when you're having troubles so we can get a gauge on how many people are hitting problems but don't be offended when we don't reply. It's only because we don't have anything we can actually --do-- at that moment other than keep working on it (which we are doing)
Small addendum:
Services do seem to be working fine for most/many users but some people do continue to hit issues. We are monitoring these as best we can to resolve them fully.
Update: I was able to re-enable the env on my agent machine, so that's good. However in https://api-v1.zrok.io/ I still also see old env - it is not possible to delete it from there, it shows
An error occurred releasing your environment t1NQ5P***p!
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
