The user MrBug reports issues with upgrading Discourse via /admin/upgrade/, experiencing slow version checks and a 502 error when attempting to upgrade all components. The issue initially appeared to be related to internet connectivity, with the /admin/docker/latest?path=all endpoint failing. itsbhanusharma suggests the problem might be specific to the installation and asks about errors during ./launcher rebuild app. MrBug confirms no errors in the console and notes that individual upgrades work. Eventually, MrBug discovers the root cause: their VPS IP was blocked by Google, which disrupted connectivity to Google-related services, leading to the 502 error despite otherwise functional internet access.
Is this something work in progress and im just punished for updating every day? ^^
Because for a couple of days i cant upgrade anymore.
“Checking for new version…” Takes 8-10 seconds each, instead of being almost instant…
And after its done, pressing Upgrade All does nothing, just white empty space… With a 502 error when fetching something on /admin/docker/latest?path=all…
./launcher rebuild app did not help -.-
Help ^^
What error are You facing on ./launcher rebuild app?
I have just upgraded two of my installs this morning and that went just fine so this is probably specific to your installation.
I don’t know, i wasn’t exactly sitting there for 10 minutes reading the console ^^
Is there any logs for that?
Can it rebuild and run just fine and still have errors there?
Well.. definitely no errors there, just checked it -.-
Oh and upgrading works with individual upgrade buttons…
Somehow that was a hosting provider issue…
My vps was not able to connect or ping anything google related… and somehow this affects discourse…
They fixed it now, and everything works perfectly! 
Crazy stuff. huh…
It did not fail due to internet connectivity… Everything worked fine… Just google blocked my vps ip for some reason. That should definitely not transfer to 502 error on /admin/docker/latest?path=all… but it did ^^
