Replies: 2 comments
-
Something like this?
|
Beta Was this translation helpful? Give feedback.
-
For some reason I couldn't get it to pass the /wbr part of the url (even as above) when it was in another config (same fqdn, but rying to separate target at "/wbr" I was adding it into another host conf, but simplified by just creating another vhost. Leaving this in case it's useful for ref for other ppl starting. This will also block unauthenticated requests to /api. This was first set up on port 80 without the ssl parts and just let "certbot --apache" create the cert and add the redirect rules.
Thanks @mrlt8 ! The bridge helps us get much more value from our several wyze cams, esp to tie into a multiuser environment like zm. Having to depend on the wyze app sucks- anyone you share a cam with can power it off. |
Beta Was this translation helpful? Give feedback.
-
Hi!
I have set all ports to only listen on 127.0.0.1 and cameras are accessible from the same host, where I am running zoneminder and have all feeds (monitors) set up ok.
I would like to secure the docker-wyze-bridge WebUI a bit so I am first trying to set up a reverse proxy to 127.0.0.1:5000 and once I get this working will move on to enabling apache's basic auth,
I have this section in one of my site configs (SSL enabled):
And it proxies almost nicely when adding the /wbr URL to that host's address, except I get no images.
I tried changing WB_IP a bit but no dice, and also tried setting "ProxyPreserveHost On" but can't get this scenario working yet.
Any pointers are very much appreciated!
Beta Was this translation helpful? Give feedback.
All reactions