# Zrok.io Account Issue(?)

**URL:** <https://openziti.discourse.group/t/zrok-io-account-issue/6161>\
**Category:** Uncategorized\
**Created:** [October 4, 2026, 2:45am UTC](https://openziti.discourse.group/t/zrok-io-account-issue/6161 "2026-10-04T02:45:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tenuto886](https://avatars.discourse-cdn.com/v4/letter/t/7cd45c/32.png) [@tenuto886](https://openziti.discourse.group/u/tenuto886)\
**Post date:** [October 4, 2026, 2:45am UTC](https://openziti.discourse.group/t/zrok-io-account-issue/6161/1 "2026-10-04T02:45:10Z")

</div>

Hosted [zrok.io](http://zrok.io) account issue: `zrok2 share public` consistently returns HTTP 429.

Client: zrok2 v2.0.7 `[79300f73]`

`zrok2 create name munkee-tenuto886` succeeds, but:

`zrok2 share public http://127.0.0.1:8771 --name-selection public:munkee-tenuto886 --headless`

returns:

`[POST /share] share (status 429)`

The account currently has only two active public shares, well below the hosted free-tier limit. Could you please check whether this account is stuck in the bandwidth-limit journal / limited state described in the v2.0.7 fixes, and clear or release that state if necessary?

---

<div class="post-metadata">

**Author:** ![tenuto886](https://avatars.discourse-cdn.com/v4/letter/t/7cd45c/32.png) [@tenuto886](https://openziti.discourse.group/u/tenuto886)\
**Post date:** [October 4, 2026, 9:07am UTC](https://openziti.discourse.group/t/zrok-io-account-issue/6161/2 "2026-10-04T09:07:24Z")

</div>

d:

Both the Windows host and Raspberry Pi are now running zrok2 v2.0.7 `[79300f73]`.

The Windows agent had accumulated 31 transient `err_*` retry entries. All were successfully released and `zrok2 agent status` is now empty/clean.

Both local Botacon backends are healthy:  
`127.0.0.1:8767` — TCP succeeds  
`127.0.0.1:8768` — TCP succeeds

The Pi agent also starts cleanly under systemd with v2.0.7 and loads zero stale shares.

Hosted account usage is only ~185 MB with two controller-listed public shares, but new public share creation continues to return HTTP 429. The existing controller-listed Botacon endpoints currently return zrok “bad gateway” because no active agent share is attached.

Given the v2.0.7 changelog entry concerning accounts remaining in the bandwidth-limit journal after usage recovers, could you please check the hosted controller/account journal state and manually