On today’s episode of TrueNAS Tech Talk, Kris and Chris do a quick review of the latest 25.10-RC1 update, along with an answer to the question of “What’s that new icon in the toolbar?” - introducing the public preview of TrueNAS Connect, available for use now alongside 25.10-RC1! From inventory management to custom enclosures, enhanced alerting to headless, web-driven installation - find out what Connect brings to the TrueNAS experience. They’ll also tackle some viewer questions from the comments on Spotlight search, a built-in file manager, and how feasible rebootless updates might be in the future. All this and more ahead today!
How will the installer know to reach out to a local instance instead of the cloud one?
Do other software packages solve this in a tidy way? (special preparation of the installer media, mDNS trickery, PXE?)
The installer isn’t actually “reaching out” to a cloud service, it’s broadcasting an mDNS record on your local network. So a “hypothetical” self-hosted TrueNAS Connect shouldn’t have any issues spotting it.
TrueNAS Connect looks amazing, especially for email setup and auto-SSL. This is a huge timesaver; I was going to setup tailscale serve, but this seems to be an instant solution.
Just setup a couple of new TrueNAS systems yesterday to test this, and it all seems pretty cool, if the future cost is lower, I’ll consider it.
One thing I want to point out, is I had to use either Github, or Google to signup, I think this is not good, I hate signing into anything using some other account, specially Google of all things, I prefer to “Sandbox” all of my services or accounts, fresh emails and logins for each.
I would like to see a third option to sign up using an email address on it’s own and not tying/linking my Github account to TrueNAS.
Double posting, but, I just found a major issue with this Connect.
3 out 4 of my servers will connect perfectly fine, the fourth will not, have tried several times, all the others I have left the default ports to 80/443 and the forth server is 90/444 because it host nginx and it wont function correctly if the TrueNAS GUI is set to 80/443
So this is another issue from not being able to assign a unique IP address to each app/container and instead they all share the same IP, this is not the only app that has this issue, but the fix/workaround has now created an issue with something else down the line.
I only run nginx for Vaultwarden as you can’t use that without a valid SSL cerificate on my private local network, which I still struggle with, I still don’t see the point of secure web services on my private network, but it is what it is, I can’t see any of this being resolved without being able to easily assign individual IP addresses to each app like you can with Hypervisors and VM’s and let each app use the ports to developers intended them to use, changing the ports to suit TrueNAS is not the correct way to do it, instead TrueNAS should just create bridges and not NAT’s for virtual network adaptors per container and let my DHCP server feed them an IP address.
