Closed CorySanin closed 4 years ago
had a similar issue through a nginx reverse proxy only. It went away randomly though
That might be the issue then. I'm also using nginx as a reverse proxy.
This might be due to firefox and needing https for clipboard access, I need to do some testing on firefox with https.
Do you think that if I use Chrome in the container and Firefox for the client that my setup would work?
well navigator.clipboard.readText
is a client side issue, the server should be working.
so can confirm, does not work on ff, chrome works just fine. going to look into alternative for clipboard
api on ff
I've updated the docker container with a potential fix for this, please update and check it out. Reopen if this still an issue for you
Thanks, that works!
Describe the bug Perhaps there is something I'm missing, but I'm unable to type anything into the browser through the client running inside of Firefox. Client works fine in Chrome.
To Reproduce Steps to reproduce the behavior:
Expected behavior Can type into the remote browser when control is obtained
Screenshots N/A
Desktop (please complete the following information):
Additional context I tried using Chrome on Windows and it worked as expected. Still using Firefox within the container
Client Log: I see this a bunch:
Server Log: N/A