Beginner Basics • Re: Port forwarding through Proton VPN?

Just so I understand you have a hapax3 that gets a public IP.........

The hAP ax³ obtains a dynamic IP address from the upstream Virgin Media device. Before enabling the VPN, the Home Assistant system used the DuckDNS add-on to associate a public DNS name of the form <something>.duckdns.org with this IP address and manage the Let's Encrypt certificate used to secure the connection. This used port forwarding of port 8123/tcp for the remote connection (and port 80/tcp for the Let's Encrypt challenge).

The WireGuard 'Endpoint' provides another public IP. As the outgoing connection from the Home Assistant system is via WireGuard it is this IP address that DuckDNS has used to associate with the public DNS name.

If so you dont need Proton VPN for incoming, you can use your own router with wireguard to let remote users access home assistant.

Agreed. Traffic to and from the Home Assistant system could be routed through the public IP address obtained from the upstream Virgin Media device. Other outgoing traffic could be routed through WireGuard.

Even if its not a public IP ( behind an ISP router ) if you can forward a port on the ISP modem/router to your hap, you can run wireguard.
Even if you cannot forward a port you can run wireguard via BTH as an option.

I have a public IP.

PROTON is not required for what you are asking for in terms of a requirement for home assistant access.

Proton VPN wont do that for you.
If you still want proton vpn to allow some users to go out internet via proton you can do both at the same time.

Agree that a VPN isn't required for a remote connection to the Home Assistant system (as noted before, it worked before I enabled a VPN).

The original question was about port forwarding through Proton VPN. I think you are saying that a remote connection originating from outside cannot be port forwarded though the VPN?

Statistics: Posted by JohnConnett — Tue Jan 02, 2024 8:53 pm

---