I have four little apps I like to tunnel to, using the backend mode "proxy".
With relatively frequent crashes of the zrok client, I can't always control how they exit 
Sometimes I see a bunch of old shares on api.zrok.io, which I then manually delete.
However, I now have 8 (two sets of my 4 usuals) sitting there that I cannot delete.
What's up with that? What's the best way to get rid of them?
WTF, why can't we embed more than one upload??
Console gives
Failed to load resource: the server responded with a status of 404 ()
{
"data": {
"message": "",
"status": 404,
"stack": "Error\n at p (https://api.zrok.io/static/js/main.55a83dee.js:2:2565605)\n at https://api.zrok.io/static/js/main.55a83dee.js:2:2564909"
},
"error": true
}
Would you be able to gather any more info on the crashes you're experiencing with the client? I would make sure you have the most recent version, but that is a surprise to hear.
Another way you could manage the share cleanup would be with the use of environment. If you disable, then enable again it will cleanup all shares under the umbrella of that environment. You can also give your environment an alias if that's more helpful to track it in the UI.
zrok enable -d your_env_description
We've backtracked the error. The shares were deleted from one resource, but an error prevented them from being deleted from another that controls the display. The lookup to delete relies on the first resource, hence the inability to delete a share that has already been partially deleted.
Can you please give us a complete list of shares in this state for you? We will delete them manually from the system.
