Hi, yes, still not able to connect.Hi there,
Are you still having issues? Looking at your logs, the concerning bit is "WARN API call unsuccessful error" which means that rpi-connect wasn't able to communicate with the Raspberry Pi Connect API which it needs to in order to advertise the capabilities of your device and negotiate connections from the browser.
Are you able to successfully make a request from your device to the API, e.g.Code:
$ curl -v https://api.connect.raspberrypi.com/up
curl looks good
I have removed, rebooted, installed again several times, no improvement.pi@raspberrypi64:~ $ curl -v https://api.connect.raspberrypi.com/up
* Trying [2a00d0::7]:443...
* Connected to api.connect.raspberrypi.com (2a00d0::7) port 443 (#0)
* ALPN: offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* CAfile: /etc/ssl/certs/ca-certificates.crt
* CApath: /etc/ssl/certs
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN: server accepted h2
* Server certificate:
Dashboard is reporting that my device is visible, yet no "connect" button
rpi-connect
Last used less than a minute ago
Statistics: Posted by bondskin — Tue Jul 02, 2024 9:18 am