starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

Unable to install #393

New Issue
Closed
opened 2025-12-29 01:28:12 +01:00 by adam · 7 comments
adam commented 2025-12-29 01:28:12 +01:00
Owner
Copy Link

Originally created by @Frankzhang854 on GitHub (Dec 13, 2022).

Excuse me, the old version cannot be installed with the new configuration file, but the old configuration file can be installed and connected to the client. Is there any change in the new version of the configuration file and the installation method of the installation package? Thank you

Issue description

To Reproduce

Context info

Originally created by @Frankzhang854 on GitHub (Dec 13, 2022). Excuse me, the old version cannot be installed with the new configuration file, but the old configuration file can be installed and connected to the client. Is there any change in the new version of the configuration file and the installation method of the installation package? Thank you<!-- Headscale is a multinational community across the globe. Our common language is English. Please consider raising the issue in this language. --> <!-- If you have a question, please consider using our Discord for asking questions --> **Issue description** <!-- Please add your issue description. --> **To Reproduce** <!-- Steps to reproduce the behavior. --> **Context info** <!-- Please add relevant information about your system. For example: - Version of headscale used - Version of tailscale client - OS (e.g. Linux, Mac, Cygwin, WSL, etc.) and version - Kernel version - The relevant config parameters you used - Log output -->
adam added the bug label 2025-12-29 01:28:12 +01:00
adam closed this issue 2025-12-29 01:28:12 +01:00
adam commented 2025-12-29 01:28:13 +01:00
Author
Owner
Copy Link

@juanfont commented on GitHub (Jan 1, 2023):

Please always check our release notes. Any breaking change in the config is reported there.

@juanfont commented on GitHub (Jan 1, 2023): Please always check our release notes. Any breaking change in the config is reported there.
adam commented 2025-12-29 01:28:13 +01:00
Author
Owner
Copy Link

@Frankzhang854 commented on GitHub (Jan 3, 2023):

Excuse me, is there any difference between the installation method and the previous one?

