• 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 DevFB

  1. D

    Resolved 502 Bad Gateway nginx after auto update Version 17.5.3 Update #54

    OK, this post helped me: Resolved - Fail2Ban Causes 502 Bad Gateway Turns out after the update, fail2ban > Trusted IP Addresses had lost my servers IP address. I have added this and all seems to be well again.
  2. D

    Resolved 502 Bad Gateway nginx after auto update Version 17.5.3 Update #54

    OK, that threw a spanner in the works. This morning (some 17 hours later) the 502 Bad Gateway nginx appeared in the browser once again when viewing any website on my DV. (all other services like mail / mySQL is fine still). So in plesk, I disabled the firewall and the sites are back again -...
  3. D

    Resolved 502 Bad Gateway nginx after auto update Version 17.5.3 Update #54

    Problem sovled! After the Plesk Onyx Version 17.5.3 Update #54 after trying numerous restarts and reboots... I turned off the firewall. And all sites instantly came back up. So I thought maybe an OLD rule was effected by the plesk update (strange). So I thought I would turn the firewall back...
  4. D

    Resolved 502 Bad Gateway nginx after auto update Version 17.5.3 Update #54

    Hi, All websites on my DV are displaying: 502 Bad Gateway nginx On logging into plesk I can see a few hours prior the plesk automaticaly updated. Plesk Onyx Version 17.5.3 Update #54, last updated on July 24, 2018 09:28 PM I have restarted services and rebooted the server via the plesk panel...
See more
Back
Top