-
Notifications
You must be signed in to change notification settings - Fork 10
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
Connection to api.pushbullet.com fails #6
Comments
Have exactly same problem. The host and port are as follows: const char* host = "api.pushbullet.com"; It fails at: if (!client.connect(host, httpsPort)) { and my console says: 03:46:06.820 -> WiFi connected Would be great if someone could give a hint :) |
also have the same problem |
I have the same problem. But I guess no one cares. |
you have to varify by using thingspeak's fingerprint |
I have the connection problem, too. Also tried to verify the actual fingerprint which I read out of the browsers certificate and via grc.com. Hope, anyone has an idea or can support me.
|
Fails for me too. The current fingerprint should be: C1 72 5A 7A 6C AE BC CD 0A 57 8E 3A DA 39 C8 47 26 36 C9 77. But this didn't work for me... |
Hi
So I expect the connection setup should be different than: I have found the solution elsewhere in GitHub: Resulting in: |
@anuroopshannu please close.. |
This Is Not Working : Compilation error: 'class axTLS::WiFiClientSecure' has no member named 'setInsecure' |
This Is Not Working Not Connecting to Pushbullet : Compilation error: 'class axTLS::WiFiClientSecure' has no member named 'setInsecure' |
Found Prob. That was not Told The Arduino IDE 2.0.4 Dose Not Work, The 2.1.1 Works 7-7-2023 |
Worked with Arduino 1.8.18 after adding " client.setInsecure();" |
Hey, I've been trying to get past this since a long time now. When I use this library it continuously fails at
I've amended the ssid, password and api key wherever necessary and my esp8266 is successfully connecting to the internet too. Here's my code:
and the following is printed on my serial console:
Please let me know a get around for this.
The text was updated successfully, but these errors were encountered: