I’ve been trying to upgrade our TrueNAS Core 13.0 U6.7 to a TrueNAS scale version and it seems to upgrade OK after trying a few different ways but I can never get on the Web Gui afterwards.
I’ve seen its possible but I don’t know what I’m doing wrong, so I have done the following so far.
Upgraded from the Web Gui directly to the earliest stable version, backed up the configuration file first and it was successful, rebooted but couldn’t get back onto the Web Gui, I could ping the IP and get to the server share fine, just not the Web Gui.
Reinstalled Core again, attached the config file (worked fine) and then tried installing Scale 23.10 with an manual update file, was successful, rebooted and nothing again, same as above.
Reinstalled the full system with Scale 23.10 and then uploaded the config file afterwards and again same as above but I also couldn’t browse the share on the server either now.
It does seem to be taking the config file, as the IP is the same, the teamed NIC settings I set are still but I get nothing.
Is there a set version I need to be on before attempting an upgrade or uploading a config file to after a fresh install of Scale?
Why are you trying to upgrade to a version of SCALE that’s a year and a half (three major releases) out of date? The current version is 25.04. Granted that was only released yesterday, and you might not want that new of a release; in that case you’d upgrade to 24.10.
In any event, the supported upgrade path is to do a fresh install of SCALE, upload your config file to it, and you should be good. For more information, see:
I’m sure I tried with 24.10 as well but I had the same results, I tried an earlier version thinking it might be to new but I can try again and see if that works.
Its like I had an issue with the https redirect like I did previously, enabled that and I lost access to the Web Gui and I had to revert back with local server commands but that option has been disabled since and I save the configuration file afterwards.
Then a really important question would be exactly what you mean by “lost access to the the web GUI.” What, exactly, happens when you try to access it? Are you using the correct address? That would normally be the one displayed on the console.
So it just doesn’t load, page cannot be displayed but it did this when it was pingable as well.
It shows the correct IP on the server itself, although it shows https://IP_Address and http://IP_Address, so not sure if that means https redirect as enabled again, even though it was disabled when the config file was saved.
Could it be a problem that the teamed nic looses it’s members, because the interfaces have different names between core rand scale?
I’d propably remove the teamed config, try the udpate with a single configured nic and if the update is successfull re-do the team settings for the nics.
Correct me if I’m wrong, but I thought that I read here on this forum that a direct upgrade path from Core to Fangtooth was not supported and that you had to install a previous version of Scale if you wanted to do a direct upgrade. I of course tried to do a search to confirm but couldn’t come up with anything with the lousy search function. If the only supported upgrade is via fresh install that’s not a big deal to do so but running the upgrade from the GUI would be easier.
If anyone knows this for sure please respond as I plan on reluctantly upgrading to scale in the next couple of days.
TrueNAS users wanting to migrate from the latest FreeBSD-based 13.0-U6 or 13.3 CORE release to the Linux-based TrueNAS version 24.10 or later can migrate to 24.04 and earlier using the UI update process, but must clean install if migrating to later releases. Attempting to migrate directly to 24.10 or later releases using the UI is not supported.
I’ve just tried removing the teamed cards, made sure this has running on a single NIC, then tried upgrade from 13.0 U6.7 to Scale 24.04 via the Gui as it mentions in the documentation this is possible and not a later version as mentioned in the previous comments & documentation
Its rebooted, I can ping the server and also access the share Windows path, it has the same IP address that was set previously with it saying https://ip_address & http://ip_address but I still can’t accessible via the web Gui.
Well that sucks, we’re going to be having an internal penetration test soon and this agent needed to be installed but it had to be on a Linux based OS which I understand is Scale and not Core because Core is its own OS or it that not correct?
You can in theory install via custom app, or if you don’t mind decreasing the security of the OS for your internal security policies you can run the command install-dev-tools and then install via dpkg / apt and hope it doesn’t break
I have this issue also when upgrading from CORE to SCALE and also using LAGG / LACP bond. I find a reconfiguration of the network interfaces via the console clears things up. Not sure why it happens but it’s an easy enough fix.
God it sucks getting old.