-
Notifications
You must be signed in to change notification settings - Fork 117
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
[LOGIN] rest-prod.immedia-semi.com: HTTP 406 error (was: SSL Certificate mismatch and endpoint error (HTTP 403)) #716
Comments
Ok I've definitely seen this happen before and it was when Blink started changing API endpoints related to login. It's been awhile, and I can't seem to find the related issues, but I'm 90% sure that's what it's related to. So options are:
|
SSL issue hopefully resolved. The server name differs between API.md and the constants.py. Blink resolves both names. Ugh. Correct one is in constants.py: rest-prod.immedia-semi.com This leaves me with a 406 error for the request. I've tried to sniff an app-originating request, but since I do not have a way to run a MITM proxy with injected certificate for the proxy I was not able to retrieve a proper API call stream. :( curl -v -H "Content-Type: application/json" -A "xxx" --data-binary '{ "password" : "xxxx", "client_specifier" : "vdfvdffd", "email" : "[email protected]" }' https://rest-prod.immedia-semi.com/api/v5/account/login
|
Waited for a week, unfortunately no progress. Anyone interested in jointly working on an update? I can do coding and testing, but would need support with protocol sniffing. |
Related to this maybe? This was a new addition about a year ago and the blinkpy library definitely does NOT send the location tier during login right now. https://github.com/MattTW/BlinkMonitorProtocol/blob/master/auth/login.md EDIT- an issue someone had where sending the account tier resulted in a correct login MattTW/BlinkMonitorProtocol#66 |
MattTW/BlinkMonitorProtocol#66 seems to resolve an issue in the later stage of the login process. So far I cannot get the Blink API to give me an auth token at all. With the step 1 login I get a HTTP 406 error (following https://github.com/MattTW/BlinkMonitorProtocol/blob/master/auth/login.md):
I I tried also other server names to check whether it may indeed be related to the tier: prod.immedia-semi.com ==> name not resolved rest.prod.immedia-semi.com ==> resolves, but returns a mismatching cloudfront.net certificate. Ignoring certificate rest-prde.immedia-semi.com ==> 406 HTTP error, no certificate issues Any other tiers I may try for Germany/Europe? |
Just to clarify: you cannot login using the blinkpy library either? So far you've only posted curl commands |
So far I have been using blinkpy as part of homeassistant. It stopped working some time back. Since I couldn't get it to run again, I upgraded to homeassistant 2023.5.2 with blinkpy 0.19.2 and tried to reinstall the Blink integration. The dialogue for entering the credentials shows up, but after entering the credentials and clicking on "send" I'm faced with an empty response box. The integration then does not proceed in the installation process. When I try it via the console I run into an login endpoint failure:
EDIT: Just confirmed the error with the latest version of blinkpy and debugging enabled. The same 406 HTTP error is returned:
|
New cat and mouse run? Would this help #568 (comment)? |
@oilervoss : Thanks for the API dump, that's indeed what's necessary to see and try to fix the issue! Do you happen to have a dump from the login procedure as well? In the extract I found only regular interactions after the user is already authenticated. But maybe I missed something? |
I'm so sorry @AndreasAchtzehn I wasn't able to extract the dump myself. That dump was a @selfagency 's work on Jun 15, 2022. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within seven days. Thank you for your contributions. |
Describe the bug
Login API server rest.prod.immedia-semi.com returns a cloudfront SSL certificate not covering the login API domain.
Even when certificate error is ignored, server returns "Not Found".
This leads to failure to login with blinkpy / home assistant integration setup.
To Reproduce
Steps to reproduce the behavior:
==> returns a certificate mismatch error
==> returns 403 error
==> returns 403 error
< HTTP/2 403
<TITLE>ERROR: The request could not be satisfied</TITLE>< server: CloudFront
< date: Sat, 06 May 2023 xx:xx:xx GMT
< content-type: text/html
< content-length: 915
< x-cache: Error from cloudfront
< via: 1.1 10cxxxxxxxxxx3d92.cloudfront.net (CloudFront)
< x-amz-cf-pop: HAM50-C3
< x-amz-cf-id: moxxxxx=
<
403 ERROR
The request could not be satisfied.
Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
The text was updated successfully, but these errors were encountered: