Snapshot update for 23.xx?
-
Yes, it's an issue with the module name. Should be fixed in the next snap.
-
It was not possible to update to 23.05.b.20230427.2246 via the web interface. Updated via console. Wireguard is working. But the branch 23.05 again disappeared from the settings. There are only 23.01 and 22.05.01
-
Hmm, so you didn't see 22.05 beta offered at all?
Do you see the correct branches after upgrading at the CLI?
-
@stephenw10 said in Snapshot update for 23.xx?:
Hmm, so you didn't see 22.05 beta offered at all?
Do you see the correct branches after upgrading at the CLI?
I have seen.. Somehow it was not updated the first time. I went through the update of the web interface, but the version did not change. After updating through the CLI, the version has changed (I now have 23.05.b.20230427.2246), but I stopped seeing the 23.05 branch.
I don’t update the second router yet and it sees the 23.05 branch
-
Hmm, can you send me your NDI in chat?
It looks good on all the devices I have here.
-
Ok, that should be fixed (again!).
-
@stephenw10 said in Snapshot update for 23.xx?:
Ok, that should be fixed (again!).
all ok, i see 23.05 branch on 23.05.b.20230427.2246 device.
-
I can not understand. Installed to a friend pfSense 2.6. Registered Plus version. Updated to 23.01. Then I updated it to 23.05b. But it get the "Choose "pfSense Plus Upgrade" to upgrade to pfSense Plus
" message. Very strange.
-
Oh, so you were able to upgrade OK to 23.01 _and _ then to 23.05 but are still seeing the update message?
Almost certainly this: https://redmine.pfsense.org/issues/14137So that message is harmless but can be removed by manually running:
rm /usr/local/share/pfSense/pkg/repos/pfSense-repo-custom.*Steve
-
@stephenw10
Thanks a lot. Helped! The most interesting thing is that I got this result twice. Installed 2.6, got a plus key and then updated to 23.01. Then a friend's ssd broke and we got the plus key again and updated everything again. And so in both cases there was such message. Right now everything is ok, thanks!
