Hello! Could someone please explain the difference between zrok share and zrok reserve commands? My use case for context: there is a docker container I need to expose under the zrok-managed domain (via subdomain). When I run zrok share public --backend-mode proxy https://127.0.0.1:8080 --verbose --insecure (the insecure flag needs to be there since the SSL is managed by the app), it works fine, except that I can't specify the subdomain - it is generated automatically and prevents the cert validation. When I run zrok reserve public --backend-mode proxy --unique-name <subdomain> https://127.0.0.1:8080 I can't specify the insecure option, but moreover, I got 404 from Zrok when I try accessing it. What's the difference between the two that I can't find out? Thanks in advance!
The zrok reserve command is used to "lock" your share name so that you can use it many times.
Once you run zrok reserve, you need to run zrok share reserved <shareToken> to actually serve the share. The zrok reserved command just creates the reservation for you.
Thanks a lot for a quick response Michael! I appreciate it
And the --insecure flag is available on the zrok share reserved command. That's a property of the local HTTPS client, it tells it to ignore insecure (self-signed) certificate issues.
Have you seen error ERROR zrok/endpoints/proxy.newReverseProxy.func2: error proxying: tls: first record does not look like a TLS handshake when trying to share docker workload with zrok public share? I've tried both self-hosted solution and managed one and the result is the same. For the context - I'm trying to spin up a nextcloud:aio instance