Skip to content
Discussion options

You must be logged in to vote

To me it sounds more like a deployment issue, rather than code issue. The error handling when something is not set up properly is not the best, but it should work when setup properly. Make sure the string that is assembled using --screen-ws-url-pattern parameter and device parameters resolves to a ws:// url that is accessible from the browser. Here is where it's assembled. This pattern must allow the browser to connect to the publicHost:publicPort of the provider. See the example in the docker-compose-prod.yaml. When resolved the url will connect to the nginx which will then proxy it to the provider using this part of the config

Replies: 8 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by irdkwmnsb
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
question Further information is requested
2 participants
Converted from issue

This discussion was converted from issue #179 on March 30, 2025 08:11.