Dear Home Assistant Community,
I’m currently working on a secure remote access solution for my Home Assistant setup and I’d love to get your insights before implementing it fully.
My Goal
I want to achieve secure remote access to Home Assistant while keeping my local access fully functional. Here’s the architecture I’m aiming for:
- Local Access:
- When I’m at home, I want to access Home Assistant via my local network (
192.168.1.X). - Even if my internet connection goes down, I still need Home Assistant to be accessible via WiFi/LAN.
- Remote Access (Secure):
- I do not want to expose Home Assistant directly to the internet (no open ports on my router).
- Instead, I have a VPS with a fixed public IP running WireGuard VPN.
- Only the VPS will be able to access Home Assistant via a WireGuard tunnel (
10.0.0.2).
My Proposed Configuration
To achieve this, I plan to configure Home Assistant to listen on both interfaces:
- Local network (
192.168.1.100) - WireGuard VPN tunnel (
10.0.0.2)
Here’s the configuration.yaml setup I’m considering:
http:
server_host:
- 192.168.1.100 # Local network access
- 10.0.0.2 # VPN access via VPS
use_x_forwarded_for: true
trusted_proxies:
- 10.0.0.1 # VPS WireGuard address
To secure this, I would also configure my firewall (ufw) to:
Allow local access (192.168.1.0/24)
Allow remote access only from the VPS (10.0.0.1 → 10.0.0.2)
Block direct access from the internet
My Question to the Community
Before implementing this setup, I’d like to confirm whether Home Assistant can properly handle two different IP addresses for access (one for local and one for VPN).
- Has anyone successfully configured Home Assistant with two listening IPs?
- Are there any known issues or conflicts when setting this up?
- Do you recommend any additional security improvements (SSL, 2FA, …)?
I appreciate any insights or feedback you can provide! Thanks in advance for your help. ![]()
![]()