I have deployed sentry on my linux VM and accessed using ZROK. I am receiving this error on the zrok terminal. Attatched below
Hi @sbansal793 
Does the Sentry app function normally when the "context canceled" error is occurring in the zrok share TUI?
The app is functioning normally even during this error. Error is displaying in zrok share TUI
Which version is running zrok share?
zrok version
The version is v0.4.30 [96bfe62c]
Great. That's the latest release.
Do you get the same error if you include the --insecure flag in your zrok share command? That will tell zrok to skip verifying the Sentry app's server certificate, if the backend is connecting with TLS.
1 Like
@qrkourier I am running without TLS. I will try running with an --insecure flag.
Hi. I just got the same problem too when I try to use my Open Webui from Zrok api.
I tried to run my website with the --insecure flag and it still gave me this error.
Before I use this command flag, I got 2 of this error but now I seem to just get 1 instead.
Welcome, @DIE020HARDZ!
You're seeing this error message when you run zrok share public, correct?
ERROR zrok/endpoints/proxy.newReverseProxy.func2: error proxying: context canceled
Also, the reporter that started this thread saw this error, but their share functioned normally, despite the error. Is your share working normally like theirs was, or are you troubleshooting a malfunction?
Are you sure you need to say zrok share public --insecure? That option is needed when your proxy target URL starts with https://, but the server has an untrusted certificate, usually a self-signed cert.
For example,
zrok share public --insecure https://my.private.server.internal
Hi. I also got the same problem when I use Zrok with beef. The beef is not hooking the browser and giving this error. please help me. I have also attached the screenshot.
Welcome to the forum and this wandering thread!
We're discussing an undiagnosed problem, possibly three unrelated issues, encountered by users of zrok share public --backend-mode proxy.
You're using Beef. Is this the same Beef you are using?
Beef can be configured with or without a TLS listener, I take it. Is your Beef listening for TLS connections, non-TLS connections, or both?
Are you sharing a TLS listener with zrok like this?
zrok share public --backend-mode proxy https://beef.internal
yes this is the same beef i am using. I don't know what TLS listener is.
I just run beef by using "sudo ./beef" command.
and i am not using --backend-mode before the link.
Instead i am using: " ./zrok share public http://127.0.0.1:3000
"
Cool. FYI, --backend-mode proxy is implied if you don't specify another mode.
Thanks for clarifying you're sharing Beef's non-TLS listener, i.e. an http:// URL (not https://).
Can you verify that http://127.0.0.1:3000/ is a valid URL on the same computer where you are running zrok share public? Specifically, if you access this URl with cURL or a web browser, are you redirected to https:// or is Beef available at the non-TLS http:// URL?
I get this page when i visit "http://127.0.0.1:3000/ "
how to check if beef is available at the non-tls "http://" URL
Hello. Please reply? I am working on a project that I need to complete. And I need your help