I did the manual upgrade via command line and my web upgrades are still disabled
AI-generated summary
Upgrades via the web UI are disabled
Bobby365 reported that after a manual upgrade via the command line, web upgrades are still disabled. Ed_S suggested checking for browser cache issues and rebuilding the app again. JammyDodger recommended running git pull and rebuilding the app.
Bobby365 confirmed they are running the latest version (2.9.0.beta4) and have already restarted the server. Maiki asked for clarification on what “disabled” refers to, wondering if it’s just a lack of available upgrades.
Bobby365 provided screenshots showing the disabled upgrade buttons. JammyDodger asked if a second rebuild has been attempted.
Falco mentioned that the experimental aarch64 image arch is failing to automatically pull in the last image during rebuilds, which may be related to the issue. However, Falco later provided a fix for the problem.
3 Likes
First, check that you’ve waited long enough for everything to start, and that you don’t have some kind of browser cacheing getting in the way.
But, it can happen that a second rebuild will do the trick, so that’s worth a try.
2 Likes
I think a git pull can help too:
cd /var/discourse
git pull
./launcher rebuild app
1 Like
Im on 2.9.0.beta4 so im up to date
1 Like
It says I’m up to date and I already did a server restart
2 Likes
When you “disabled”, what does that refer to? Do you mean the buttons on the upgrade page are not clickable?
Could it be there are no upgrades to be had? 
1 Like
As u can see im up to date
1 Like
And a second rebuild hasn’t helped?
2 Likes
The experimental aarch64 image arch is indeed failing to automatically pull in the last image during rebuilds, it’s on my list to investigate why next week.
9 Likes
This should fix it
5 Likes