I have no idea. I would think it didn’t, but I don’t really have any experience to base that on. Maybe you could try just copying the cert.pem and pasting this at the end of the fullchain.pem file and saving, then doing the certbot renewal and see?
Otherwise you just hope someone else can answer better than me.
AGRHHHHH… I am going crazy because of this!!! EXACTLY the same issue, cannot control HA from IFTTT. The problem is that IFTTT, webhooks, SSL, are all new to me…
Anyway, I have maker channel configured EXACTLY as in examples, correct URL, correct password, and yet it never actually manages to talk to HA. The best I got to was I was receiving notifications that there was an attempt to connect but failed due to authentication. In IFTTT I am getting “an error with Maker Webhooks prevented your Applet…”
I did appended content of cert.pem in to fullchain.pem (so I have 3 keys in fullchain.pem)
Any ideas?
Thanks
Found it: I copied body messages form examples, and edited them to fit my needs. Turns out those where somehow wrong quotation marks!
@hede0n
Frustrating! I can show you what I have set up, so maybe you’ll find something useful?
I assume you have everything set up so you can access you homeassistant instance from outside you home network, with an address starting with https://?
And just to be completely sure (sorry if this sounds condesending, just something I could have screwed up, so better make sure 
), you are using the cert.pem and fullchain.pem in the correct folder? I have three different pairs, but only one pair in the correct folder (/etc/letsencrypt/live/REDACTED.duckdns.org/fullchain.pem)
My IFTTT applet looks like this:
I also tried sending from HA to IFTTT first; I have a scripts.yaml file where I have the following entry for IFTTT
ifttt_test:
alias: IFTTT Test
sequence:
- service: ifttt.trigger
data:
event: testhass
Then you can make an applet on IFTTT that reacts to receiving “testhass”, and does whatever.
So if you can access through SSL (that is, if you can connect to your home assistant when you are not at home, using an address like the one I have in my IFTTT applet, starting with https://, not http://), then I’d start by seeing if you can send out, from HA to IFTTT.
If you can access from outside, but can’t send from HA to IFTTT, then… well, then I don’t know. Maybe re-check you maker api key? I’ve changed mine several times, and somehow I always forget to set the new one in one or two places.
But if you can’t access via https, then that is where you should start.
For reference, my http entry in my configuration file is:
### HTTP ###
http:
api_password: !secret api_password
ssl_certificate: !secret my_ssl_certificate
ssl_key: !secret my_ssl_key
base_url: !secret secret_base_url
ip_ban_enabled: True
login_attempts_threshold: 3
If you’ve set up your certificates etc. like I have (let’s encrypt and duckdns), then you also need to enable port forwarding on you router. Some people said it didn’t matter about the port, but the way it works for me is forwarding the external port 443 to my internal IP (192.168.0.160 for me) for the system running home assistant, and port 8123. But given that you get a connect attempt, this is probably not the problem…?
Good troubleshooting guide, thanks for that.
I think I had two problems, first one was probably with .pem files, as soon after I worked on them, I stopped recive notifications about failed login attempts (or something like that). But it still didn’t work, so I was starting to pull my hairs out. At this point I decided to revisit .log and found that problem cascaded down and now I was reciving error messages about not using double quotation marks! I was, but copy/pasted body somehow had different double quotation marks.
Thanks man, I can finally go to bed 
Great! I do remember having some issues with those as well. But glad you figured it out.
Hey! anyone know how to make it work with HassIO (with lets encrypt and DuckDNS)? If I understand things correctly it has to do with the Encryption-certificates. I’ve set up Lets Encrypt and DuckDNS with the addons in HassIO and I had an old Webhook/Maker-connection in IFTTT.
//F
I am also having trouble getting IFTTT and Google Home to work. I am so aggravated. I have spent the whole day reading threads and changing settings. I’m pretty sure my IFTTT webhooks key is right; the Applet has the right stuff in the right parts. But when I give Google Home my command, I get this error in the log file"
2017-08-16 16:05:12 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File “/usr/lib/python3.6/site-packages/aiohttp/web_protocol.py”, line 422, in start
resp = yield from self._request_handler(request)
File “/usr/lib/python3.6/site-packages/aiohttp/web.py”, line 306, in _handle
resp = yield from handler(request)
File “/usr/lib/python3.6/asyncio/coroutines.py”, line 213, in coro
res = yield from res
File “/usr/lib/python3.6/asyncio/coroutines.py”, line 213, in coro
res = yield from res
File “/usr/lib/python3.6/site-packages/homeassistant/components/http/ban.py”, line 58, in ban_middleware_handler
return (yield from handler(request))
File “/usr/lib/python3.6/site-packages/homeassistant/components/http/init.py”, line 424, in handle
result = yield from result
File “/usr/lib/python3.6/site-packages/homeassistant/components/api.py”, line 311, in post
data = json.loads(body) if body else None
File “/usr/lib/python3.6/json/init.py”, line 354, in loads
return _default_decoder.decode(s)
File “/usr/lib/python3.6/json/decoder.py”, line 339, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File “/usr/lib/python3.6/json/decoder.py”, line 355, in raw_decode
obj, end = self.scan_once(s, idx)
json.decoder.JSONDecodeError: Expecting property name enclosed in double quotes: line 1 column 2 (char 1)
Here is my Applet:
Any Help out there in Hass.io land?
In case anyone has the same issue. I just cut and pasted the example at https://home-assistant.io/blog/2015/09/13/home-assistant-meets-ifttt/ and did not notice that the BODY section had some of those upside down quotaion marks. I retyped all the quotes and it all worked. What a life!
please can you help in the instructions to append de certificates? where I find them? how can I do this through windows?
I haven’t really worked with any of this in windows, but I guess it would be where you installed it. If you can’t remember, can’t you just search for them? Once you find them, I just did as acs suggested; copied the contents of cert.pem and pasted it into the fullchain.pem. Not replaced, just added after whatever was already there. So in my fullchain.pem, I have something like:
-----BEGIN CERTIFICATE-----
MY-SECRET-CERTIFICATE-THAT-WAS-ALREADY-THERE
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
MY-OTHER-SECRET-CERTIFICATE-FROM-cert.pem-FILE
-----END CERTIFICATE-----
Its installed on my pi do I have to take off my sd card pr just run ssh?
I’ve done everything through SSH; I haven’t taken out my SD (except for full image backups) or connected a keyboard since installing home assistant.
On a raspberry pi, I installed mlocate. Using the terminal (through ssh):
sudo apt-get update && sudo apt-get install mlocate -y
sudo updatedb
Then you can search for your files. remember to run the updatedb every time you change something (or just before you search). Search with locate, e.g.
locate cert.pem
then open it with your favorite editor (I use nano), and copy the text from from -----BEGIN CERTIFICATE----- to and including -----END CERTIFICATE-----. The find the fullchain:
locate fullchain.pem
Again, open in an editor, and paste the text at the end of the fullchain.pem file. You might need to do a reboot after this.
Has anyone got this to work with Hassio, duckDNS and let’s encrypt? I can’t located the fullchain.pem file
Thank you, at last i have had a sucsess, was just about to smash it up…lol.