• 0 Posts
  • 13 Comments
Joined 2 months ago
cake
Cake day: March 16th, 2025

help-circle



  • Some advice, TrueNAS isn’t very newbie friendly. Between permissions and their wonky kubernettes setup that no containers actually leverage, it’s not great. It is free, but expect bumps in the road. Unraid and OpenMediaVault are much easier to use. I switched to Unraid, and it’s been amazing, I highly recommend it. It’s nice that you can install random sized drives, they don’t need to match. You can toss in a few ssds for cache, and the docker containers are super easy to setup and maintain. Jellyfin works just fine for instance. OMV has some great offerings too, but lack the docker/VM hosting side. It’s a NAS and nothing else. It’s expected to have proxmox or something hosted elsewhere that uses OMV as storage.

    #2 opinion, build your own NAS. Especially if you’ve already built your own Gaming PC, it’s pretty straight forward. Pick a low powered cpu, toss in some ram, a ton of hdds, and maybe some old graphics card you have lying around for transcoding or hosting local AI for kicks. You’ll get a lot more for your money this way.


  • A lot of people aren’t big fans of Nginx Proxy Manager, which is separate from Nginx. But I like it. It’s got a nice gui, and the part I really like is the letsencrypt ssl certs baked in. You can get a new one, for a new service with a click of a button, and it auto renews your certs, so you don’t have to worry about it once it’s set up.


  • So, something to note is that a lot of UPSs have a configuration for sensitivity. Your power actually fluctuates quite a bit, but you don’t notice. I have my UPS on the default sensitivity, and there have been a few instances of it going onto battery power when none of my other devices even flickered.

    So, with that in mind, I use NUT. My server has it setup and it’s set to gracefully shutdown after my UPS hits 25% battery remaining. That way false positives don’t shut it down, nor will small flickers, nor will an outage less than an hour or so. My UPS says I can run for about 90mins on current load.





  • I only had issues with the latest tag when dealing with the community apps. Some of them would randomly break and I’d have to roll back. Once I manually configured the docker settings using normal file mounts things were plenty stable. I think the issues were with the k8s community charts not with the underlying software. And that was fixed by just configuring it manually like however the dockerhub docs suggest.

    I would still have the occasional issue where a container would freeze and a force stop wouldn’t work, and spinning up a new one wouldn’t work because the ports were still used. But I traced that back to a bad ssd with write timeouts. I still think truenas’s k8s wrapper is buggy. Even if a container crashes hard, I shouldn’t have to reboot the system to fix it. I switched to unraid and have been blissfully happy since.


  • Not sure if you were aware of the recent (last year) drama with a major contributing group to the community apps. TrueCharts I think they were called? I had some truecharts containers and some straight truenas containers. Then TrueCharts ragequit and took down their repo. I ended up reinstalling all those apps manually because for the life of me I still couldn’t get the dumb truenas versions to work. Also, I wasn’t a fan of the pvc (or whatever it was called) storage containers that got used by default. Made eveverything more difficult. My advice is to use the truenas community apps as a learning tool to configure your own properly with the truenas software. I noticed the community apps would seriously take around a minute to restart, but the ones I made manually would takes seconds. Same docker image, never figured out why, maybe a k8s thing?


  • Might need more info about your setup. The reverse proxy probably has some logs you aren’t looking at. Most bots from what I’ve seen do ip:port scans hitting every ip and every port. Nginx reverse proxy manager or something similar isn’t going to forward ip:8123 to home assistant. A straight router port forward will, but the reverse proxy manager will look at the domain GET request for https://ha.hit_the_rails.net to your LAN ip:port. It’s a little security through obscurity as they have to know your sub+domain.

    For a time I had port 22 open and forwarded directly to a server. Constant bot traffic. Changed the port, put an ssh honeypot on 22, and it almost completely went away. Sure the bots could be smart enough to scan and find another open ssh port, but they rarely did. I assume because anyone savvy enough to change the ssh port is savvy enough to not allow default logins like ubnt:ubnt and root:1234 which were by far the most common logins I got in the honeypot.