I setup wg-easy, am I somehow exposed to attacks? - eviltoast

I configured wg-easy on my home-server (docker installation) and want to check if I missed something security-wise:

  • I port-forwarded UDP 51820 on my router
  • I have a domain which I purchsed, it’s managed in Cloudflare and I created an A record pointing to my WAN IP.
  • Not sure if it matters, but all I have for my wg.domain.com is a username/password authentication and it’s secured with an SSL certificate, which is obviously only valid inside of my LAN.

I currently assume that since I port-forwarded a UDP port, people can’t try and access MY_WAN:51820. Is it somewhat correct?

Any tips on this would be great. I’m not interested in exposing my setup to the internet, all I want is a secure VPN to sometimes access my network from my phone.

By the way, huge props to wg-easy, very quick and simple setup.

  • Simplixt@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    - Don’t expose the web interface of wg-easy ( 51821 ) to the internet
    - update your docker installation frequently
    - Keep the private keys of your clients safe

    That’s all you need to do.
    Personally I also would change the UDP port of WG (via different port forwards of your router). But more for getting through firewalls in public WiFis (e.g. UDP Port 443, 53 or 123)

    • d4nm3d@alien.topB
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      agreed on all of this however updating the docker container feels a little pointless with this one… it’s not been updated in over a year…

      Unless, by updating it is actually pulling an updated wireguard… do you know if thats the case?