Link to home
Start Free TrialLog in
Avatar of jnsimex
jnsimex

asked on

Apache not starting

Before I post my question, please be aware that I am not very familiar with this stuff so please be gentle with me!

I have my store website hosted on Debian OS 8.11 with Plesk Onyx 17.8.11. I got a warning from Jetpack this morning that my website was down so I tried to load it and got a 502 bad gateway error.

When I logged into Plesk, I see this message:

"New configuration files for the Apache web server were not created due to the errors in configuration templates: Can not restart web server: . Detailed error descriptions were sent to you by email. Please resolve the issues and click here to generate broken configuration files once again or here to generate all configuration files. See the details in Configuration Troubleshooter"

I try generating new configuration files but no success. I then get this email in my inbox.

Template_Exception: Can not restart web server:
file: /opt/psa/admin/plib/Service/Driver/Web/Server/Apache.php
line: 109
code: 0

I am not sure what to do next..Please help!

Thanks in advance.
ASKER CERTIFIED SOLUTION
Avatar of Martyn Spencer
Martyn Spencer
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Reading this...

"Before I post my question, please be aware that I am not very familiar with this stuff so please be gentle with me!"

"got a warning from Jetpack this morning that my website was down"

First consideration is importance of your Website.

If you pay your bills from your Website income, then likely best you hire someone very smart about WordPress sites (since you mentioned JetPack) to host your WordPress site.

One of the reasons I avoid all Panel systems like the plague is your exact situation.

You can make changes at the Panel level which crash your site(s) with no way to even understand the problem.

As Martyn suggested, only your hosting company (someone with root ssh access) can likely diagnose this problem + then help you fix this at the Plesk level.

If you get stuck, you can reach out to many EE folks for assistance.

Hint: This problem can't really be fixed via an EE question. This will require you or someone else interacting with your hosting company to fix the problem.
In my experience, some panel based systems are run by people who do not really know what they are doing. I say this based on reading forum comments from people hosting such services. I am not suggesting that this is the case with your provider. Those that do sometimes encounter this type of issue, and it does happen, hold their hands up and fix it for their clients. If you changed nothing and your site is now failing, it falls right at the feet of your hosting provider. Don't let them persuade you otherwise :)
Avatar of jnsimex
jnsimex

ASKER

Thank you Martyn and David for your replies.

I have opened a ticket with the hosting provider and then will engage Plesk support for guidance.