• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Search results

  1. M

    Question Update Phusion passenger

    Hi, How to update Phusion passenger on Plesk ? (6.0.13) of Phusion Passenger(R). We strongly recommend upgrading to version 6.0.18. [ E 2023-07-10 08:43:13.9333 435295/T5 age/Cor/SecurityUpdateChecker.h:526 ]: Additional security update check information: - [Fixed in 6.0.14] [CVE-2018-25032]...
  2. M

    Issue file 'plesk.list.ai_back' invalid filename extension

    I am still investigating the SSL issue since the Let's Encrypt update, and it appears that the problem stems from the ZScaler certification. Since the update, it requires domains to be whitelisted. Could you please provide me with the list of domains used for the update and maintenance of Plesk...
  3. M

    Issue file 'plesk.list.ai_back' invalid filename extension

    do you have any other ideas?
  4. M

    Resolved Intermittent cURL error 6 citing Let's Encrypt / Mozilla ciphers, server restart does not resolve

    Did you find a solution ?
  5. M

    Issue file 'plesk.list.ai_back' invalid filename extension

    the timezone is correct.
  6. M

    Issue file 'plesk.list.ai_back' invalid filename extension

    Arf no time for edit my post lol. So, i installed new server, but only core plesk is installed, impossible install extension or other dependencies. but all dependencies is installed ?! no wet, lol !? Repair : # plesk repair all -y Reconfiguring the Plesk installation Reconfiguring the...
  7. M

    Issue file 'plesk.list.ai_back' invalid filename extension

    New Thread N: Ignoring file 'plesk.list.ai_back' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension N: Skipping acquire of configured file 'all/binary-amd64/Packages' as repository 'http://autoinstall.plesk.com/pool/WPB_18.0.51_64 all InRelease' doesn't support...
  8. M

    Resolved URGENT Certificate location not specified in response Lets Encrypt

    Thank's, This fixed part of the problem. the situation remains unchanged. Maybe I'm wrong, but I still think I'm restricted by this SSL issue. - INFO: Executing upgrade task: 2015-06-23-17-35-48 (clean) - [2023-04-06 10:27:49.074] 174245:642e828511938 ERR [panel] Error in cURL...
  9. M

    Resolved URGENT Certificate location not specified in response Lets Encrypt

    With the error unable to complete the installation, the extensions are hibernated but inaccessible?! OS : Ubuntu 22.04.2 LTS Product : Plesk Obsidian - Version 18.0.51 Update #1 ----------------------------------------------------------- $ plesk bin extension --list...
  10. M

    Issue Nodejs App error EACCES on port 80

    thanks, no problem with deployment for nodejs. by adding the reverse proxy it works, but i never needed to do this before with my other applications in vuejs/nuxtjs/nextjs they are shared and globally developed on port 80 / 3000
  11. M

    Issue Nodejs App error EACCES on port 80

    My first topic for subject : Strapi on Plesk Windows, port redirect error
  12. M

    Issue Nodejs App error EACCES on port 80

    I understand that this is not very clear. my topic presents two examples, a launch of the application on port 80, and on port 8081; port 80 is necessarily open for the web. I understand that nodejs cannot open an additional service on port 80, but plesk does not run the application natively...
  13. M

    Issue Nodejs App error EACCES on port 80

    Strapi Version: 4.4.5 Operating System: Windows 2022 Datacenter + Plesk Obsidian 18.0.48 Database: MariaDB 10.6.9 Node Version: 16.16 NPM Version: 8.19.2 Yarn Version: N/A -> server.js module.exports = ({env}) => ({ host: '0.0.0.0', port: 8081, app: { keys...
  14. M

    Resolved GravCMS open_basedir restriction (Plesk Windows)

    I set the value to 'none' the installation went through
  15. M

    Resolved GravCMS open_basedir restriction (Plesk Windows)

    in PhpInfo, i have open_basedir E:/plesk/vhost/xyz.com\;C:\Windows\Temp;\;"E:/plesk/vhost/xyz.com/grav-demo.xyz.com/cache/problem-check-*" but I have no idea, how the php.ini used by Grav
  16. M

    Resolved GravCMS open_basedir restriction (Plesk Windows)

    Hey guys, when i try to install GravCMS on Plesk (windows) but there is allways this error : "GlobIterator::__construct(): open_basedir restriction in effect. File(E:/plesk/vhost/xyz.com/grav-demo.xyz.com/cache/problem-check-*) is not within the allowed path(s)...
Back
Top