search

mrlt8 / docker-wyze-bridge

WebRTC/RTSP/RTMP/LL-HLS bridge for Wyze cams in a docker container
GNU Affero General Public License v3.0
2.7k stars 176 forks source link

400 Client Error on New Install #1127

Open 1simpleAtom opened 9 months ago

1simpleAtom commented 9 months ago

I have attempted to install wyze-bridge using docker compose, Portainer, Homeassistant, and Unraid. Each installation has given me the same error: 400 Client Error: Bad Request for url: https://auth-prod.api.wyze.com/v3/user/login

Below is the contents of the log file from my Unraid installation.

[WyzeBridge] WARNING: invalid escape sequence '\:'

🚀 DOCKER-WYZE-BRIDGE v2.6.0 X86_64 2.7.0 BUILD [2024-01-11t04:20:13.342z] bbacb0f

[WyzeBridge] ♻️ Clearing local cache...
[WyzeBridge] 🔍 Could not find local cache for 'auth'
[WyzeBridge] ☁️ Fetching 'auth' from the Wyze API...
 * Serving Flask app 'frontend'
 * Debug mode: off
[WyzeBridge] WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
 * Running on all addresses (0.0.0.0)
 * Running on http://127.0.0.1:5000
 * Running on http://172.17.0.16:5000
[WyzeBridge] Press CTRL+C to quit
[WyzeBridge] ⚠️ 400 Client Error: Bad Request for url: https://auth-prod.api.wyze.com/v3/user/login
[WyzeBridge] 🔍 Could not find local cache for 'cameras'
[WyzeBridge] ☁️ Fetching 'cameras' from the Wyze API...
[WyzeBridge] 🔍 Could not find local cache for 'auth'
[WyzeBridge] ☁️ Fetching 'auth' from the Wyze API...
[WyzeBridge] 192.168.5.103 - - [21/Feb/2024 09:59:50] "GET / HTTP/1.1" 200 -
[WyzeBridge] 192.168.5.103 - - [21/Feb/2024 09:59:50] "GET /static/bulma.css HTTP/1.1" 200 -
[WyzeBridge] 192.168.5.103 - - [21/Feb/2024 09:59:50] "GET /static/site.css HTTP/1.1" 200 -
[WyzeBridge] 192.168.5.103 - - [21/Feb/2024 09:59:50] "GET /static/bulma-toast.js HTTP/1.1" 200 -
[WyzeBridge] 192.168.5.103 - - [21/Feb/2024 09:59:50] "GET /static/site.js HTTP/1.1" 200 -
[WyzeBridge] 192.168.5.103 - - [21/Feb/2024 09:59:51] "GET /favicon.ico HTTP/1.1" 404 -
[WyzeBridge] 🔍 Could not find local cache for 'user'
[WyzeBridge] ☁️ Fetching 'user' from the Wyze API...
[WyzeBridge] 🔍 Could not find local cache for 'auth'
[WyzeBridge] ☁️ Fetching 'auth' from the Wyze API...
[WyzeBridge] ⚠️ 400 Client Error: Bad Request for url: https://auth-prod.api.wyze.com/v3/user/login
[WyzeBridge] 🔍 Could not find local cache for 'cameras'
[WyzeBridge] ☁️ Fetching 'cameras' from the Wyze API...
[WyzeBridge] 🔍 Could not find local cache for 'auth'
[WyzeBridge] ☁️ Fetching 'auth' from the Wyze API...
[WyzeBridge] ⚠️ 400 Client Error: Bad Request for url: https://auth-prod.api.wyze.com/v3/user/login
[WyzeBridge] Stopping 0 streams
[WyzeBridge] 👋 goodbye!

Am I perhaps missing something, or is the URL invalid?

Thanks!

dimmanramone commented 9 months ago

I have exactly the same issue.

I had a docker container up and running without any problems, then I had to remove it and set it up again, used exactly the same docker compose and I'm getting this error.

Rulevoid commented 9 months ago

