To be clear I’m a beginner and I’m a bit overwhelmed with all the information I found and not completely sure if the information I found is up to date or outdated and I figured I would just ask here to get some clear answers.

What I want to achieve:

  • have TrueNAS Scale web GUI and installed apps like Nextcloud or Photoprism be remotely accessible
  • have that remote access be secure
  • use my registered domain instead of the IP address of my server to access the TrueNAS Scale web GUI and the installed apps
  • don’t have certificate warnings when accessing all this over HTTPS

Can someone explain to me how I achieve this or point me to a guide that walks me through it? I appreciate any help I can get.

I already managed to setup Tailscale and managed to access my server through that but then I got stuck on how to set it up to use my registered domain name to access the server.

So the next thing I tried was using the DynDNS of my Fritzbox but unfortunately it seems that Cloudflare (where I have registered my domain) does not provide a “update url” which the Fritzbox DynDNS GUI requires to set it up. This was to use it in combination with port forwarding and Wireguard (this is the guide I was following: https://www.wundertech.net/how-to-set-up-wireguard-on-truenas-scale/)

I also found this guide: https://notthebe.ee/blog/easy-ssl-in-homelab-dns01/ but that’s for servers without TrueNAS and I don’t think I’m experienced enough to transfer it and apply it to TrueNAS.

So yeah, I’m overwhelmed by information and I need help.

  • kostel_thecreedEnglish
    4·
    1 year ago

    To connect via a domain name I would recommend using a VPS as a reverse proxy to your server. This is easily done by initiating a Wireguard connection to the VPS, then connecting to your home server via the domain which points to the VPS’s ip. Quick google search got me this.

    And for wolfgang’s blog, all he’s doing is setting up NPM then pointing Nextcloud’s ip+port to his domain name (which is a DuckDNS). For truenas scale I found this, which basically says that Traefik is a better reverse proxy for scale.

    Note: I have not used TrueNAS Scale at all, so take my info with a grain of salt. I personally feel as if using Proxmox and then making 1x TrueNAS Core and 1x Linux containers would be easier, but I digress. Let me know if you have questions.

    • cipherpunk@discuss.tchncs.deEnglish
      1·
      1 year ago

      I will echo this. I’m pretty new to homelabbing (I got a Synology NAS a year ago but have just gotten more serious about is and built a new machine last week that I have installed Proxmox and TrueNAS Core on). I haven’t set up remote access yet on the new machine, but for my Synology I have a VPS with Nginx (not NPM just vanilla Nginx) pointing to a VM on the Synology that also has Nginx, with a Wireguard tunnel between them. The VPS uses Nginx to forward ports 80/443 to the local VM (if the headers have appropriate URLs), then the local VM uses Nginx to forward the requests to the locally hosted services.

      I’m thinking about dabbling with Traefik to set things up with my new machine, but the VPS+VM (or a container) with proxy capabilities is the way to go. And, of course, have your domain point to the VPS.