Resolved Issues generating config files

[f.irgolitsch]

Hello,

I'm not quite sure what caused it but all my websites hosted in plesk are down at the moment and I can't seem to start nginx or apache. On the started page of plesk I get the message that tells me to try regenerating the config files. This doesn't work however. I get the following error when trying to regenerate the config files:

Error: New configuration files for the Apache web server were not created due to the errors in configuration templates: nginx: [emerg] cannot load certificate "/usr/local/psa/var/certificates/certFDSVirp": PEM_read_bio_X509_AUX() failed (SSL: error:09091064:PEM routines:PEM_read_bio_ex:bad base64 decode) nginx: configuration file /etc/nginx/nginx.conf test failed.

I have found which files are using this certificate and I found 4. 3 are from webmail domains and one is /etc/nginx/plesk.conf.d/server.conf. I have tried looking around for solutions but so far have found nothing. I've tried repairing plesk with both 'plesk repair web' and 'plesk repair installation' and I've also tried following this. So fair nothing worked. The certificate does exist however, so I have no clue why it can't read it.

 

[f.irgolitsch]

Small update, I'm now getting a different error message when trying to regen the config files:

Error: Can not reconfigure web server configurations: Unable to execute httpdmng: [2020-06-01 14:01:30.624] ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/apache_control_adapter' '--restart' '--restart-interval' '0' '--http-port' '7080' '--https-port' '7081'] with exit code [255]
[2020-06-01 14:01:33.211] ERR [panel] Apache config (15910128830.97296600) generation failed: Template_Exception: Can not restart web server: INFO: [Mon Jun 1 14:01:29 CEST 2020]: Service: httpd, Action: start
Trying to start service httpd... failed
Jun 01 14:01:30 Plesk.amwittools.nl systemd[1]: Starting The Apache HTTP Server...
Jun 01 14:01:30 Plesk.amwittools.nl systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Jun 01 14:01:30 Plesk.amwittools.nl systemd[1]: Failed to start The Apache HTTP Server.
Jun 01 14:01:30 Plesk.amwittools.nl systemd[1]: Unit httpd.service entered failed state.
Jun 01 14:01:30 Plesk.amwittools.nl systemd[1]: httpd.service failed.

***** problem report *****
Warning: start service httpd failed

/usr/local/psa/admin/sbin/pleskrc execution failed:
Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.

file: /usr/local/psa/admin/plib/Service/Driver/Web/Server/Apache.php
line: 111
code: 0
sendmail: the server sent an invalid reply
sendmail: could not send mail (account default from /etc/msmtprc)
[2020-06-01 14:01:34.163] ERR [panel] Unable to send mail: Unknown error
[2020-06-01 14:01:34.163] ERR [panel] Administrator notification failed: Unable to send mail: Unknown error
Can not restart web server: INFO: [Mon Jun 1 14:01:29 CEST 2020]: Service: httpd, Action: start
Trying to start service httpd... failed
Jun 01 14:01:30 Plesk.amwittools.nl systemd[1]: Starting The Apache HTTP Server...
Jun 01 14:01:30 Plesk.amwittools.nl systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Jun 01 14:01:30 Plesk.amwittools.nl systemd[1]: Failed to start The Apache HTTP Server.
Jun 01 14:01:30 Plesk.amwittools.nl systemd[1]: Unit httpd.service entered failed state.
Jun 01 14:01:30 Plesk.amwittools.nl systemd[1]: httpd.service failed.

***** problem report *****
Warning: start service httpd failed

/usr/local/psa/admin/sbin/pleskrc execution failed:
Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.

 

[f.irgolitsch]

Managed to fix it finally.

So the certificate that was mentioned in the error (certFDSVirp) was invalid. This was the default certificate of plesk. I changed the default to the let's encrypt cert is was using anyway. This allowed me to regen all the configuration files without error. Afterwards however I still couldn't connect to my websites. I was getting a ssl_protol_error in Edge (chromium). I managed to fix this by running '/usr/local/psa/admin/bin/nginxmng -d' and '/usr/local/psa/admin/bin/nginxmng -e' in that order. Everything seems to be working ok now.