tailscale / tailscale/caddy-tailscale
Does not reconnect to tailnet after network downtime
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 978
- Forks
- 96
- PR merge metrics
- No merged PRs in 30d
Description
I had an outage today, and my caddy service went awol, the ephemeral services expiring, even after the outage ended. I had to restart the server to get it working again.
Nothing interesting in the log but there might be a condition to monitor here.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing a network outage while the Caddy service is running, then inspect the logs and the handling of ephemeral services after connectivity returns. Compare behavior after recovery with behavior after a full server restart. Done means the service reconnects to the tailnet and ephemeral services do not expire after a temporary outage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100