-
-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] <setting cloudflares browser rendering to vnc breaks this and wont allow the connection> #38
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
You are layering remote browser on a remote browser I am not entirely sure what you think I can do to fix this, I have never used RBI and you should likely take this up with them. |
ooooh is that what im doing? i figured from the cloudflare documentation is was a streamlined way of passing vnc through there tunnel service |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue is locked due to inactivity |
Is there an existing issue for this?
Current Behavior
im trying to get a better refresh rate as im only getting 20fps on a coomputer not more than 5 miles from my server and I wanted to see if setting the cloudflare browser rendering to vnc would help. insead i get a broken page that says"The origin has unexpectedly closed the connection. Please confirm that the origin is healthy." and in the inspect window I see "WebSocket connection to 'wss://web.blank.com/' failed"
again, this works if i do not set browser rending to anything, but i cannot get more than 20fps
Expected Behavior
the page should load
Steps To Reproduce
going to zero trust in cloudflare and changing "browser rending" from none to VNC
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: