check_upgrade: "Updating repositories metadata" returned error code 1
-
If you send me your NDI in chat I can check it.
-
@stephenw10 I have the same issue
-
Send me your NDI and I'll check it.
-
@stephenw10 thanks! I’ve sent it on the chat
-
@stephenw10 after upgrade to 24.11, i get this error.
Can you help me?
Thanks -
You are seeing no branches like that?
-
@stephenw10 Hi, we have the same problem, pfSense+ 24.11. The problem appeared since about 3 days ago.
-
It's showing as unregistered. Send me your NDI in chat and I'll check it.
-
I too have this exact problem.
-
Hello,
I have exactly same issue. I am running pfSense on Proxmox. It was all good until couple days ago i've notices empty branches and dashboard shows community edition. If i enter activation token again, it accepts it but dashboard still showing community and no updates/branches available. How can we proceed? -
Send me your NDI and order number in chat and I'll check it.
-
@stephenw10 Thank you, meanwhile I am in touch with LEV from netgate TAC. Already know about interface amount vs NDI.
-
Ah, OK. They can check that for you then.
-
Today I upgrade pfsense 2.7.2 to version 2.8 after reboot it shows in my notices on the menu bar also :
Upgrade
check_upgrade: "Updating repositories metadata" returned error code 1 @ 2025-05-30 13:34:24 -
It may fail during the upgrade or at reboot. Does that message return if you clear it? Can you see the available packages list?
-
How can I clear this message? I only see x Close and Mark All as Read buttons. yes I can see available packages list.
-
Mark it as read and it should be removed from the dashboard.
-
Ok I will try it.
I did Mark All as Read. After I reboot pfsense. Notice come back again
Upgrade
check_upgrade: "Updating repositories metadata" returned error code 1 @ 2025-05-31 01:23:18! Before upgrading pfSense from version 2.7.2 to 2.8, I removed all the installed packages. After completing the upgrade, I reinstalled the same packages again.
-
This post is deleted! -
But it only returns if you reboot? It checks for updates periodically or if you refresh the check on the dashboard. If that isn't throwing the error then it's not a general issue but something at boot.
