TrueNAS CORE 13.3-RELEASE in August

Nightly has 1.66.0

2 Likes

Something i can’t understand: example, integrated Shell has been removed, due to problem that everyone used It know well… Fair and legit for me.
Despite, plugin are still there, and people still try to use them (same for me some months ago, until community users advice me). Just why :melting_face:

Beats me, @etorix, @Stux, @dan, @Redcoat, @joeschmuck, and even @winnielinnie! I can only suppose some enterprise users are running some. We fought a years-long battle before iX removed plugins from their feature advertising of CORE.

2 Likes

I remember that. One of the few things I can remember such as the FreeNAS version which will not be mentioned, oops. :crazy_face:

I actually miss the shell as well in the GUI, it was convenient in spite of its pitfall. It actually forced me to log into the TrueNAS GUI periodically. I can say, I log in maybe once a week now, or less.

As usual I will upgrade to 13.3 shortly after it comes out but that is just to ensure script compatibility, not because I have any problems being fixed by the update. That is the good thing about multiple boot environments :wink:

How so?

Beats me, too. Just as does the number of people who apparently do no research/reading before installing TrueNAS and committing data to it.

I’m having trouble understanding how logging into the GUI and navigating to the shell is more convenient than typing ssh user@truenas in a terminal window.

I agree, especially when you combine the result with not having to deal with the vagaries of shell.

That requires an SSH connection to be configured and set up using a config file and known hosts, or having to type you password every time.

For me Is like more a bait.
Only recently plugin are documented as unsupported, but still in the GUI no alert Is show about that.

The known hosts will be taken care of the first time you connect. And you have to type your password every time with the GUI anyway (though I’m assuming joeschmuck would have public key authentication set up). I’m not sure what you mean about “a config file;” I’ve not had any need for one on Mac, Windows, or Linux clients.

.ssh/config is very handy though for different profiles on frequently accessed machines.

Plugins have long been a pain point with us. iX had the bright idea, they put it in the GUI, they put minimal effort into maintaining it, and left the community (us) to pick up the pieces. Frustrating to say the least, as you can probably tell from my phrasing, and yes, a bit of a bait-and-switch.

But I think Redcoat’s referring more to people who choose completely inappropriate hardware (perhaps on the basis of a YouTube video saying something like, “turn your old junk into a NAS!”) and completely inappropriate pool configuration, and then come here (or to the old forum) with their hair on fire when they’ve lost irreplaceable data.

I run commands from the shell often. Right now I have to open an SSH window from my computer, not the GUI, however before I would open the GUI and jump into the Shell from there so I would at least look at the GUI to see if anything was of concern. So now I log into the GUI significantly less. Keep in mind that most of my time on TrueNAS is spent working my little scripts and that is from a shell. Otherwise TrueNAS is just a great place to store data for me and I appreciate that very much. I don’t even use Plex anymore.

This is just how I use my machine.

2 Likes

The config file is to specify keys and connection when typing say ssh tnc in my case. It can be configured like this.


Host tnc
        HostName 192.168.10.65
        User root
        IdentityFile ~/.ssh/otherkeyname
Host tns
        HostName 192.168.60.18
        User root
        IdentityFile ~/.ssh/keyname
Host tnb
        HostName 192.168.30.11
        User root
        IdentityFile ~/.ssh/keyname

But my root password is a long random string, and I don’t want to have to type that every time.

Edit: I believe you can also specify your password with the config file. Correct me if I’m wrong.

2 Likes

Key pairs all the way.

1 Like

For me the No1 reason for not removing shell access within the UI is support. How often do we ask someone with an issue to run a command from the shell? Just imagine having to walk them through ssh access before we even get started.

3 Likes

Correct!

Yep, my quote was dumb, sorry :face_with_spiral_eyes:

We are sticking with the plan documented in April last year.

Ongoing Support for Plugins

Today, the majority of TrueNAS users are running TrueNAS CORE. Those users have a choice of staying with CORE or migrating to SCALE. Given the reliability issues of CORE plugins described above, iX intends to only support these plugins until early 2025. For TrueNAS Enterprise 13.0 customers, official plugins will be supported for appliances covered by a support contract.

In the next two years, we expect CORE users to either:

  1. Migrate their plugins to personally managed jails and remain on CORE
  2. Migrate from CORE to SCALE and rebuild their applications using the simpler Apps or VMs

We are sharing these recommendations so users have ample time to plan. We expect TrueNAS SCALE to significantly improve in both functionality and quality during that time. Notably, the migration process from CORE to SCALE is a major focus for polish and documentation, intending to drastically simplify migration before the end of plugin support in 2025.

2 Likes