`zrok` hosted service — known 500 errors on enable, environments and shares (investigating)

zrok
1

We know about the 500 errors on the hosted zrok service, and we're working on it.

You don't need to open a new topic — this one will be updated as we make progress.

What's affected:

enabling an environment, deleting or releasing an environment, and creating or deleting shares can all return 500. Some accounts also see repeated 429 rate-limit errors. You can end up with stale environments or shares you can't clear yourself.

If you're stuck:

Please reply in this topic instead of starting a new one.

What's going on:

a handful of intertwined issues in our rate limiters and account cleanup, plus conflicts that arise from mixing zrok and zrok2 environments in the same account. We're preparing service updates and fixing individual accounts as we go.

Status: investigating

We'll update here as the service updates land, and again when it's resolved.

Thanks for using zrok, and sorry for the disruption — this is a bug on our side, not something you did.

3

root@fb69af4ef628 and root@d0dc3a3ed204 environments have hung and won't delete. Everything was working fine yesterday, but today they’ve hung again.

4

I am stuck at root@c0eb6e92e17b

5

I am stuck since 18:33 CET root@nucleus and root@piedpiper take care the good nucleus one is one created 23/2/2026. This is the one to be restablished

6

still stuck on this on varius roots: root@0dbd136a068d, root@c30db86e70da, root@5279fc25af34 and root@34086ac49228

[ERROR]: unable to create share (unable to create share: [POST /share][500] shareInternalServerError "")
and delete
An error occurred releasing your environment 4wDayZ47IK!

7

Please delete: grifqialdi@*******.**.localdomain / EnvZId ekdXFXicjK (api-v2.zrok.io, created 2026-09-14, IP 193.204.135.241)

Symptoms: POST /share, /disable, /enable all 500 (even ephemeral/private + fresh enable token). zrok disable cleaned local but server orphan remains. Web UI delete also fails.

Thanks!

8

I'm also stuck, enabling environment, accessing shares all return 500 Internal Error :frowning:

9

Same here since 18:13 CET. Some moments it started to work again during 1 hour and again failing with 500 bad gateway and no way to start up services. A real big issue. Considering to move away from zrok

10

We're experiencing an issue and are working on it. We will update https://status.zrok.io as we make progress.

11

Finally I have decided to use frpc/frps and throw away this service using a VPS in aws. Two long blackouts in less 6 months is not acceptable

I have scripted moving +10 complex confs including ws and streaming services but it worths , everything up and running in 3 hours , and tested

Stay safe and don’t wait to much to explore alternatives.

12

Hi My Zrok reserve share is not creating proxy its getting timeout any issues on the zrok internal side