6

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.

you are viewing a single comment's thread
view the rest of the comments
[-] cipherpunk@discuss.tchncs.de 1 points 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.

this post was submitted on 30 Jul 2023
6 points (75.0% liked)

Selfhosted

39677 readers
246 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS