Let's be clear: which server? The Joomla server (hosting the installation package to be used in the download) or the target server hosting the website.
Yes, I agree that there have been connectivity issues in the past with joomla.org and people have been unable to connect in order to obtain the updates. Yes, I agree that—for many reasons—the webhosting service(s) used by people who operate Joomla websites are the causes of people's inability to update Joomla. The solution—the simplistic solution to preferably
"navigate" to the download page [to] avoid human error—is one approach but it's not preferable. This approach may rule out human error but, once human error is eliminated (it sounds like something Sherlock Holmes would say), we should find out the true cause. I wouldn't say it's preferable (in all cases); it's just a line of investigation that can be followed.
Once the cause has been identified then we're ahead of the game.
I agree that there are dozens of possibilities for why the Joomla! Update
component doesn't work. These causes can include:
- outdated "server" certificates (at the site host or even at joomla.org)
- inadequate PHP quotas, e.g. Max. Upload Size, Max. POST Size, Max. Input Time, Max. Execution Time, Memory Limit
- missing, outdated or disabled PHP functions, e.g. curl, allow_url_fopen
- peculiar or buggy versions of PHP
- peculiar or unsupported browsers, e.g. IE 4
- peculiar or unsupporter webserver software, e.g. IIS
- .htaccess rules
- third-party extensions
- buffering, internet connectivity, ISP-related
- penguins flying over the satellite dish
- the phase of the moon or the alignment of the planets
- database "issues"
- when people have used "quickstart packages" to install God-only-knows-what-version of J! in the first place
- caching (server-side, browser and proxy, e.g. CDN)
- Russia and other countries who object to Joomla whenever they feel like it
We don't know what we don't know.