• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Application Vault - Application not updated anymore

Here is what I have described in my Plesk feature suggestion below:

Moodle 4.0 Upgrade in Web Applications


"According to Plesk Obsidian's Documentation for Web Applications at Web Applications regarding "Updating Apps," by default, Plesk installs the latest available app versions and updates apps immediately once the newer versions are available.


However, this is not true because Plesk offered for the past year 2021 an outdated version 3.10.4 of the Moodle App. Recently Plesk released a Moodle update to version 3.10.10, for which the security support period ended on 9 May 2022 (see Roadmap - MoodleDocs for more details). For most people and their organizations, this is a major security risk.


It should not be a too complicated task for the Plesk developers to prepare an update for Moodle 4 since the latest release of Plesk Obsidian already meets Moodle's server requirements described at Moodle 4.0 release notes - MoodleDocs. "


Hopefully, after receiving our votes, the Plesk product managers will take into consideration this feature suggestion and start working on this request shortly.
 
Well, I took some time and successfully installed Moodle 4.0.1 on the Plesk server using the following steps:
  • Go to target domain overview page.
  • Ensure domain PHP handler is 7.4 or higher
  • Go to 'Databases' and create database to be used by Moodle and associated database user - you will be prompted to enter them during installation.
  • Go to domain overview page -> Git.
  • Select 'Remote repository' option.
  • in 'Repository URL' type or paste 'GitHub - moodle/moodle: Moodle - the world's open source learning platform'
  • Click 'Create' button and wait until process finished.
  • Click 'Branch'.
  • Select branch 'MOODLE_400_STABLE'.
Screenshot 2022-05-31 at 15.44.38.png
  • Click 'Pull now' and then 'Deploy now'.
  • Open file manager for domain and ensure index.html is absent in domain document root folder. Delete or rename it if necessary.
  • Open domain in browser - it should proceed to Moodle installation page.
  • Proceed with Moodle installation.
Now I see Moodle and I hope it is ok (I know nothing about Moodle):

Screenshot 2022-05-31 at 16.03.41.png
 
Well, I took some time and successfully installed Moodle 4.0.1 on the Plesk server using the following steps:
  • Go to target domain overview page.
  • Ensure domain PHP handler is 7.4 or higher
  • Go to 'Databases' and create database to be used by Moodle and associated database user - you will be prompted to enter them during installation.
  • Go to domain overview page -> Git.
  • Select 'Remote repository' option.
  • in 'Repository URL' type or paste 'GitHub - moodle/moodle: Moodle - the world's open source learning platform'
  • Click 'Create' button and wait until process finished.
  • Click 'Branch'.
  • Select branch 'MOODLE_400_STABLE'.
View attachment 20905
  • Click 'Pull now' and then 'Deploy now'.
  • Open file manager for domain and ensure index.html is absent in domain document root folder. Delete or rename it if necessary.
  • Open domain in browser - it should proceed to Moodle installation page.
  • Proceed with Moodle installation.
Now I see Moodle and I hope it is ok (I know nothing about Moodle):

View attachment 20906
Hi @IgorG ,

Thank you for the detailed installation instructions. They are great workaround on how to install Moodle 4, but in my case I need to upgrade my existing Moodle version 3.10.10 installation to version 4.0.1.

Do you have any instructions how to do that?

Thank you in advance!
 
Here is what I have described in my Plesk feature suggestion below:

Moodle 4.0 Upgrade in Web Applications


"According to Plesk Obsidian's Documentation for Web Applications at Web Applications regarding "Updating Apps," by default, Plesk installs the latest available app versions and updates apps immediately once the newer versions are available.


However, this is not true because Plesk offered for the past year 2021 an outdated version 3.10.4 of the Moodle App. Recently Plesk released a Moodle update to version 3.10.10, for which the security support period ended on 9 May 2022 (see Roadmap - MoodleDocs for more details). For most people and their organizations, this is a major security risk.


It should not be a too complicated task for the Plesk developers to prepare an update for Moodle 4 since the latest release of Plesk Obsidian already meets Moodle's server requirements described at Moodle 4.0 release notes - MoodleDocs. "


Hopefully, after receiving our votes, the Plesk product managers will take into consideration this feature suggestion and start working on this request shortly.
Please vote here : Moodle 4.0 Upgrade in Web Applications
 
Well, I took some time and successfully installed Moodle 4.0.1 on the Plesk server using the following steps:
  • Go to target domain overview page.
  • Ensure domain PHP handler is 7.4 or higher
  • Go to 'Databases' and create database to be used by Moodle and associated database user - you will be prompted to enter them during installation.
  • Go to domain overview page -> Git.
  • Select 'Remote repository' option.
  • in 'Repository URL' type or paste 'GitHub - moodle/moodle: Moodle - the world's open source learning platform'
  • Click 'Create' button and wait until process finished.
  • Click 'Branch'.
  • Select branch 'MOODLE_400_STABLE'.
View attachment 20905
  • Click 'Pull now' and then 'Deploy now'.
  • Open file manager for domain and ensure index.html is absent in domain document root folder. Delete or rename it if necessary.
  • Open domain in browser - it should proceed to Moodle installation page.
  • Proceed with Moodle installation.
Now I see Moodle and I hope it is ok (I know nothing about Moodle):

View attachment 20906
I was doing a clean install so this worked. Thanks
 
Well, I took some time and successfully installed Moodle 4.0.1 on the Plesk server using the following steps:
  • Go to target domain overview page.
  • Ensure domain PHP handler is 7.4 or higher
  • Go to 'Databases' and create database to be used by Moodle and associated database user - you will be prompted to enter them during installation.
  • Go to domain overview page -> Git.
  • Select 'Remote repository' option.
  • in 'Repository URL' type or paste 'GitHub - moodle/moodle: Moodle - the world's open source learning platform'
  • Click 'Create' button and wait until process finished.
  • Click 'Branch'.
  • Select branch 'MOODLE_400_STABLE'.
View attachment 20905
  • Click 'Pull now' and then 'Deploy now'.
  • Open file manager for domain and ensure index.html is absent in domain document root folder. Delete or rename it if necessary.
  • Open domain in browser - it should proceed to Moodle installation page.
  • Proceed with Moodle installation.
Now I see Moodle and I hope it is ok (I know nothing about Moodle):

View attachment 20906
it also works for an upgrade from Moodle 3.10.10 to 4.0.4
 
Back
Top