homeassistant

12083 readers

2 users here now

Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io

founded 1 year ago

MODERATORS

[email protected]

Duckdns/wireguard/... Which one do you prefer and why? (jlai.lu)

submitted 1 month ago by [email protected] to c/[email protected]

30 comments fedilink hide all child comments

Hi everyone

So, that's a 2 in 1 post. First a more general question then looking for advice for a friend.

What is your preferred way to access HA from outside (and why)?
a friend of mine use duckdns and I often read (recently) that some people are having issue with it. Is wireguard a better way or another solution that is not too techy to deal with?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 8 points 1 month ago (4 children)

Very different solutions.

DuckDNS: you expose your HA to the internet like a public website and register it's address with DuckDNS so you can look it up.
Wireguard: you VPN to inside your firewall and can access anything on your private network.

Wireguard all the way. Exposing just a VPN endpoint that can't be connected to without the right cryptographic keys is a much more secure and maintainable attack surface.

BTW I assume that's what you meant by "DuckDNS". Using that service is orthogonal to making HA visible externally, but is (I think) the common pairing.

[–] [email protected] 1 points 1 month ago (3 children)

Thanks, wireguard sound much better then for just accessing HA, wonder why is duckdns so popular then

[–] [email protected] 1 points 1 month ago (1 children)

@paf @wewbull maybe also have a look at Tailscale

[–] [email protected] 1 points 1 month ago

Will check that, thanks

load more comments (1 replies)