I'm getting persistent errors when trying to create a public share, alternating between a context deadline exceeded and a 500 Internal Server Error, across multiple retries over more than an hour (including after a device restart and after deleting a duplicate/stale environment from my account). Environment: - envZId: f-N1r2u7jK - Client: zrok2, Windows 11 - apiEndpoint: https://api-v2.zrok.io Command: zrok2 share public localhost:5678 Errors seen (alternating across consecutive retries): [ERROR]: unable to create share (unable to create share: Post "https://api-v2.zrok.io/api/v2/share": context deadline exceeded) [ERROR]: unable to create share (unable to create share: [POST /share][500] shareInternalServerError "") Troubleshooting already done: - Confirmed basic HTTPS/TLS connectivity works fine (curl -v https://api-v2.zrok.io returns 200 OK) - No proxy env vars set - zrok2 status shows clean config, valid account token and envZId - Had a second, stale environment (created Nov 2025, different device) registered on the same account with an old share attached — deleted it via the myzrok.io console - Issue persists identically after that cleanup, and after a full machine restart - Also tried creating a share with a reserved name (-n) — same alternating errors Would appreciate help figuring out if this is account-specific or a broader service issue right now.
Judging by the number of threads created on this topic over the past month, this problem is affecting many people and occurring very frequently. I don't know if the developers are aware of the issue.
+1, hitting this exact same alternating pattern today (2026-09-24) — same two errors:
[POST /share][500] shareInternalServerError ""
and
unable to create share: context deadline exceeded
Same as described above: retries alternate between the two, confirmed status.zrok.io shows all green, DNS resolves fine, client is on latest (v2.0.4), restarted the local agent fresh — same errors persist regardless. Tried on multiple different reserved share names on my account, not just one.
Given another user reported the same exact signature 6 days ago, this looks like a recurring issue on the hosted /share endpoint rather than anything account or client-side. Happy to share my envZId or timestamps if it helps correlate on your end.
I shared this with them. They simply aren't responding. It seems the problem is critical and unsolvable.
Thanks for the report. We're aware of the issue and are preparing updates to the service.
I'm facing the exact same issue.
zrok 1.1.11: zrok enable still works, but creating a share fails:
[ERROR]: unable to create share (unable to create share: [POST /share][500] shareInternalServerError)
zrok2: enabling an environment fails entirely:
the zrok service returned an error: [POST /enable][500] enableInternalServerError
there was a problem enabling your environment!
you are trying to use the zrok service at: https://api-v2.zrok.io
Both requests return an HTTP 500, which points to a server-side problem rather than a client misconfiguration. I can provide more details (OS, exact commands, timestamps) if that helps.
Thanks for confirming, smilindave26 — good to know it's on your radar.
In the meantime, for anyone else stuck: denis.mladenek's workaround above worked for me today. Release the environment via api-v1.zrok.io (took two attempts — first one also 500'd, second went through), then locally zrok2 disable → zrok2 enable <account token>, then re-share as normal. All my previously-reserved share names survived the release and worked again immediately after re-enabling, so nothing was lost — just needed the environment reset.
Hope that helps tide people over until the service update lands.
Just following up here to let you know in case you haven't seen.. Please follow that thread for updates
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!