marble acorn
Hi there,
I wanted to switch from DuckDNS to tailscale. But the way I did this did not quite work out. I stopped and removed the DuckDNS app first and then started to install the tailscale app as described here
But somehow it did not work this way. In the machines section of tailscale, the green funnel logo did not come up. And yes, I checked the funnel box and save the configuration of the app before I started the app. I added the code snippet to tailscales access control JSON file within the curly brackets.
// Added for Homeassistant 20.04.2026
"nodeAttrs": [
{
"target": ["autogroup:member"],
"attr": ["funnel"],
},
],
// Test access rules every time they're saved.
// "tests": [
// {
// "src": "alice@example.com",
// "accept": ["tag:example"],
// "deny": ["100.101.102.103:443"],
// },
// ],
}
I noted some existing code in the http section of my configuration.yaml when I added the nessesary snippet for tailscale. I think it was for DuckDNS but I am not sure what to do with it.
use_x_forwarded_for: true
trusted_proxies:
- 127.0.0.1
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
cors_allowed_origins:
- https://google.com
- https://home-assistant.io
ip_ban_enabled: true
login_attempts_threshold: 5
The ssl_certificate and the ssl_key do exist in the ssl folder.
Is there a way to subsequently enable the funnel function?
Do I have to delete the old http entries and their associated files?
Thank you in advance for your assistance.
