Issue Redo a lets encrypt cert on a domain- wont allow me to remove and redo

[Will TCSI]

Hi I wanted to redo a lets encrypt cert, and tried to delete the install and start again, but plesk isnt allowing me to do so, anyone have any ideas how to do so? Please see attached pic... I tick the box to remove but it wont then let me do so...
ta muchly

 

[Bitpalast]

Steps to remove a certificate:
1) Certificates that are currently in use cannot be removed. Change "Hosting settings" of the website to a different certificate, e.g. the host certificate.
2) Extensions > Let's Encrypt > Click on second column link "Let's Encrypt DOMAIN.TLD"
3) Check selector checkbox
4) Click "Remove" iconbar button

 

[Will TCSI]

Hi Peter.
thanks for your response... however that is the problem I am experiencing... What you describe is what i would expect procedure would follow...
however as per earlier attached pic... when i try tick choose domain to remove it it doesnt give me the live option.. when i chose " remiove" it keeps saying " make a selection"... biut i have already tocked the upper box to include any in the list below.. but list below does not reflect that tick....

 

[Bitpalast]

I cannot confirm that and have tested the procedure on a test machine. Your screenshot is not showing that effect either.

Please follow exact steps listed above. Make sure that the certificate is not being used by your domain. It must not be selected in the SSL settings.
Further, you are in "Domain", but steps are "Extensions > Let's Encrypt > ..." from where you can remove it.

 

[Will TCSI]

Hi Peter ,, thansk for input..

have definately unticked "use ssl" in domain.. have also 100% accessed the cert via extension link...
still same problem....

 

[Will TCSI]

was wondering if i manually edited the vhosts conf to remove cert references may work or make things worse?

 

[Bitpalast]

Manual editing is discouraged. Deselect the certificate from the selector box in the SSL configuration. Turning off SSL may not do the job. The certificate must not be selected from the drop down box of certificates to choose from. As long as it is selected as the domain's certificate, it is considered active, because it is still set in the database, even if SSL is turned off.

 

[Will TCSI]

Hi peter..
thanks for the info... have now followed your hints to deselect cert as you instructed... I think have made progress !!! ... Unfortunately when i run /usr/sbin/apachectl -t now to check everything i suddenly get Warning: DocumentRoot [/var/www/vhosts/localchimes.com.au/httpdocs] does not exist !! which is a domain that i used to host and deleted 6 months ago..... have no idea why it is suddenly popping up in log errors.. happy to delete in a conf somewhere but as plesk is so embedded thought i might ask where to start....? alll ears for any helpful tips... bloody server.. fix one fault and another pops up.. lol

 

[Bitpalast]

Your server seems to think that localchimes.com.au is still available. This is probably due to a wrong database entry on that or due to files having been edited or deleted manually instead of reconfiguring the web server through Plesk.

1) # plesk repair db -y
to fix database inconsistencies.

2) # plesk repair web -y
to re-create all webserver configuration files according to the latest database entries

There is a small risk in executing these commands. It could in some cases result in a web server that won't start. In that case, check
# service httpd status
output and follow the instructions where to look into log files for further information. You will find the cause for errors in there.

 

[Will TCSI]

Hi thanks for help...
have run those commands
All came up as saying ok except for one line
Checking for extra configurations in database not owned by any object

There are some unnecessary configurations in the database. Please
check http://kb.odin.com/116412 for solution ...................... [WARNING]

following that up the advice was
Resolution

• Plesk Panel 11.x - 12.5: In the Webserver Configuration Troubleshooter extension , filter out all erroneous configurations with the help of the "Show Errors" button and remove them using the "Remove" button. Then click the "Rebuild All" button to rebuild the configurations.

However when I run the troubleshooter it says that are no errors !!
Once again stumped..

 

[Bitpalast]

The remaining warning can be ignored. It is saying that there is additional information in the database that can be removed. That additional information does not harm operations.

When you run
# apachectl -t
now, does it still show the document root warning for the domain you had deleted?

 

[Will TCSI]

Ah woops.,.. knew i forgot to add info...
Yes error still shows...
[root@vps0 /]# /usr/sbin/apachectl -t
Warning: DocumentRoot [/var/www/vhosts/localchimes.com.au/httpdocs] does not exist
Syntax OK

have solved the lets encrypt issue tho

 

[Bitpalast]

It seems that you had previously manually edited directories that descend from /var/www/vhosts/system. If you are perfectly sure that the domain localchimes.com.au does not show up in Plesk any longer (check with Domains menu), then
1) Backup /var/www/vhosts/system/localchimes.com.au just in case you need to restore the path later.
2) Remove /var/www/vhosts/system/localchimes.com.au
3) # apachectl -t

If an httpd.conf file is found in the /system path, it will be included in the Apache configuration. Files in these directories can exist, even if Plesk has not generated them.

 

[Will TCSI]

Ok have done that...

Have also found other localchimes files and confs still hanging around.. Manually remove also? listed them all further below

[root@vps0 ~]# /usr/sbin/apachectl -t
httpd: Syntax error on line 221 of /etc/httpd/conf/httpd.conf: Syntax error on line 9 of /etc/httpd/conf.d/zz010_psa_httpd.conf: Could not open configuration file /etc/httpd/conf/plesk.conf.d/vhosts/localchimes.com.au.conf: No such file or directory
[root@vps0 ~]#

/etc/httpd/conf/plesk.conf.d/vhosts/localchimes.com.au.conf
/etc/httpd/conf/plesk.conf.d/webmails/horde/localchimes.com.au_webmail.conf
/etc/nginx/plesk.conf.d/vhosts/localchimes.com.au.conf
/var/spool/cron/localchimes
/var/spool/mail/localchimes

 

[Bitpalast]

I am afraid that you will have to apply more common sense to it. I would like to, but due to lack of resources I cannot possibly accompany every single step. You have a conf file set that you are saying should not be there, because the domain was removed from Plesk DB. If it has been removed and is not showing Plesk panel, if database repair has been done with no errors remaining, then the domain cannot be there. Something is missing from the description of this case, because this situation is inconclusive.

Your latest error shows that in /etc/httpd/conf.d/zz010_psa_httpd.conf there is a reference to the removed file. However, if Plesk DB does not contain any references to it and httpdmng -reconfigure-all was run, this should not be the case. So one of the information pieces given previously must be false. Are you sure that the domain does not exist in the panel? Where did you look for it in the panel?

I'd restore the .conf files from the backup recommended in (1), to heal the situation that is now worse than before. Then try to reconfigure all domains and see if the references to the localchimes.com.au.conf are still present. If the error, that a configuration for the domain is present, but the according web space directories are missing and the domain is missing from panel display persist, you must investigate the issue in the Plesk database tables. In that case one will need to search for datasets refering to that domain name and checking why construction is leading to this situation.

 

[Will TCSI]

Totally understand ! you have spent a lot of time already and given a lot of free advice, but as you have seen this is obviously well outside my skill level.. Is there somewhere I could reasonably affordably hire an plesk expert such as yourself to look into fixing the issue perhaps?

 

[Bitpalast]

I suggest to contact official Plesk support on the issue and open a ticket with them. They are trained experts and will surely find what's wrong if this is a database issue or other configuration problem.