2026-09-23 18:45 UTC
cool, yeah it might be the cert issue, I could navigate with the browser but got this when using curl:
$ curl https://nexus.asbestos.cafe/api/v2/instance
curl: (60) SSL certificate OpenSSL verify result: unable to get local issuer certificate (20)
More details here: https://curl.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the webpage mentioned above.
>the server sends only the leaf certificate, without the Let’s Encrypt intermediate. Check that relayd’s certificate file contains the full chain.
and since I don't know how to do that here's astra's response to how do I do that:
grep -c 'BEGIN CERTIFICATE' /etc/ssl/nexus.asbestos.cafe.crt
1 means it contains only one certificate. For his Let’s Encrypt setup, the file should contain the site certificate followed by the intermediate certificate—normally 2 certificates.
One wrinkle: relayd prefers /etc/ssl/nexus.asbestos.cafe:443.crt if that exists, so check that file too. relayd documentation
If he uses OpenBSD’s acme-client, check the domain block in /etc/acme-client.conf. The relevant setting should be:
domain full chain certificate "/etc/ssl/nexus.asbestos.cafe.crt"
The distinction is full chain certificate, which writes the site certificate plus intermediates, versus certificate, which writes only the site certificate. The output path must match whichever file relayd
actually loads. acme-client documentation
Replies (0)
No replies.