tailscale: cert: set-dns response: 500 Internal Server Error | Unable to provision new certificate
What is the issue?
I am unable to renew a certificate for a tailscale node, which was previously working. It seems that the Tailscale API throws a HTTP 500 when Tailscale is trying to update/set DNS configurations for the respective ACME DNS Challenge.
It seems to be an issue for this specific node only, I was ably to successfully renew certificates for other nodes.
I did upgrade Tailscale from 1.30.X to latest (1.52.1) in an attempt to resolve this, but this didn’t change anything.
Steps to reproduce
sudo tailscale cert ****.tailnet-****.ts.net
> 500 Internal Server Error: SetDNS "_acme-challenge.****.tailnet-****.ts.net" => "****": set-dns response: 500 Internal Server Error, failed to create DNS record
Additional logs don’t show anything useful:
Nov 13 12:18:31 machine tailscaled[975]: cert("****.tailnet-****.ts.net"): already had ACME account.
Nov 13 12:18:32 machine tailscaled[975]: cert("****.tailnet-****.ts.net"): starting SetDNS call...
Nov 13 12:18:32 machine tailscaled[975]: Accept: TCP{*** > ***} 60 tcp ok
Nov 13 12:18:36 machine tailscaled[975]: cert("****.tailnet-****.ts.net"): getCertPEM: SetDNS "_acme-challenge.****.tailnet-****.ts.net" => ***": set-dns response: 500 Internal Server Error, failed to create DNS record
Are there any recent changes that introduced the issue?
No changes.
OS
Linux
OS version
Ubuntu 20.04.4 LTS
Tailscale version
1.52.1
Other software
No response
Bug report
BUG-221800ba2866e940112ded3ac5100d3c019345ec728be786bc78f1cf3e039be8-20231113064619Z-40e514f598f78137
About this issue
- Original URL
- State: open
- Created 3 years ago
- Comments: 16
I’m having the same issue on macOS, latest app store version.
I’m having this issue currently
500 Internal Server Error: SetDNS "_acme-challenge.name.tail6ceac.ts.net" => "N5ZXGzRb0x0unsAM_yKHQdkTWFY51D8t8ZWDuPQ_akQ": set-dns response: 500 Internal Server Error, failed to create DNS recordI’m experiencing the same issue while configuring the API server proxy in the Kubernetes Operator. The operator pod log contains:
Since I’m also using a Tailscale Ingress resource, I checked its pod log as well. It revelaed:
Yes, I’m the one to blame for the
too many certificatesissue on the Ingress resource. I’m wondering if this also affects the Kubernetes Operator certificate somehow. I already changed the hostname several times to unused values to circumvent this limitation, but the500 Internal Server Errorremains.I think I’ll just wait for
2024-09-19T04:07:15Zand check if the issue is still reproducible afterwards.