Plugins and packages tabs are not populating?

Started by dinguz, December 18, 2024, 04:47:46 PM

Previous topic - Next topic
I noticed that starting with 24.7.11, the plugins and packages tabs are not populating anymore. Another thing I noticed, is the 'status' tab wheelie thing keeps spinning.
Are other people seeing this?
In theory there is no difference between theory and practice. In practice there is.

Means something wrong with local pacakge database or pkg stuck while trying to connect to the mirror.

What happens on the console if you run:

# pkg update -f


Cheers,
Franco

root@77-164-16-61:~ # pkg update -f
Updating OPNsense repository catalogue...
Fetching meta.conf: 100%    163 B   0.2kB/s    00:01
Fetching packagesite.pkg: 100%  245 KiB 250.8kB/s    00:01
Processing entries: 100%
OPNsense repository update completed. 861 packages processed.
Updating SunnyValley repository catalogue...
Fetching meta.conf: 100%    163 B   0.2kB/s    00:01
Fetching packagesite.pkg: 100%   22 KiB  22.5kB/s    00:01
Processing entries: 100%
SunnyValley repository update completed. 66 packages processed.
All repositories are up to date.

The tabs Changelogs, Plugins, Packages all remain empty.

Further info: this is a fresh install because of hardware changes. I installed 24.7 from USB and restored config.xml during install, upgraded to 24.7.10, reinstalled missing plugins, and after reconfiguring things because of changes in network adapter naming everything worked. It is after the upgrade to 24.7.11 that things started to go wrong.
In theory there is no difference between theory and practice. In practice there is.

> The tabs Changelogs, Plugins, Packages all remain empty.

> Further info: this is a fresh install because of hardware changes.

Ok, next idea: scold your browser for keeping a cached version of a 500 API responses?  :)

Try to clear the browser cache.


Cheers,
Franco

I chastised my browser, but this made no difference. This gave me an idea, because I access my OPNsense install through a Caddy reverse proxy. So I tried to access directly, bypassing the proxy, and now it works. So Caddy is the culprit here. Thanks for the suggestion!
In theory there is no difference between theory and practice. In practice there is.

Ah this silly issue.  They time out the firewall API proxy request after 3 seconds because caddy believes no answer will follow after 3 seconds of wait time.  I remember because Cedrik and me debugged and debated this for a bit.

At the moment there is a bug report on the caddy side, but I don't have the reference.


Cheers,
Franco