Phil_Goodwin is managing a Discourse installation and received a notification to upgrade from 2.5.0 to 2.5.1. He attempted to use the one-click upgrade link but encountered a “page doesn’t exist or is private” error on both his local sandbox and production environments, despite being logged in as admin. He also noted the release notes link redirected to 2.6.0 beta, raising confusion about whether it’s the same release. The admin dashboard flags the update as critical but offers no upgrade instructions. Stephen asked whether the sandbox was a developer install or third-party package; Phil clarified it’s a developer install deployed via Ansible, Docker, and Nginx. Stephen explained that /admin/upgrade is not available in developer builds and advised consulting the original deployer. pfaffman emphasized that developer installs are not suitable for production use. The team can only support the standard install.
I inherited a Discourse install that I am trying to just keep running. I got an email recently saying that I should upgrade to 2.5.1. There was a link advertising an easy one-click upgrade, but when I translate that link to my sandbox site it says " Oops! That page doesn’t exist or is private." (I am logged in as admin and can see the admin dashboard). When I clicked on the link for the release notes it took me to the release notes for the 2.6.0 beta, not the 2.5.1 release. Are these the same?
The admin dashboard says this is a critical update, but doesn’t provide information for how to update it. I’m concerned that my installation might be misconfigured or something. Is there some other mechanism for initiating the upgrade, or something I should fix with my installation so that the ‘admin/upgrade’ path will take me to a page where I can initiate the upgrade?
I’m sorry. I was completely unclear. I have an instance of the site running in a VM on my local machine which is called “sandbox”. I don’t think it’s relevant – I get the same message in production as well.
Also, it’s a developer install. We’re provisioning it via Ansible and connecting to it through the Rails gem. It’s deployed into a Docker container and served via Nginx.
Ok, so you wouldn’t expect /admin/upgrade to be present in that build. If the live environment is similar then you’re going to have to consult whoever deployed that installation.