question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

BUG: error indicates auth process using IP not host name to do SSL verfiication

See original GitHub issue

Describe the bug & steps to repro

I setup integration via hacs. Added integration in integrations panel in the config i added my amazon username, password and external accessible hostname for home assistant (e.g. https://myname.mydomain.com (this uses a wildcard cert issues by comodo and that is trusted by amazon) was proxied redirected to amazon authenticated with amazon was redirected back to https://[myextenraldnsname]/auth/alexamedia/proxy/ap/signin then got this:

https://<internalip>/auth/foomedia/proxy/ap/signin/<redacted>; please retry: Cannot connect to host <internalip>:443 ssl:True [SSLCertVerificationError: (1, "[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: IP address mismatch, certificate is not valid for '<internalip>'. (_ssl.c:1125)")] 

it needs to be using a host name, not the IP address… or the SSL verification will never work.

System details

  • Home-assistant (version): core-2021.3.2 supervisor-2021.03.4
  • Hassio (Yes): (Please note you may have to restart hassio 2-3 times to load the latest version of alexapy after an update. This looks like a HA bug).
  • alexa_media v3.8.2
  • alexapy 1.24.2
  • Amazon [2FA is disabled] (using new proxy method)

Logs Please provide logs. We’ll be most likely asking for them anyway.

Additional context Add any other context about the problem here.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:17

github_iconTop GitHub Comments

1reaction
alandtsecommented, Mar 15, 2021

No. But I’ll leave this open until I propagate the fix.

0reactions
scytocommented, Mar 15, 2021

oh and to answer your earlier question, there was no other proxy in my network and yes the URL in the browser had names and not ip.

Read more comments on GitHub >

github_iconTop Results From Across the Web

A Simple Explanation of SSL Certificate Errors & How to Fix ...
This error indicates that the domain name in the SSL certificate doesn't match the URL that was typed into the browser. This message...
Read more >
What Is an SSL Common Name Mismatch Error and How Do I ...
A common name mismatch error occurs when the common name or SAN of your SSL/TLS Certificate does not match the domain or address...
Read more >
How to solve the problem of getting HostName Verification ...
It indicates that your application is not able to establish SSL connection to remote server, due to Hostname verification failure. CAUSE. A host...
Read more >
SSL Certification works with localhost but not computer name ...
The certificate warning that you are encountering is really a name mismatch error, which indicates that the common name (domain ...
Read more >
How to Fix “SSL Handshake Failed” & "Cloudflare 525" Error
1. Update Your System Date and Time · 2. Check to See If Your SSL Certificate Is Valid.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found