trying with a fresh token and I get 500 error from api:
status page says you're experiencing issues: https://status.zrok.io/
same situation for me
Sorry for the issues & thank you all for reporting. https://status.zrok.io has been updated and we are working to resolve the issue.
My hosted account is getting 500s on share, disable, enable, delete. Not sure if related, but timing is right.
account email joe@zerogcapital.com
- env ZIDs d0SluOxo7j + EFX9h1zo7j
- works: overview, create name
- fails: POST /share, /disable, /enable empty 500
- zrok2 delete environment … --force → same disable 500
- earlier missing Ziti service 40prmKmCLjDebxXFSOSFo8 for joezge
- clients: zrok 1.1.11 + zrok2 2.0.4
- links: Hosted: dual environments; POST /share /disable /enable return empty 500 (account stuck) · Issue #1265 · openziti/zrok · GitHub
@emoscardini I regenerated my token and destroyed my env. I've enabled with the new environment now when I try to reserve with same unique name as before I'm getting "409 Share Conflict". Could my old env/token be in a bad state and have not cleaned up it's unique names during the outage?
ok I've found the release button on the original unique named release. I'll try that.
I released the machine...and we're back in business
I've been getting those same errors when trying to release via the UI. How were you able to get the resource released?