Connect.tidbyt.com certificate error

I was gone for a few weeks and when I came home my Tidbyt’s been stuck in the CONNECTING… loop + the app won’t even load.
Did a little digging and found the certificate on connect.tidbyt.com is not working for me, even though it’s not expired. This may be a problem with my network, but I’m posting here for posterity. Can anyone help?

I (2112) tidbyt/wifi: SYSTEM_EVENT_STA_CONNECTED connected...
I (2142) wifi:AP's beacon interval = 102400 us, DTIM period = 1
I (2172) tidbyt/wifi: SYSTEM_EVENT_STA_GOT_IP IP assigned...
I (2172) esp_netif_handlers: sta ip: 192.168.3.79, mask: 255.255.255.0, gw: 192.168.3.1
I (2172) tidbyt/ble: Not sending event (5) since no peer connected
I (2182) tidbyt/ble: Not sending event (6) since no peer connected
I (2232) tidbyt/connect: Downloading connection profile from: https://connect.tidbyt.com?deviceID=xxxxx-xxxxx-xxxxx-xxxxx-xxx
E (16122) esp-tls: couldn't get hostname for :connect.tidbyt.com: getaddrinfo() returns 202, addrinfo=0x0
E (16122) esp-tls: Failed to open new connection
E (16122) TRANSPORT_BASE: Failed to open a new connection
E (16132) HTTP_CLIENT: Connection failed, sock < 0
E (16132) tidbyt/connect: HTTP_EVENT_ERROR
E (16142) tidbyt/connect: couldn't reach https://connect.tidbyt.com?deviceID=xxxxx-xxxxx-xxxxx-xxxxx-xxx: ESP_ERR_HTTP_CONNECT
E (16162) tidbyt/connect: HTTP error - ESP_ERR_ESP_TLS_CANNOT_RESOLVE_HOSTNAME (mbedtls: 0x0)
E (16172) tidbyt/cloud: Error retrieving connection profile: ESP_ERR_HTTP_CONNECT
E (16182) tidbyt/connect: Failed to connect: ESP_ERR_HTTP_CONNECT
I (16222) tidbyt: Entering state ERROR (-1).
E (16222) tidbyt: Couldn't find handler for state: ERROR (-1).
W (16222) tidbyt: Handler loop suspended due to error, restarting in 5 seconds.
W (17232) tidbyt: Handler loop suspended due to error, restarting in 4 seconds.
W (18242) tidbyt: Handler loop suspended due to error, restarting in 3 seconds.
W (19242) tidbyt: Handler loop suspended due to error, restarting in 2 seconds.
W (20252) tidbyt: Handler loop suspended due to error, restarting in 1 seconds.
W (21262) tidbyt: Handler loop suspended due to error, restarting in 0 seconds.
W (22272) tidbyt: Restarting...
I (22302) wifi:state: run -> init (0)
I (22302) wifi:pm stop, total sleep time: 363895 us / 20194263 us
https://connect.tidbyt.com/

Peer’s Certificate issuer is not recognized.

HTTP Strict Transport Security: false
HTTP Public Key Pinning: false

Certificate chain:

