Https://club-automobile.webtest.cern.ch

Hello, the preview/temporary D9 copy of the Automobile Club website on the Cloud infrastructure https://club-automobile.webtest.cern.ch is not working. I obtain the error message: The website encountered an unexpected error. Please try again later. What I need to proceed?
Cheers,
Fabio

Hi Fabio

Thanks for raising this; I will be flagging this accordingly.

Thanks!

Dear Joachim, the site is still not working and rise the same error. It means the site is not portable to D9?
Thanks.
Cheers,
Fabio

Dear Joachim, the site https://club-automobile.webtest.cern.ch is now up and running, but I’m surprised that the drupal core version is 8.9.19 and not 9! It is correct ?
Cheers,
Fabio

Hi Fabio

Good to hear things are up and running! That is correct though; right now your website has been migrated to the new cloud infrastructure (OpenShift). The next step, as outlined in On the November 2nd Deadline, is upgrading compatible websites to Drupal 9. This process will commence next week. According to https://club-automobile.webtest.cern.ch/en/admin/reports/upgrade-status, your website is compatible. No further actions are necessary from you; the upgrade will be completed automatically.

Thanks!

Great ! Thanks to you :slight_smile:

Dear Joachim, I can see that there are updates for the https://club-automobile.web.cern.ch/en/admin/reports/updates site. In fact the drupal core seems to be still the version 8.9.20 and it was supposed to migrate “automatically” to version 9 last November. I tried to download the updates and install them but I had the error message: “Automatic updating of Drupal core is not supported. See the upgrade guide for information on how to update Drupal core manually.” How I should proceed to update to the version 9? Thanks. Fabio

Hi Fabio

I will flag your website as attempting to sign-in throws an invalid parameter: redirect_uri error. While upgrades to Drupal 9 have commenced automatically without any action necessary from website owners, a copy of each website is always tested before the upgrade is rolled out to production. It is likely that the above SSO issue halted the process in your case. Updates to follow.

Thanks!