• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Recent content by briceld

  1. B

    Issue 502 Bad Gateway after Plesk upgrade

    Moving my data to another server will require several days of installation and then cause a service interruption of several hours. I consider this only as the last option. It should be possible to update libstdc++.so.6, but on the Centos forum it is recommended that the solution comes rather...
  2. B

    Issue 502 Bad Gateway after Plesk upgrade

    OS: CentOS Linux release 7.6.1810 (Core) Plesk installed: Plesk Onyx 17.5.3 Update #91 Plesk upgrading to: Plesk 18.0.21 No warning before the upgrade. I still have access to my server via SSH but my host provider is not able to deliver a new server right now. How can I backup my full...
  3. B

    Issue 502 Bad Gateway after Plesk upgrade

    Thanks for your answer, For half a year I have tried to solve the problem by myself without success, then I finally started managing my websites using linux commands. But now it is no more possible because I need to: 1. make advanced update on my websites and create new ones, 2. upgrade plesk...
  4. B

    Issue 502 Bad Gateway after Plesk upgrade

    Hi, I am still not able to access Plesk to manage my websites, please see below even repair installation fails. How can I fix that or reinstall plesk without losing my website configurations? I have tried plesk installer --select-release-current --reinstall-patch...
  5. B

    Issue 502 Bad Gateway after Plesk upgrade

    Hi, I have tried to update my plesk server to the Obsidian version, but the installation failed. Now I can't access plesk anymore. If I try to restart the service via ssh, I get an error: ---- [root@master ~]# service sw-engine start Starting sw-engine (via systemctl): Job for...
Back
Top