NPM can also do URL proxying: you can reach sub.maindomain.com
at maindomain.com/whatever/
. Edit the proxy host definition for the main domain and look in the “custom locations” tab.
Alternatively, if you can control your browser’s settings, you can try using DNS over HTTPS which can let you bypass your company’s DNS. Try using https://dns.quad9.net/dns-query
for example as the DNS over HTTPS address (or whatever your browser can offer).
Don’t self-host email SMTP or public DNS. They’re hard to set up properly, hard to maintain, easy to compromise and end up used in internet attacks.
Don’t expose anything directly to the internet if you’re not willing to constantly monitor the vulnerability announcements, update to new releases as soon as they come out, monitor the container for intrusions and shenanigans, take the risk that the constant updates will break something etc. If you must expose a service use a VPN (Tailscale is very easy to set up and use.)
Don’t self-host anything with important data that takes uber-geek skills to maintain and access. Ask yourself, if you were to die suddenly, how screwed would your non-tech-savvy family be, who can’t tell a Linux server from a hot plate? Would they be able to keep functioning (calendar, photos, documents etc.) without constant maintenance? Can they still retrieve their files (docs, pics) with only basic computing skills? Can they migrate somewhere else when the server runs down?
A
record to the IP of the VPS.I’m partial to the DIY PC option because it allows far more flexibility. If you can swing the space for the larger box IMO it’s the best way to go.
Some things to keep in mind when speccing the box:
Are you familiar with any Linux distro in particular? I would strongly recommend using Docker rather than native regardless of distro.
Here’s an idea, check out ytdl-sub: https://github.com/jmbannon/ytdl-sub
You can set it to track a YouTube channel and it will download videos and set up nice collections for you in Jellyfin, which you’ll never lose again and can watch without ads.
Please take such advice with a large grain of salt. OP’s experience is very much not the norm. Especially for more complex apps like Jellyfin or Nextcloud, it’s almost guaranteed you’ll break them if you just update blindly.
“Shared network folder” in Jellyfin doesn’t do what you think it does. 😛 I agree it’s rather confusing. It’s just a convenient link to a Windows share which you can open from the Jellyfin app if you want to browse the files and they happen to also be shared as a Windows share. It’s NOT where Jellyfin takes the files from.
Jellyfin can only index files accessible to it locally. Share the files from TrueNAS to the machine or container running Jellyfin, then point Jellyfin to the directory where you mounted the share. I recommend NFS rather than Samba for this purpose.