• 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. K

    Resolved 502 Bad Gateway Web server received an invalid response while acting as a gateway or proxy server.

    I'm affraid I cannot help you because I am not technically proficient enough but I couldn't recommend you more to take the Plesk Paid Support. It is only 10$ monthly, you can cancel it any time and the support is really fast and highly professionnal.
  2. K

    Resolved 502 Bad Gateway Web server received an invalid response while acting as a gateway or proxy server.

    Here is the solution for this case : ################################# The issue is caused by the PaX incompatibility with PHP 7.x branch: PAX PHP errors. Previously, this issue was not triggered, because Plesk Onyx 17.5 comes with sw-engine based on PHP 5.x: # plesk php -v | head -n1 PHP...
  3. K

    Resolved 502 Bad Gateway Web server received an invalid response while acting as a gateway or proxy server.

    Thank you for your advice. I have the exact same error as you but since websites are running on the nginx, if I disable it - it is all doom. In my case every website is working well except the majestically inaccessible Plesk Panel.
  4. K

    Resolved 502 Bad Gateway Web server received an invalid response while acting as a gateway or proxy server.

    Thank you for your reply. I agree with you, 502 is a general error and due to various reasons. However, Plesk is a paid service (at least for me) and we use Plesk not to struggle with our server management in command line. And in this case it is however related to Plesk since it is the only...
  5. K

    Resolved 502 Bad Gateway Web server received an invalid response while acting as a gateway or proxy server.

    UPDATE ---------------------- This issue was solved by the Plesk paid support and it was apparently an internal Plesk problem : The issue is caused by the PaX incompatibility with PHP 7.x branch: PAX PHP errors. --------------------------- Hello everyone, Plesk has become better and better...
  6. K

    Issue Nginx 502 Bad gateway on Php 7.2 with SSL

    The error "ERROR: No pool defined. at least one pool section must be specified in config file" was logged when I was indeed not having a single site running on PHP 7.2 It is not relevant to my last message.
  7. K

    Issue Nginx 502 Bad gateway on Php 7.2 with SSL

    Thank you for your reply. Indeed, no site was running since I wasn't able to get it running on PHP 7.2. Switching it back to PHP 7.2 (which creates config files and makes PHP.7.2-FPM running) helps nothing. So, to be sure I a proprer / new website installation : creating brand new subscrption...
  8. K

    Issue Nginx 502 Bad gateway on Php 7.2 with SSL

    Thank you. Here is what I get : # service plesk-php72-fpm restart Redirecting to /bin/systemctl restart plesk-php72-fpm.service Job for plesk-php72-fpm.service failed because the control process exited with error code. See "systemctl status plesk-php72-fpm.service" and "journalctl -xe" for...
  9. K

    Issue Nginx 502 Bad gateway on Php 7.2 with SSL

    Thank you for your reply. Yes, indeed, the plesk-php72-fpm service is not running and there is no way it can be started. I have uninstalled and re-installed the PHP 7.2 with the plesk installer. Nothing changes that. Error message on # service plesk.php72-fpm restart is : Redirecting to...
  10. K

    Issue Nginx 502 Bad gateway on Php 7.2 with SSL

    If I set a web hosting for a domain to PHP 7.2 handled by Nginx with SSL enabled I'm always getting a 502 Bad Gateway when accessing the website. If I switch to lower version of PHP - 7.1 - everything is fine with no single other change. Error log is recv() failed (104: Connection reset by...
  11. K

    Plesk 12.0.18 MU#63

    For people still dealing with the problem, looking at /var/log/messages will tell you exactly where it bugs. I've commented that include line and everything is ok. On my version: rpm -qa | grep proftpd shows : psa-proftpd-xinetd-1.3.6-8.el6.art.x86_64 psa-proftpd-1.3.6-8.el6.art.x86_64
  12. K

    Plesk 12.0.18 MU#63

    Found it - after the plesk update it was written in /etc/proftpd.conf on line 95 : Include /etc/proftpd.d/*.conf which generated fatal error because of the lack of such directory
  13. K

    Plesk 12.0.18 MU#63

    I'm using Plesk 12.0.18 on CentOS 6. After update #63 on 5 of september which installed newer version of Proftpd all websites went inaccessible on FTP. I've neither touched or installed something. Any idea how to get FTP service back ?
Back
Top