-
-
Notifications
You must be signed in to change notification settings - Fork 161
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
WB_AUTH=False doesn't appear to be working #1331
Comments
The page you're seeing is unrelated to Keep in mind that wyze actively blocks any authentication attempt from commercial VPNs and/or data center IPs, so you may need to temporarily disable any VPNs for the container. |
After getting a new Wyze Key ID and API Key, it appears to be working again. |
I have WB_AUTH=False in my docker compose file. Previous version I was able to gain access to the UI, but with the latest release v2.10.2 it's asking for credentials. For some odd reason, even if I enter my credentials I'm unable to login which is why I decided to disable the authentication, can't remember which version, must have been from the release where it was enforced.
Could someone confirm whether or not they are able to disable the web UI authentication for docker compose? Appreciate your help. Currently have gone back to version 2.10.1 since it's been stable for me.
Below is my compose file:
version: '2.4'
services:
wyze-bridge:
container_name: wyze-bridge
restart: unless-stopped
image: mrlt8/wyze-bridge:latest
ports:
- 1935:1935 # RTMP
- 8554:8554 # RTSP
- 8888:8888 # HLS
- 8889:8889 #WebRTC
- 8189:8189/udp # WebRTC/ICE
- 5000:5000 # WEB-UI
environment:
# [REQUIRED] Fill the following two lines:
- WB_AUTH=False
- WYZE_EMAIL=#redacted"
- WYZE_PASSWORD=#redacted"
- API_ID=#redacted"
- API_KEY=#redacted"
- TZ=America/New_York
- ENABLE_AUDIO=True
- FILTER_NAMES=Backyard, West Yard, East Yard, Front Porch
devices:
- /dev/dri:/dev/dri
The text was updated successfully, but these errors were encountered: