• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Search results

  1. M

    Issue update error 18.0.47 #5 to 18.0.48

    a workaround # rpm -ivh --nodeps php-process-5.4.16-48.el7.x86_64.rpm then upgrade works. only one Warning -- Warning: RPMDB altered outside of yum. ** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows: php-process-5.4.16-48.el7.x86_64 has missing requires of php-common(x86-64)...
  2. M

    Issue update error 18.0.47 #5 to 18.0.48

    @sebgonzes that's not the solution. It is surprising that another server that has php5.6 as OS-PHP upgraded without any problems. i haven't figured out why yet. If you remove the OS-PHP via the plesk installer and reinstall it (php5.4), the upgrade also works.
  3. M

    Issue update error 18.0.47 #5 to 18.0.48

    few years ago the OS PHP version was upgraded from php5.4 to php5.6. the remi repro has also been deactivated since then. you mean I should remove the OS-PHP completely? Plesk PHP versions 5.4 and 5.6 are still required on the server. I don't understand why there is suddenly a problem. over...
  4. M

    Issue update error 18.0.47 #5 to 18.0.48

    >requires php-common(x86-64) = 5.4.16-48.el7 this is already installed #yum install php-common #Package matching php-common-5.4.16-48.el7.x86_64 already installed. but #yum install php-process #Error: Package: php-process-5.4.16-48.el7.x86_64 (base) #Requires: php-common(x86-64) =...
  5. M

    Issue update error 18.0.47 #5 to 18.0.48

    Plesk 18.0.47 #5 CentOS 7.9 when updating from 18.0.47 Update #5 to 18.0.48 i get the following error Exception: Failed to solve dependencies: php-process-5.4.16-48.el7.x86_64 requires php-common(x86-64) = 5.4.16-48.el7 Does anyone know where exactly the problem is and how I can solve it?
  6. M

    Forwarded to devs Plesk 18.0.46 Update #1 - Joomla! Toolkit no access

    that didn't work yesterday. This morning it suddenly works again without an update. at least I can't find any reference to an update.
  7. M

    Forwarded to devs Plesk 18.0.46 Update #1 - Joomla! Toolkit no access

    Many Thanks should there be a workaround before the patch, please let me know
  8. M

    Forwarded to devs Plesk 18.0.46 Update #1 - Joomla! Toolkit no access

    logged in as admin it works normally. you have to be logged into plesk as a reseller and then open the toolkit excerpt from the log 23: /usr/local/psa/admin/htdocs/modules/joomla-toolkit/index.php:4 [2022-09-07 07:56:12.741] 22000:63183279949ae ERR [panel] Call to a member function...
  9. M

    Forwarded to devs Plesk 18.0.46 Update #1 - Joomla! Toolkit no access

    Username: TITLE Plesk 18.0.46 Update #1 - Joomla! Toolkit no access PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE CentOS Linux 7.9 Obsidian 18.0.46 Update #1 Joomla! Toolkit 2.5.1-328 PROBLEM DESCRIPTION As a reseller you no longer have access to the Joomla Toolkit. The error...
  10. M

    Forwarded to devs Rotation of files with multiple hard links is not allowed

    on some servers the "allowhardlink" line was added to /usr/local/psa/etc/logrotate.conf.rpmnew !! but not to logrotate.conf
  11. M

    Forwarded to devs Changing the host's default certificate does not update cert file references in the web server config files that are using the host cert

    I can confirm. that was already the case 2 years ago when the certificate was changed. Now that the certificates are only valid for 1 year, this problem comes up every year. a certificate is often displayed as used even though ssl is deactivated for the user. but since the certificate was...
  12. M

    Issue Unable to install or update Plesk components: There are no products for your operating system | Update operation was locked by another update process

    Try this https://support.plesk.com/hc/en-us/articles/213917525-Unable-to-open-the-Updates-and-Upgrades-page-or-start-Plesk-Installer-in-CLI-Update-operation-was-locked-by-another-update-process
  13. M

    Question Centos8 migration

    please read the thread above. it was all discussed there
  14. M

    Question Centos8 migration

    only a few minutes. we switched about 30 servers within 2-3 hours https://talk.plesk.com/threads/conversion-of-centos-8-server-with-plesk-to-almalinux.361493/#post-902348
  15. M

    Question Centos8 migration

    you can easily switch from centos 8 to almalinux See: https://support.plesk.com/hc/en-us/articles/360018916859-Does-Plesk-support-AlmaLinux-as-an-alternative-to-CentOS-8- https://talk.plesk.com/threads/conversion-of-centos-8-server-with-plesk-to-almalinux.361493/
  16. M

    Question Conversion of Centos 8 server with Plesk to Almalinux ?

    that was a few weeks ago and I don't know exactly anymore. but it was always only a few minutes.
  17. M

    Resolved [PPPM-13304] Update failed Almalinux 8.4 -> 8.5

    as I have already described above
  18. M

    Resolved [PPPM-13304] Update failed Almalinux 8.4 -> 8.5

    what is the output when you run "yum update" manually? During the manual update I had an error regarding "nothing provides jasper-devel needed by ImageMagick-devel-6.9.10.86-1.el8.x86_64" but after activating powertools "yum config-manager --set-enabled powertools" the problem was also eliminated.
  19. M

    Question Conversion of Centos 8 server with Plesk to Almalinux ?

    Hi, there is no difference in operation between centos 8 + Plesk and Almalinux + Plesk as described here: https://support.plesk.com/hc/en-us/articles/360018916859-Does-Plesk-support-AlmaLinux-as-an-alternative-to-CentOS-8- ultimately only: https://github.com/AlmaLinux/almalinux-deploy for me...
  20. M

    Forwarded to devs migrator does not migrate outgoing email settings in the service plan

    We are currently migrating several servers and the server-wide settings for outgoing emails per hour now apply to all service plans and customers. It is also not possible to adjust the service plan at a later date because the subscriptions are not synced in this regard. is there a short-term...
Back
Top