tailscale / tailscale/tailscale

cert: set-dns response: 500 Internal Server Error | Unable to provision new certificate

Open
#10,220 18 comments 0 reactions 0 assignees View on GitHub
bug needs-triage
Dominant language
Go
Stars
36.5k
Forks
3.2k
Avg merge
2d 3h
Merged PRs (30d)
123

Description

### 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

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.