• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

502 Gateway error. Plesk Onyx 17.8.11

n317

New Pleskian
I'm running Plesk Onyx 17.8.11 Update #24 on Ubuntu 16.04.5 LTS‬ and I'm currently getting a 502 gateway error when trying to access my website, I think the below error has something to do with it. The Apache.php file does appear to be corrupted as it is full of random characters.

Details: [2018-10-02 11:18:50.311] ERR [util_exec] proc_close() failed ['/opt/psa/admin/bin/apache_control_adapter' '--restart' '--restart-interval' '0' '--http-port' '7080' '--https-port' '7081'] with exit code [255]
[2018-10-02 11:18:50.944] ERR [panel] Apache config (15384789850.57971700) generation failed: Template_Exception: Can not restart web server:
file: /opt/psa/admin/plib/Service/Driver/Web/Server/Apache.php
line: 109
code: 0
Can not restart web server:

Is there a way I could get a copy of the Apache.php from somewhere?
 
Thanks for taking the time to look. Unfortunately that KB did not help. In the end I had to spin down the server and start a new instance. It was mission critical.
 
Have you checked the Apache error log file? It normally mentions the exact reason why Apache does not want to start.
 
You should stop the NGINX via Panel. This will re-write the configuration files Apache as the Web Server.

Stop the NGINX via Plesk Panel | Tools & Settings > Service Management.

Then try to restart Apache,

#service apache2 restart

Then check the error log,

# vi /var/log/apache2/error.log

Error log will explain why the Apache is refusing to restart. Then you can troubleshoot from there.

Also you can try to restart the Apache via Panel too. This might also show you the template with errors.

The Apache.php file does appear to be corrupted as it is full of random characters.

Some of the Plesk files are encrypted. Nothing unusual about this file contain "full of random characters"
 
Last edited:
Back
Top