-----BEGIN CERTIFICATE-----
MIIDOTCCAuCgAwIBAgIUAPKZE+gfp6SxI+J60VGfVnHqmiAwCgYIKoZIzj0EAwIw
KDEVMBMGA1UEChMMVGlkYnl0LCBJbmMuMQ8wDQYDVQQDEwZUaWRieXQwHhcNMjMw
NTAyMTM1NDE4WhcNMjMwNzMxMTM1NDE3WjAdMRswGQYDVQQDExJjb25uZWN0LnRp
ZGJ5dC5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQD3E7/S3w2B
yFObIeJV1u+0YkLGpElrjqSJgxcE5YCMPBTQnD/oEXKNn2w6rasOrl1HQL2KEdBL
FG8li0Q5W0HcnAxa/nj6RzsCzde43u+E3YGPHrsLVSx9ANcn+zDj0WxoQ3IUsCiq
rE/LTy1Ygitsrv3DkHkbeUa4d9AP/Lmu9hMRjwIQTgvpoM5cy7NSLn3Wewf1XW1M
IQQ8Kx7WeUiOtmNP4oPFpN8LEOoRwLNCoLYaDW390gpqfZmTyb1c2+hRBZT9t0/0
Mo2REkk/x1UStvrLt+uwXZ/S2qKOyymL/sreOVY2VwzR+rKHRC6YvC11wwrzhtEL
BsLjgaPKXDbpAgMBAAGjggEmMIIBIjAOBgNVHQ8BAf8EBAMCBaAwEwYDVR0lBAww
CgYIKwYBBQUHAwEwDAYDVR0TAQH/BAIwADAdBgNVHQ4EFgQUxXkd2esqWCqBsJWB
NCMoc50k8RwwHwYDVR0jBBgwFoAUkWzl2h6nJFemsrhhE4Ilb+U33i0wgY0GCCsG
AQUFBwEBBIGAMH4wfAYIKwYBBQUHMAKGcGh0dHA6Ly9wcml2YXRlY2EtY29udGVu
dC02NDUxMDZmZC0wMDAwLTIyNjktODBkNS0xNDIyM2JiMGE3NDIuc3RvcmFnZS5n
b29nbGVhcGlzLmNvbS8yZjVkZGUzY2IxNThlYTI5ZjVkNC9jYS5jcnQwHQYDVR0R
BBYwFIISY29ubmVjdC50aWRieXQuY29tMAoGCCqGSM49BAMCA0cAMEQCIC/iYmRo
oLwPqw/DeUJp8JSnkYWk04A3VV2PWdmHtMrPAiBmCq2/k4OlYo8NREyvuok43QTN
r5iR4grB4Oa/bVqU0g==
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
MIIBxDCCAWmgAwIBAgIQXcLxYVfRWtD/fMftlL2OFTAKBggqhkjOPQQDAjAWMRQw
EgYDVQQDEwtUaWRieXQgUm9vdDAeFw0yMzA1MDIxMzUwMTRaFw0yNDA2MjIwNTUw
MTRaMCgxFTATBgNVBAoTDFRpZGJ5dCwgSW5jLjEPMA0GA1UEAxMGVGlkYnl0MFkw
EwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEhdI9xRLlNnusu5zyvLLbhETK6QSzK4mc
++mRqBmbYutIM8hoz/wiqStQ7McmjMgWIKeDJ+W9pcqeEid2RWsp1aOBhjCBgzAd
BgNVHQ4EFgQUkWzl2h6nJFemsrhhE4Ilb+U33i0wHwYDVR0jBBgwFoAUaOJx+V1g
j8NcObczjxpObq+y42QwDgYDVR0PAQH/BAQDAgEGMB0GA1UdJQQWMBQGCCsGAQUF
BwMBBggrBgEFBQcDAjASBgNVHRMBAf8ECDAGAQH/AgEFMAoGCCqGSM49BAMCA0kA
MEYCIQDx2iFgG2CLkoVF0g9sZwzr/eRxqDExc9SrMdm5/w6zQQIhALoRtdCCzSub
LARSTK0Ol5DATTmqpgBlJ7cP3Sl5+cY5

-----END CERTIFICATE-----

No one has any idea? This thing is now a paperweight…

That certificate actually looks correct. It’s not valid for or recognized by browsers, but it will be recognized as valid by the root certificate chain that’s baked into the Tidbyt.

It looks like the underlying issue is actually that the Tidbyt can’t resolve the IP address for connect.tidbyt.com:

This seems like a DNS issue. Do you have an ad blocker or anything else on the network that would block the Tidbyt from resolving connect.tidbyt.com?

Also, in case you haven’t tried it, a good first troubleshooting step is always to hard reset the Tidbyt and set it up again, by holding down the button on the back for 5-10 seconds.

@rohan it seemed to be an issue with the wifi network my iot devices are on. fixed with your clue-- thank you!