tailscale: Failed to get cert on Synology
What is the issue?
My win10 device can get the cert file successfully, but the Synology failed… Running the command on Synology:
root@myNas:~# tailscale cert
Usage: tailscale cert [flags] <domain>
For domain, use "mynas.****.ts.net".
root@myNas:~# tailscale cert mynas.****.ts.net
unexpected output: no delimiter
Steps to reproduce
Run tailscale cert <domain> on a Synology device.
Then it returns
unexpected output: no delimiter
Are there any recent changes that introduced the issue?
No response
OS
Synology
OS version
DSM6
Tailscale version
1.22.0
Bug report
BUG-4107f35d6ef47f772854e72ba476b9a07037c6ddfc410801bf5c252697827bcb-20220303170343Z-096b0250aa682d28
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 2
- Comments: 23 (7 by maintainers)
Commits related to this issue
- start-stop-status: set --statedir Pass --statedir argument to tailscaled, instead of the state file, to allow certificate support to work. Fixes https://github.com/tailscale/tailscale/issues/4060 S... — committed to tailscale/tailscale-synology by DentonGentry 2 years ago
- ipn/localapi: define a cert dir for Synology DSM6 Fixes #4060 — committed to tailscale/tailscale by bradfitz 2 years ago
- ipn/localapi: define a cert dir for Synology DSM6 Fixes #4060 Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com> — committed to tailscale/tailscale by bradfitz 2 years ago
- ipn/localapi: define a cert dir for Synology DSM6 Fixes #4060 Change-Id: I5f145d4f56f6edb14825268e858d419c55918673 Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com> — committed to tailscale/tailscale by bradfitz 2 years ago
- ipn/localapi: define a cert dir for Synology DSM6 Fixes #4060 Change-Id: I5f145d4f56f6edb14825268e858d419c55918673 Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com> — committed to tailscale/tailscale by bradfitz 2 years ago
Okay, this’ll be fixed in Tailscale 1.28.0 on DSM6. You’ll need DSM6 Update 3 or higher.
@DentonGentry although I rant (and apologies for threadjacking), believe me I completely understand and appreciate your comment. The TS blog post I referenced does a great job of explaining the complexity involved (I learned a lot from it!). What gets harder, now, however, is searching for solutions to problems, especially for users new to tailscale. If you have one set of users (e.g. sticking to 1.18), extolling the virtues of TS saying “this works great! go download tailscale and happy networking”) without mentioning these complexities, I predict new users are going to get frustrated when things don’t work as they expected or like they had been told. I’ve been a TS fanboy for the last 4 or 5 months, and while I am still enamoured with the software, it’s been quite an exercise to piece together information from reddit, forums, github, knowledge base, blog posts, just to understand how the software should work.