Cobar Posted March 17, 2022 Share Posted March 17, 2022 I updated my test environment to 4.6.11 last week with no issues, but when trying that now in my production environment, I get the "Manual action Required" error message on step 2. I've done a search and it looks like you typically need to fix this on the backend when it occurs. Is that the case here? Thanks, John Link to comment Share on other sites More sharing options...
Management Matt Posted March 17, 2022 Management Share Posted March 17, 2022 Hi John, This can occur for a variety of reasons. We generally suggest taking the long route of downloading the files, uploading them via FTP and running the /admin/upgrade/ upgrader. Link to comment Share on other sites More sharing options...
Cobar Posted March 17, 2022 Author Share Posted March 17, 2022 Thanks Matt. I've seen mentions of that but those responses for when the error was thrown in step 4. In September someone else also reported this issue on Step 2 (initial authentication step) and you did something on the backend to address. Will you please confirm that's not the case here before I invest the time to do this manually? It seems odd that this worked last week on the test environment which is on the same server. Thanks, John Link to comment Share on other sites More sharing options...
Management Solution Matt Posted March 17, 2022 Management Solution Share Posted March 17, 2022 @Cobar The issue is caused by GitHub being down right now. The build process pulls from the latest tagged release, and as GitHub is currently experiencing issues, it's failing there. Once GitHub is back up, it will work fine.https://www.githubstatus.com Link to comment Share on other sites More sharing options...
Cobar Posted March 17, 2022 Author Share Posted March 17, 2022 Thanks for saving me the hassle of doing this manually. I'll try again tomorrow. Matt 1 Link to comment Share on other sites More sharing options...
Recommended Posts