Reverse Proxy about browserboxpro HOT 7 CLOSED

@skug67 In reply to your comment on config:

OK thanks for that. Some issues I can think of might be:

The DockerHub image is quite old, you could try to rebuild a docker image using the included utility script from the latest code version.

Chrome headless also needs to open port 5002 locally. Which the backend (on 8002) needs to talk to. No sure if that's somehow being blocked.

When you say "refreshes" are any errors shown?

In any case, I think you could try to run it from Node itself, or build a Docker image from a recent release, to get better debugging info and it by updating it might fix the problem.

I'm not sure. These are just ideas. I don't have a certain picture of what the problem might be.

from browserboxpro.

I'll poke around some. Don't think it has to do with 5002 <-> 8002 problems because it all works fine if I access directly from my browser to 8002. There's pretty clearly something going on with the Apache proxy......

from browserboxpro.

PS the error which shows is "Error connecting to the server - Will reload to try again"

from browserboxpro.

from browserboxpro.

Thanks. (For when/if you get back to this ... but totally understand if you never do)

One thing I am noticing which might help lead to explanation. When I run directly instead of via docker, I see that a direct connection produces console output of
{ connectionIp: '::ffff:192.168.0.157' }
When I connect via Apache proxy there's no output at all. Additional point -- my LAN is not set up for ipv6.

from browserboxpro.

I've got it working a lot better (still having problems with authorization/access control via Apache) but the following seems to generally work

  RewriteEngine On
  RewriteCond %{HTTP:Upgrade} =websocket [NC]
  RewriteRule /(.*)           ws://localhost:8002/$1 [P,L]
  RewriteCond %{HTTP:Upgrade} !=websocket [NC]
  RewriteRule /(.*)           http://localhost:8002/$1 [P,L]

  ProxyPassReverse / http://localhost:8002/

from browserboxpro.

Awesome, thank you for the issue, and the config on how you got it working!

There's a "login" step, which uses a /login? url with a special token, which then sets the cookie,

I believe. That may be causing issues if it's not in the rewrite rules, I don't know.

from browserboxpro.