23.09.1

MaxK 0

I'm currently on 23.05. The dashboard shows that 23.09 is available (not 23.09.1). The only branches available are:

Previous Stable Version (23.09)
Depreciated Version (23.01)
Depreciated Version (23.05.1)

Does this mean I cannot update directly to 23.09.1?

stephenw10

It probably means it's unable to pull the repo update for some reason
Try running at the command line:
pkg-static -f update
pfSense-repoc

See what errors are shown.

MaxK 0

@stephenw10 As requested:

output.txt

stephenw10

Hmm, did you run 'update' or 'upgrade'?

That looks like it was upgrade. However it shows it's able to pull packages.

To confirm I'd try: pkg-static -d update

But it also looks to be pulling repo data correctly so it should show 23.09.1.

If you send me your NDI in chat I can check it.

Steve

MaxK 0

I had to upgrade from 23.05 to 23.09 then I could upgrade to 23.09.1

JimBob Indiana

23.09 to 23.09.1 keeps telling me unable to check update. Not going to get fancy in problem solving as the thing works like a charm as is on 23.09.

jrey

@JimBob-Indiana

The repo servers have been unavailable/offline for a lot of people, most of the day today.

Maybe just a case of waiting a bit.

PPCM

@jrey I am the same issue

Retrieving Unable to check for updates

Servers are still offline?

jrey

@PPCM said in 23.09.1:

Servers are still offline?

everything appear fine from here.

yon 0

@stephenw10

pfsense-plus-pkg.netgate.com DNS Record not found

stephenw10

https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#packages-netgate-com-has-no-a-aaaa-record

JimBob Indiana

@PPCM I'm not able to upgrade due to not finding the servers.

stephenw10

What error are you seeing?

PPCM

@stephenw10 The front page shows that an update is available, but on update page, after we change the branch to 23.09.1, the following message appears:

jrey

@PPCM

Strange as it sounds - try this

Go on the next tab over "Update Settings" and set the branch there. Save it .. then go to the dashboard (or some other page) but not directly back to the System Update tab
wait a few minutes (say 5 - grab a coffee or beverage of your choice)
then go the System Update page again ..

Same result?

stephenw10

Yes, that. Or just refresh the page will often allow it to update to the new branch. It can timeout while pulling the new branch data and updating to it.

jrey

@stephenw10 said in 23.09.1:

Yes, that.

The coffee or the second beverage?

netboy

@jrey 23.09 to 23.09.1 on 2100 went smooth without a hitch