Can't rollback because certbot can't find the certificates

by which you mean emptied? or deleted? or does it matter.

1 Like

Deleted. It's useless. Did you move the le version of 000-default back to sites-available (to back it up)?

The only things that should currently be in sites-enabled are:

Don't forget to run these:

sudo a2dissite 000-default.conf
sudo apachectl -k graceful
1 Like


and look at that:

(that is definitely on the right server)

THANK YOU, @griffin


Which conf file is that in?

I think you might have gotten ahead of me, which is fine.


1 Like

You seem to be of a higher knowledge/experience level compared with many we see here.

1 Like

-rw-r--r-- 1 root root 627 Aug 26 00:46, if that's what you mean. These things are incredible; they just use plugins to trawl rss feeds and populate themselves with content daily. I guess he runs ads on them, or that's the plan? They get a fair amount of traffic for things built with bots.

1 Like

You seem to have things in hand now. :slightly_smiling_face:

Just manage the individual port 80 vHost files and let certbot create your port 443 vHost files. Don't be afraid to delete certbot's created files and just have it regenerate them as needed.

1 Like

well I have been staring at these webroots for like a couple weeks now, so I'm kinda familiar with them. And now with the limits of multiple vhosts (my original plan had been one big honking server)

1 Like

I think you've got a smooth setup going now. With each site having its own two vHost files and individual certificate lineage in certbot, your world should be simple.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.