-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Latest config example contains deprecated key #2219
Comments
Sorry, can you elaborate on which key is wrong? |
Not the OP but if I were to guess: they are seeing this in their logs:
Which presumably is due to the key being explicitly set to false in the current default config:
|
iirc there were one or three I had to fix to get main working. sorry for incomplete report, I think I intended to self-assign when I opened this. |
"dns.use_username_in_magic_dns" |
nblock
added a commit
to nblock/headscale
that referenced
this issue
Dec 11, 2024
Upgrade the use of dns.use_username_in_magic_dns or dns_config.use_username_in_magic_dns to a fatal error and remove the option from the example configuration and integration tests. Fixes: juanfont#2219
6 tasks
nblock
added a commit
to nblock/headscale
that referenced
this issue
Dec 11, 2024
Upgrade the use of dns.use_username_in_magic_dns or dns_config.use_username_in_magic_dns to a fatal error and remove the option from the example configuration and integration tests. Fixes: juanfont#2219
nblock
added a commit
to nblock/headscale
that referenced
this issue
Dec 11, 2024
Upgrade the use of dns.use_username_in_magic_dns or dns_config.use_username_in_magic_dns to a fatal error and remove the option from the example configuration and integration tests. Fixes: juanfont#2219
nblock
added a commit
that referenced
this issue
Dec 11, 2024
Upgrade the use of dns.use_username_in_magic_dns or dns_config.use_username_in_magic_dns to a fatal error and remove the option from the example configuration and integration tests. Fixes: #2219
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a support request?
Is there an existing issue for this?
Current Behavior
current conf example does not match latest spec
Expected Behavior
match the latest spec
Steps To Reproduce
use the example conf file. it has a deprecated key.
Environment
Runtime environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: