logs:
35.222.246.110 - - [21/May/2025:12:01:30 +0000] "GET / HTTP/2.0" 404 19 "-" "-" 562 "-" "-" 0ms
please Ziti Family help me with this soon
Hi @AshZi03, a 404 like this generally makes me think you have successfully connected to the remote service and it returned a 404. Are you certain your remote services is working properly? Right now to me, this seems like zrok is working correctly but the target serice at localhost:5000 is not
Sir i tried with actual port 5002 as well, the service was running on 5002 but still i am getting 404 error
i even tried with "zrok share public --backend-mode web ." but faced same error
Are you using zrok 1.0.3+ ? can you run zrok test canary public-proxy and see what it reports?
You can run zrok test endpoint and then zrok share public localhost:9090 in a different terminal and confirm zrok is working.
See what those get you?
version : v1.0.4
zrok test canary public-proxy
[ 0.001] FATAL main.(*testCanaryPublicProxy).run: this is a dangerous canary; see canary docs for details on enabling
zrok test endpoint
the above was stuck no output
zrok share public localhost:9090
[ 0.228] INFO sdk-golang/ziti.(*listenerManager).createSessionWithBackoff: {session token=[821e4741-609b-4d40-9368-3e84a0534fc3]} new service sessio
service starts but no results
i checked all and above are the logs
i got same output after sharing port 9090 404 not found when clicked on url provided
Hi there 
I think you're setting up self-hosted zrok and trying to get a public share working for the first time.
You can reach the zrok console, and that means the zrok controller is reachable through your HTTPS reverse proxy. I assume you were able to do zrok enable too because they use the same public API.
Your zrok public frontend is not correctly configured in your HTTPS reverse proxy as a virtual server, upstream, etc. You might be using Caddy, Traefik, Nginx Proxy Manager, etc. Check the config and logs where you have configured your wildcard cert. The requests are not being proxied to the zrok-frontend!
Ahh you were right
DNS name was not configured correctly and after correcting that next error was regarding internal server error 500 so for that i needed to check if i have used https anywhere inside and i found in frontend url and after removing it , its working
Thank you for your guidance and help @qrkourier && @TheLumberjack
@qrkourier @TheLumberjack
just to make myself clear is zrok same as ngrok ?
and will it work like directing to other url ? not the token url for the actual url
You can use zrok like ngrok.
zrok share public 8080
This creates a public URL for http://127.0.0.1:8080.