You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First off, excellent work. My ESP8266 is running much quicker with your TG bot library. However, I'm quite concerned about the embedded TLS certificate (tg_certificate.h) for api.telegram.org. I understand it's likely in place to reduce the overhead for connection time. But what occurs when the certificate expires, which is expected in September 2024?
I am planning to put my device in remote distant place, and now thinking what workarounds or fixes can be applied to avoid any service interruptions.
The text was updated successfully, but these errors were encountered:
Unable to connect to Telegram server
(SSLClient)(SSL_ERROR)(m_start_ssl): Failed to initlalize the SSL layer
(SSLClient)(SSL_ERROR)(m_print_br_error): Certificate is expired or not yet valid.
Unable to connect to Telegram server
(SSLClient)(SSL_ERROR)(m_start_ssl): Failed to initlalize the SSL layer
(SSLClient)(SSL_ERROR)(m_print_br_error): Certificate is expired or not yet valid.
Hello!
First off, excellent work. My ESP8266 is running much quicker with your TG bot library. However, I'm quite concerned about the embedded TLS certificate (tg_certificate.h) for api.telegram.org. I understand it's likely in place to reduce the overhead for connection time. But what occurs when the certificate expires, which is expected in September 2024?
I am planning to put my device in remote distant place, and now thinking what workarounds or fixes can be applied to avoid any service interruptions.
The text was updated successfully, but these errors were encountered: