Hi you two,
both of you seem to have problems with investigations in the first place. You don't get even near to your root cause and you choosed the linux beginner solution: "Restore to a previous state". That's o.k. for your current linux knowledge, but I strongly recommend to INVESTIGATE issues, instead of just restoring a server to a previous state.
Especially @
die|webhosterin , who has the time to write a ( from my point of view ) nonsense blog - post, which is not at all based on facts, my advise is: Please try to learn some linux basics, before you think that you are able to help people with issues by writing blog - posts, which only reflects a very amateur handling of linux and Plesk.
@TimoViBritannia :
If you would like to get to your root cause of your issue, you have to
READ the possible error message(s):
Apache config (14765156730.57244100) generation failed: Template_Exception: Can not restart web server:
You would now start to restart the used webserver(s) ( apache+nginx ), or/and see possible misconfigurations with the commands:
apachectl -t ( or: apachectl configtest )
nginx -t
Both commands are used to check the configuration - files and will display possible errors. Afterwards, you would investigate the possible error(s), so that you are able to correct possible misconfigurations, which block the start of your used webserver(s).
In addition, it would really help, if you have a look at your log - files ( from your webserver(s) ), to see and investigate, WHY the webserver(s) didn't start and due to the fact that both of you don't provide informations about their used operating system, and other usefull informations ( apache version, nginx version, ... ), we now have to wait for more informations, in order to make suggestions how to solve your issue(s).
die|webhosterin tries to answer a "
Can not restart web server", with the used PHP - version and SSL - usage. The statement
PLESK has put PHP on mod_php for all customers using PHP 5.5.9
is absolutely wrong, because there is no such command used by Plesk, when you upgraded from an earlier Plesk version.
The recommendation
Here, I recommend to temporarily disable SSL for each individual customer
might solve possible issues in your configuration files, with wrong paths for the domain specific certificates. But again, you don't investigate the root cause here. If you experience wrong path - issue(s), you really have to investigate, if Plesk database consistencies exists, or if the recreation based on templates causes the issue(s).
In some vhost entries even an IPv6 address is entered, even though it has not been assigned.
Once you disable roundcube, the host entries will normalize again.
I strongly recommend that you do not install the Onyx Update.
Roundcube configuration files can be easily removed manually from apache2 and nginx configuration folders, there is absolutely no need to "disable" the webmail - software, if you experience issue(s)/problem(s) in their configuration files, because these files are created based on templates, which get their informations from your Plesk database. If the process to recreate new webmail - configuration files result again in misconfigured webmail - configuration files, you really should investigate the root cause here, instead of stating "I strongly recommend that you do not install the Onyx Update", because again, this reflects only, that you don't have any clue about your root cause. It's pretty much the same as stating "Please do not use your newly purchased car because the new car has no ignition lock and instead has a start button to start the engine."
Back to the threadstarter and his issue:
If you would like further help with your issue, pls. consider to provide more informations and don't forget, that since Plesk 12.5, there is as well a wonderfull "
Plesk repair utility", which you could use.
Facebook
Twitter
