I run a service on my home desktop to share my music to my other devices over a tailscale VPN. I enabled https for it, I used a certificate generated by tailscale cert <my-ts-domain>, and I renew it automatically 1/week. This works great with FF:
This is how FF reports it. Which looks exactly as I expected. Before I did this setup, I would get prompts about the connection. I also use audacious for music, and it supports streaming over http/https. So I figured I just try the same URL. But in the case of audacious it fails to verify the certificate, and refuses to play. There’s also no option to ignore the error.
$ openssl s_client -connect node.tailnet.ts.net:port < /dev/null
Connecting to <IP>
CONNECTED(00000003)
depth=0 CN=node.tailnet.ts.net
verify error:num=20:unable to get local issuer certificate
verify return:1
depth=0 CN=node.tailnet.ts.net
verify error:num=21:unable to verify the first certificate
verify return:1
depth=0 CN=node.tailnet.ts.net
verify return:1
---
Certificate chain
0 s:CN=node.tailnet.ts.net
i:C=US, O=Let's Encrypt, CN=YE1
a:PKEY: EC, (prime256v1); sigalg: ecdsa-with-SHA384
v:NotBefore: Aug 28 23:50:02 2026 GMT; NotAfter: Nov 26 23:50:01 2026 GMT
---
Server certificate
-----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----
subject=CN=node.tailnet.ts.net
issuer=C=US, O=Let's Encrypt, CN=YE1
---
No client certificate CA names sent
Peer signing digest: SHA256
Peer signature type: ecdsa_secp256r1_sha256
Negotiated TLS1.3 group: X25519MLKEM768
---
SSL handshake has read 2396 bytes and written 1653 bytes
Verification error: unable to verify the first certificate
---
New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
Protocol: TLSv1.3
Server public key is 256 bit
This TLS version forbids renegotiation.
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 21 (unable to verify the first certificate)
---
DONE
Hmm, that doesn’t look correct. If I’m reading it right, that is not verifying. Does that mean I inadvertently added an exception to FF (quite unlikely, not my muscle memory default)? I also restart my browser every 2-3 days, and haven’t seen any certificate related prompts for my service ever since I set this up.
I looked at the manpage, not sure I understand. I’m sure I didn’t run this, but the instructions to setup the service didn’t have this in the steps. These were my steps (now in a systemd timer script) :
Thanks! That works! I was wondering there are probably other certificates in the chain I need. But I couldn’t find it. Could you share how you found the other 2 certs?
chillzone
(Rick The OldFart And **Private Tester**)
10
sudo update-ca-trust extract is the command used on RHEL-based Linux distributions (such as RHEL, CentOS, Fedora, and Rocky Linux) to regenerate the system’s consolidated CA certificate trust store.
Scans source directories: It reads certificate files from /etc/pki/ca-trust/source/ (high priority) and /usr/share/pki/ca-trust-source/ (low priority), including specific subdirectories like anchors/ for trusted CAs and blocklist/ for distrusted CAs.
And I’ve been told through my years, you run this command after adding, removing, or modifying certificates in the source directories to apply the changes system-wide.