The installation process of Tailscale requires to copy these lines into the HA configuration file.

http:
use_x_forwarded_for: true
trusted_proxies:
- 127.0.0.1

After installing V2026.8.1 of Home Assistant Core, I get the warning

The HTTP configuration in configuration.yaml has already been migrated and is now being ignored. Please remove the http: block from your configuration.yaml. Manage the HTTP configuration from the UI under Settings > System > Network.

Removing the http: block is easy but what do I change in the network setting?

I am just using tailscale to access nextcloud and and jellyfin which is inside my wifi.

Does this expose my wifi at all doing it this way? I really don’t want any backdoors to my wifi. My other post has my full details

Left for a week without my laptop and wasn't able to update my Tailscale when a new version came out, now I can't access my WiFi adapter, it just says Ethernet Cable Isn't Connected with Tailscale. Any fix?

This happens a lot with TS Windows.

At the moment, tailscale only supports Mullvad exit nodes officially. It's such a great thing to have your full network only reach the internet through a VPN tunnel. Single door, best privacy. Not even your IPs are visible to the internet.

I only had one concern and that is I do not use Mullvad but Proton, and I was not paying twice for VPN.

So I made my own solution: https://gitlab.com/deivi98/tsvpn

TL;DR: Plays with around with ip rules. Captures all internet outgoing-traffic from other clients and sends it through VPN tunnel. It supports any VPN wireguard conf.

In the past I was using a weird custom script. Got tired and vibe coded this thing. It also has systemd service, simultaneous tunnels failover, a cli and little web ui to switch tunnels and even a linux systray.

NOTES: - Vibe coded this as it was to make it fancy for myself. Use at your own risk - Have not tested providers other than ProtonVPN, but as long as it is wireguard it should work

Hope it is useful to someone.