Having the same issue even when using the UI to input my credentials (which work when entered to wyze's website).

giorgi1324 commented 9 months ago

Same here. Wyze recently had a security breach, this might be the result of them tightening things.

Here's my log:

wyze-bridge              | [WyzeBridge] WARNING: invalid escape sequence '\:'
wyze-bridge              |
wyze-bridge              | 🚀 DOCKER-WYZE-BRIDGE v2.6.0 X86_64 2.7.0-HW BUILD [2024-01-11t04:20:12.238z] bbacb0f
wyze-bridge              |
wyze-bridge              | [WyzeBridge] 🔍 Could not find local cache for 'auth'
wyze-bridge              |  * Serving Flask app 'frontend'
wyze-bridge              |  * Debug mode: off
wyze-bridge              | [WyzeBridge] ☁️ Fetching 'auth' from the Wyze API...
wyze-bridge              | [WyzeBridge] WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
wyze-bridge              |  * Running on all addresses (0.0.0.0)
wyze-bridge              |  * Running on http://127.0.0.1:5000
wyze-bridge              |  * Running on http://172.18.0.12:5000
wyze-bridge              | [WyzeBridge] Press CTRL+C to quit
wyze-bridge              | [WyzeBridge] ⚠️ 400 Client Error: Bad Request for url: https://auth-prod.api.wyze.com/v3/user/login
giorgi1324 commented 9 months ago

I commented on another issue as well and I'll post here as well for visibility:

I decided to change Wyze password to something without special characters and I was able to log back in!

Rulevoid commented 9 months ago

I commented on another issue as well and I'll post here as well for visibility:

I decided to change Wyze password to something without special characters and I was able to log back in!

I don't see how that's possible. The password requirements include special characters. How did you accomplish that?

image

giorgi1324 commented 9 months ago

Looks like dash counts as a special character. I use bitwarden and generated passphrase with capitalized first letters.

On Fri, Mar 1, 2024, 6:06 AM Ryan @.***> wrote:

I commented on another issue as well and I'll post here as well for visibility:

I decided to change Wyze password to something without special characters and I was able to log back in!

I don't see how that's possible. The password requirements include special characters. How did you accomplish that?

image.png (view on web) https://github.com/mrlt8/docker-wyze-bridge/assets/386998/fbdde120-5f77-41a5-915e-3a83884b677f

— Reply to this email directly, view it on GitHub https://github.com/mrlt8/docker-wyze-bridge/issues/1127#issuecomment-1973266889, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFU2XWGJFOH34BIBYSJ65LYWCDNZAVCNFSM6AAAAABDTN4WLCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZTGI3DMOBYHE . You are receiving this because you commented.Message ID: @.***>

Rulevoid commented 9 months ago

I specifically tried a dash and still received the 400 error. I wonder why you had success and I didn't. Probably some other variable at play.

Menz01 commented 9 months ago

i didn't see this post... i am having the same issue as well.

cybersholt commented 8 months ago

Perhaps your password contains a $ symbol, if it does you have to escape it in your compose file. So pa$sw0rd becomes pa$$sw0rd

Rulevoid commented 8 months ago

Personally, I'm not using a $ symbol. I've also completed avoided using the file and am just trying to type it in to the web interface on the fly. Still no luck.

Menz01 commented 8 months ago

Perhaps your password contains a $ symbol, if it does you have to escape it in your compose file. So pa$sw0rd becomes pa$$sw0rd

I don't have any $ in my password either

Menz01 commented 8 months ago

so i changed my password to a long password without any special characters and i was able to get it running again

Rulevoid commented 8 months ago

How did you create a password without special characters? That's one of the main password requirements.

On Tue, Mar 12, 2024 at 11:26 AM Menz01 @.***> wrote:

so i changed my password to a long password without any special characters and i was able to get it running again

— Reply to this email directly, view it on GitHub https://github.com/mrlt8/docker-wyze-bridge/issues/1127#issuecomment-1991917172, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAC6PNQKLSQKDPPIRPBHGQDYX4NCTAVCNFSM6AAAAABDTN4WLCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJRHEYTOMJXGI . You are receiving this because you are subscribed to this thread.Message ID: @.***>

Menz01 commented 8 months ago

How did you create a password without special characters? That's one of the main password requirements. … On Tue, Mar 12, 2024 at 11:26 AM Menz01 @.> wrote: so i changed my password to a long password without any special characters and i was able to get it running again — Reply to this email directly, view it on GitHub <#1127 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAC6PNQKLSQKDPPIRPBHGQDYX4NCTAVCNFSM6AAAAABDTN4WLCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJRHEYTOMJXGI . You are receiving this because you are subscribed to this thread.Message ID: @.>

I made it 11 characters long with a capital letter and numbers only and it accepted it

Menz01 commented 8 months ago

Special characters is not a requirement ![Uploading Screenshot_20240312-131316.png…]()