Unable to upgrade from 23.01-RELEASE to latest version on Netgate 3100

Mastiff

Weird one. I first tried to update with the Home Assistant plug-in for pfSense. Then I tried the regular way in the GUI, and then I tried via command line, in the GUI,

pfSense-upgrade -d

I get timeouts (504) when doing that. So I tried to kill all static processes, which didn't help. Finally I activated SSH (never use it if I can avoid it) and logged in. And of course...

[23.01-RELEASE][Myusername@pfSense.mydomain.no]/home/Myusername: pfSense-upgrade -d
ERROR: It must run as root
[23.01-RELEASE][Myusername@pfSense.mydomain.no]/home/Myusername: sudo pfSense-upgrade -d
sudo: Command not found.
[23.01-RELEASE][Myusername@pfSense.mydomain.no]/home/Myusername: sudo su - Myusername
sudo: Command not found.

And now I'm getting 504 Gateway Timeouts when I try to go to the GUI update page too, even after a full reboot...
So does anybody know what I can do to get this working? I did luckily do a full backup before I started messing around, after the first attempt failed. So I guess doing a full reinstall is not out of the question, it's just very scary... I share the device with a bunch of neighbours, and I'm sort of the "digital superintendent".

stephenw10

Yes, you need to be logged in as admin/root to use pkg commands like that. Or setup sudoers to allow it.

You can run those from the GUI command prompt (which runs them as admin) as long as it doesn't require any interactive input.

I would ssh in as admin to see what the actual fault it here. Or use the console directly if you can.

Steve

Mastiff

@stephenw10 Thanks for answering! I just tried to run the update again now from the GUI, and it just started without problems! I have not done anything in the five days since I last tried, so I have no idea what has changed, but the problem seems to be solved! Maybe something in the connection between me and the update servers?

stephenw10

Could be. There was an IPv6 issue at the servers a few days ago. I thought it had been fixed before you posted here but maybe not. It's fixed now.

Steve