IFTTT Webhook error Eproto
Hello,
Since 2 or 3 months I have noticed that all my webhooks return the error below:
I think that a ssl certificat problem or error.
What is the way to remove this problem ? Any Idea ??
Replies 17
Can you past your URL and body please?
(Please be aware to hide your credentials in the URL !!)
No sorry, I am mistaken. It's 33.
But fixed though. What error do you get?
Hi,
I can confirm this issue has been fixed in bèta 34.
RCP running as fine as before.
Best,
Michiel
Where you find the beta version 34?
For me the version 33 not work for the RPC ifttt
Hi,
I can confirm this issue has been fixed in bèta 34.
RCP running as fine as before.
Best,
Michiel
Hi there,
I can confirm I got the very same issue with my IFTTT + RPC connections since a few weeks ago (I did install the beta though).
So very interested as well for a solution.
Best regards,
Hello,
I do not remember if the issue appear after updated bOS.
I use the version 4.7.30 but the issue is present before this version.
The request from bOS to IFTTT work fine.
I have no idea where the problem comes from ???
In few days I try with an other bOS 4.7.0 to test if the problem is the same.
Best regards.
Hello,
you mentioned you started having this errors 2-3 months ago? Do you remember if they started after you updated bOS ?
We tested RPC/IFTTT using webhooks to control devices in the office using the latest bOS beta version and everything checks out and everything is working here.
Looking trough the update notes for our betas, there weren't any changes done on the RPC service so the communication should be working normally.
You tested directly roomba/IFTTT and you get the same results?
Best regards.
Hello!
I have the same problem on a Grinder Black box. I have an own domain, because my IP can change. I tried to set this domain as public address and restart bOS (i can even see the address has been correctly under the license settings). When I try to reach the box through https web browser I get certificate error (because the provided SSL cert is not valid on our domain). I have tried to find the certificate in the manager but I don't have any under Personal. What I found is a CC-Grinder cert under Remote Desktop, but based on HTTPS cert ID these are not the same, so I haven't touched it.
Do you have any idea how can I make a new cert for my domain (It's not a problem if i need to provide my own)? Then the HTTPS connection won't have any problem and I think the IFTTT with webhooks can work without any SSL problem.
Thank you in advance!