WB_AUTH=False doesn't appear to be working

[James62370]

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

[mrlt8]

WB_AUTH=False seems to be working for me:

Could you try running docker compose down, confirm it's really down and then run the docker compose up command again to make sure it's using the correct docker-compose.yml?

[James62370]

Appreciate the reply along with your continued support.

I'm running this with ProxMox 8 in a stand alone lxc container along a portainer stack. I tried updating the stack again and for some reason it keeps asking for credentials.

Please advise if there is anything else I can try.

[James62370]

Strange that previous version works ok.

[mrlt8]

The page you're seeing is unrelated to WB_AUTH and is actually used to authenticate with wyze. I'm not sure why 10.2 is failing while 10.1 still works, but can you check the logs to see if the authentication is failing for some reason?

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.

[James62370]

After getting a new Wyze Key ID and API Key, it appears to be working again.