NO key necessairy, in the start-up trail it shows the option to which version you want to “downgrade/ restore”
Maybe it is because it is not the mainboard NIC, but a Nic card.
Okay, you didn’t reply to a specific post which made it harder for anyone else to know what you meant. The post directly preceding yours was related to a different issue running a benchmark. Also, as you can likely see in the followup posts from the OP, an issue remains, possibly linked to the network card.
The GUI settings default to binding to 0.0.0.0. As far as I can tell, this has been the case for many years and should be the case in Cobia as well. Address 0.0.0.0 tells TrueNAS to listen on all IPv4 interfaces and IP’s.
Is your system set to something other than 0.0.0.0 or did you find that when set to 0.0.0.0 it still didn’t work? If the latter I suggest you post your own thread on the issue because that sounds like unintended behaviour.
The problem as described Above (1 Post) , was that WebGUI IPwas NOT set .
After Setting and webgui IP in 25.04, I had WEBGUI in the 25.04.01 after upgrade
Pictures before setting webGUI IP ( Ipv4)
So it looks like you have no valid interface up.
- Which of those NICs do you have a cable attached to?
- Have you verified that the cable is connected correctly on both ends?
- There are two different networks visible on the second screenshot, which one is your client computer connected to?
- What is the output of
ip aandnetstat -tuln?
after setting webGUI to Fixed ip and webgui, instead of DHCP.
( so it could also be and DHCP problem, although i could ping to 240)
I could upgrade without any problem and acces to webgui
AS you can read in 1 st post Problem for me is solved
Okay, I guess you don’t need more help then.
Best of luck to you.
what the?
Why would I post my own issue in someone elses thread???
I was only ever remarking on the OP’s experience.
Which he clearly posted as solved to start with, thanks anyhow I guess.
If Neofusion would have started at the top, he could have saved himself some time.
Most of these threads only give the answers at the bottom if any
Then it may come as a surprise to you that I did read the thread from start to finish.
I posit that you (and the other person) came to the wrong conclusion as to what the cause was.
If it had been a new requirement (or possibly bug) to set a specific IP for the WebUI the forum would likely have been drowning in thousands of threads asking why they couldn’t access their UI post 25.04.1 update. As this has not happened it’s unlikely that the cause of your issues is as simple as you suggest. It could be that the issue is due to a combination of things or a different trigger entirely.
I interjected because I was trying to figure that out, but due to some kind of miscommunication never got anywhere with that.
It happens, you win some you lose some. Hopefully this interchange will be useful for someone else in the future.
Time to move on.
Must have been and IP network setting , which worked in my other upgrades and , didn’t work after this upgrade. Fixed(altered) the IP settings and the upgrade worked.
i am not going to re-try several options to figure out what was the exact cause.
i can send you my back-up file, if you can read the network settings in it to see what was missing or mis-configured
No, thank you.
One can also Try to get acces to the WEBgui with IPV6:
if that is shown in the Console.
for example : http://[2001:4c3c:2700:e603:b226:28ff:fee2:de81]:/8080.
Bold section is your individual IPv6 address