Hosted zrok v1: Reserved Public Share Returns HTTP 502 Bad Gateway Despite Successful Bind and Listener

zrok
1

Hi, I'm experiencing an issue with an existing reserved public share on the hosted zrok v1 service.

My reserved share is:

rkg8oggjh4zg

Environment ID:

PhwLt-JGdr

Backend:

http://127.0.0.1:6767

The local FastAPI application is working correctly and returns HTTP 200.

The zrok API (api-v1.zrok.io) is reachable, and zrok overview correctly lists my environment and reserved share.

When running:

zrok share reserved rkg8oggjh4zg --headless --verbose

The client successfully authenticates, creates a Bind session, connects to the AWS SA-East-1 edge router, and establishes a listener.

However, accessing:

https://rkg8oggjh4zg.share.zrok.io/docs

returns HTTP 502 Bad Gateway with the zrok error page.

The issue was reproduced on September 25, 2026, at approximately 17:25 UTC.

Could you please check the hosted frontend and OpenZiti service/terminator state for this reserved share?

I would prefer not to release the share or disable the environment because the hosted service is currently experiencing issues with these operations.

Thank you!

2

Just following up here to let you know in case you haven't seen.. Please follow that thread for updates

3

Hi. Just following up here too. I made this post on the pinned topic but just FYI here to make sure I cover all the bases... [duplicating the summary of that post here follows]

If you had stuck sessions that cannot be deleted, I'm told you should now be able to delete them on your own again. I don't have any I can test myself personally but if someone does and if they could post a follow-up here with success (or failure but let's hope not) that would be appreciated.

Thanks again for reporting the issues and bearing with us while we make zrok better!