-
-
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
SSL verification failure #59
Comments
@freedreamer82 - Sorry for the delay on this (we do this in our spare time for free). I know the instructions aren’t great on this, but it’s up to you. Since you control the configuration and the server, you can decide to have the verify off, or on. If you want to have it on, grab a copy of your |
got it , maybe update the wiki! |
@freedreamer82 Yes, I know 😄 I plan on posting the update this weekend. |
If anyone is hitting the issue with verification failing (Ive seen this on a number of Forums, but not the solution.)
The order is important, and actually I found it had to be in the order 1. Your Cert, 2. The Root Cert, 3. lets Encrypt CA Cert. -----BEGIN CERTIFICATE----- Note that it also needs to be readable by homeassistant, so be careful of dos-to-unix conversion issues if you are editing under windows.. Also make sure each of the ---BEGIN--- and ---END--- statements are each on a separate line (as above). Once you've created this file, copy it up to homeassistant (probably the ssl directory) and update your configuration.yaml to use this new file rather than the previous certificate.crt (or simply replace the existing certificate.crt with this combined one) Just a side note, the other issue I found was that running haaska in AWS (Ireland/Europe instance), HA had to be accessible via port 443 rather than HA's standard 8123. Once I updated that, all worked perfectly! |
Question... as far I understood this is why I'm getting this problem... how can I avoid it? |
Hi,
i followed the guide and I registered correctly the skill for Alexa , but if I test the lambda I get:
'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed
if i disable the ssl verify in config it works...but It's not a good idea.
any idea?
I've been using letsencrypt cert on my server.
Marco
The text was updated successfully, but these errors were encountered: