Hosted zrok2 enable returning 500 / cannot release shares in API console

Uncategorized
1

Hello,

I'm using the hosted zrok service (api-v2.zrok.io) with zrok2 v2.0.4 on Windows 11. My environment is currently stuck and I'm unable to enable or release anything.

Symptom 1 — zrok2 enable fails: Running zrok2 enable --headless <my-account-token> returns:

the zrok service returned an error: [POST /enable][500] enableInternalServerError

Other attempts have also returned:

Post "https://api-v2.zrok.io/api/v2/enable": context deadline exceeded

Symptom 2 — Cannot release shares in the API console: In the zrok API console, I have stale shares/environments that I cannot delete. Any delete/release attempt returns a 500 error.

What I've verified locally (all correct on my side):

  • zrok2 version → v2.0.4 [6ff92039] (the newest public release)
  • apiEndpoint → https://api-v2.zrok.io (matches the official docs)
  • Account token is valid and in the correct format
  • Local network/connectivity to api-v2.zrok.io works fine

This appears to be a server-side issue — it looks like a stale/orphaned environment tied to my account is stuck on the hosted backend, which is blocking both enable and share release. I've seen this matches a known report in the forum.

Request: Could you please reconcile/delete the orphaned environment and its associated OpenZiti identity/policies from the hosted backend for my account?

I can provide my account email privately if needed. Happy to share logs or run any diagnostics on your end.

Thank you.

2

It appears that since this message was posted, there have been enablements and shares created. Are you working now? And if so, can you report what the issue was?

3

Hi Mike,

Thanks for following up!

I managed to get unblocked after generating and rotating through multiple account tokens. After several attempts, one finally succeeded in creating a clean environment and allowing zrok2 enable to complete.

It seems like the account was hit by a stuck or orphaned identity/environment state on the backend—triggering the 500 enableInternalServerError—until a new token generation finally cleared the deadlock.

Since I went through multiple tokens during the process, could you check if there are any orphaned environments or stale identities left behind on my backend profile that need to be purged? Other than that, everything is fully operational now.

Thanks again for reaching out!