Hosted 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?
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