------------------ 原始邮件 ------------------
发件人: "Juan @.>;
发送时间: 2023年1月1日(星期天) 晚上8:35
收件人: @.>;
抄送: @.>; @.>;
主题: Re: [juanfont/headscale] Unable to install (Issue #1060)

请随时查看我们的发行说明。配置中的任何破坏性更改都会在此报告。

—
直接回复此邮件，在GitHub上查看，或取消订阅.
@.***与>.

@Frankzhang854 commented on GitHub (Jan 3, 2023): Excuse me, is there any difference between the installation method and the previous one? ------------------&nbsp;原始邮件&nbsp;------------------ 发件人: "Juan ***@***.***&gt;; 发送时间: 2023年1月1日(星期天) 晚上8:35 收件人: ***@***.***&gt;; 抄送: ***@***.***&gt;; ***@***.***&gt;; 主题: Re: [juanfont/headscale] Unable to install (Issue #1060) 请随时查看我们的发行说明。配置中的任何破坏性更改都会在此报告。 — 直接回复此邮件，在GitHub上查看，或取消订阅. ***@***.***与&gt;.
adam commented 2025-12-29 01:28:13 +01:00
Author
Owner
Copy Link

@Frankzhang854 commented on GitHub (Jan 3, 2023):

Please ask, in the configuration file similar to "./headscale.sock", do you need to manually fill in the file address, such as "/var/run/headscale.sock".

------------------ 原始邮件 ------------------
发件人: "新新" @.>;
发送时间: 2023年1月3日(星期二) 上午9:02
@.@.>;
@.>;
主题: 回复： [juanfont/headscale] Unable to install (Issue #1060)

Excuse me, is there any difference between the installation method and the previous one?

------------------ 原始邮件 ------------------
发件人: "Juan @.>;
发送时间: 2023年1月1日(星期天) 晚上8:35
收件人: @.>;
抄送: @.>; @.>;
主题: Re: [juanfont/headscale] Unable to install (Issue #1060)

请随时查看我们的发行说明。配置中的任何破坏性更改都会在此报告。

—
直接回复此邮件，在GitHub上查看，或取消订阅.
@.***与>.

@Frankzhang854 commented on GitHub (Jan 3, 2023): Please ask, in the configuration file similar to "./headscale.sock", do you need to manually fill in the file address, such as "/var/run/headscale.sock". ------------------&nbsp;原始邮件&nbsp;------------------ 发件人: "新新" ***@***.***&gt;; 发送时间:&nbsp;2023年1月3日(星期二) 上午9:02 ***@***.******@***.***&gt;; ***@***.***&gt;; 主题:&nbsp;回复： [juanfont/headscale] Unable to install (Issue #1060) Excuse me, is there any difference between the installation method and the previous one? ------------------ 原始邮件 ------------------ 发件人: "Juan ***@***.***&gt;; 发送时间: 2023年1月1日(星期天) 晚上8:35 收件人: ***@***.***&gt;; 抄送: ***@***.***&gt;; ***@***.***&gt;; 主题: Re: [juanfont/headscale] Unable to install (Issue #1060) 请随时查看我们的发行说明。配置中的任何破坏性更改都会在此报告。 — 直接回复此邮件，在GitHub上查看，或取消订阅. ***@***.***与&gt;.
adam commented 2025-12-29 01:28:13 +01:00
Author
Owner
Copy Link

@Schokobecher commented on GitHub (Jan 3, 2023):

./ is the current dir as a relative path.
Sockets usually fo into /run, but you are free to do as you see fit.

@Schokobecher commented on GitHub (Jan 3, 2023): `./` is the current dir as a relative path. Sockets usually fo into [/run](https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch03s15.html), but you are free to do as you see fit.
adam commented 2025-12-29 01:28:13 +01:00
Author
Owner
Copy Link

@Frankzhang854 commented on GitHub (Jan 3, 2023):

Please ask, the same configuration file, and the client version remains unchanged, headscale_0.18.0-beta2 cannot open the exit node, but headscale_0.18.0-beta1 can open the exit node, thank you
My English is very bad, please forgive me

------------------ 原始邮件 ------------------
发件人: "juanfont/headscale" @.>;
发送时间: 2023年1月3日(星期二) 晚上7:41
@.>;
@.@.>;
主题: Re: [juanfont/headscale] Unable to install (Issue #1060)

./ is the current dir as a relative path.
Sockets usually fo into /run, but you are free to do as you see fit.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

@Frankzhang854 commented on GitHub (Jan 3, 2023): Please ask, the same configuration file, and the client version remains unchanged, headscale_0.18.0-beta2 cannot open the exit node, but headscale_0.18.0-beta1 can open the exit node, thank you My English is very bad, please forgive me ------------------&nbsp;原始邮件&nbsp;------------------ 发件人: "juanfont/headscale" ***@***.***&gt;; 发送时间:&nbsp;2023年1月3日(星期二) 晚上7:41 ***@***.***&gt;; ***@***.******@***.***&gt;; 主题:&nbsp;Re: [juanfont/headscale] Unable to install (Issue #1060) ./ is the current dir as a relative path. Sockets usually fo into /run, but you are free to do as you see fit. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***&gt;
adam commented 2025-12-29 01:28:13 +01:00
Author
Owner
Copy Link

@Frankzhang854 commented on GitHub (Jan 3, 2023):

Please ask, the same configuration file, and the client version remains unchanged, headscale_0.18.0-beta2 cannot open the exit node, but headscale_0.18.0-beta1 can open the exit node, thank you
My English is very bad, please forgive me

------------------ 原始邮件 ------------------
发件人: "juanfont/headscale" @.>;
发送时间: 2023年1月3日(星期二) 晚上7:41
@.>;
@.@.>;
主题: Re: [juanfont/headscale] Unable to install (Issue #1060)

./ is the current dir as a relative path.
Sockets usually fo into /run, but you are free to do as you see fit.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

@Frankzhang854 commented on GitHub (Jan 3, 2023): Please ask, the same configuration file, and the client version remains unchanged, headscale_0.18.0-beta2 cannot open the exit node, but headscale_0.18.0-beta1 can open the exit node, thank you My English is very bad, please forgive me ------------------&nbsp;原始邮件&nbsp;------------------ 发件人: "juanfont/headscale" ***@***.***&gt;; 发送时间:&nbsp;2023年1月3日(星期二) 晚上7:41 ***@***.***&gt;; ***@***.******@***.***&gt;; 主题:&nbsp;Re: [juanfont/headscale] Unable to install (Issue #1060) ./ is the current dir as a relative path. Sockets usually fo into /run, but you are free to do as you see fit. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***&gt;
adam commented 2025-12-29 01:28:14 +01:00
Author
Owner
Copy Link

@Frankzhang854 commented on GitHub (Jan 4, 2023):

But if you don't modify it, headscale can't run. I don't know where my installation method is wrong.

------------------ 原始邮件 ------------------
发件人: "juanfont/headscale" @.>;
发送时间: 2023年1月3日(星期二) 晚上7:41
@.>;
@.@.>;
主题: Re: [juanfont/headscale] Unable to install (Issue #1060)

./ is the current dir as a relative path.
Sockets usually fo into /run, but you are free to do as you see fit.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

@Frankzhang854 commented on GitHub (Jan 4, 2023): But if you don't modify it, headscale can't run. I don't know where my installation method is wrong. ------------------&nbsp;原始邮件&nbsp;------------------ 发件人: "juanfont/headscale" ***@***.***&gt;; 发送时间:&nbsp;2023年1月3日(星期二) 晚上7:41 ***@***.***&gt;; ***@***.******@***.***&gt;; 主题:&nbsp;Re: [juanfont/headscale] Unable to install (Issue #1060) ./ is the current dir as a relative path. Sockets usually fo into /run, but you are free to do as you see fit. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***&gt;
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#393
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?