Server damage after runningle "letsencrypt"

[MicrosiM]

To make it short,

I ran the scripts for the Apache Centos 6, and I got the a broken server, the httpd service failed to start.

I have the copied the below from the screen, were the error was shown.

I dont understand how come you ask people to run scripts on there servers, without any backup plans?

I had to restore my server from an image.

Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter ‘c’ to cancel): 7
Obtaining a new certificate
Performing the following challenges:
tls-sni-01 challenge for www.diysmps.com
Waiting for verification…
Cleaning up challenges
Error while running apachectl graceful.
httpd not running, trying to start

Warning: DocumentRoot [/var/www/vhosts/==s.net] does not exist
Warning: DocumentRoot [/var/www/vhosts/==s.com] does not exist
httpd: Could not reliably determine the server’s fully qualified domain name, using 2001:4801:7818:6:4d87:8ba:ff10:8fdf for ServerName

Error while running apachectl graceful.
httpd not running, trying to start

Warning: DocumentRoot [/var/www/vhosts/a==.net] does not exist
Warning: DocumentRoot [/var/www/vhosts/s==.com] does not exist
httpd: Could not reliably determine the server’s fully qualified domain name, using 2001:4801:7818:6:4d87:8ba:ff10:8fdf for ServerName

IMPORTANT NOTES:

• The following errors were reported by the server:

  Domain: www.diysmps.com
  Type: connection
  Detail: Error getting validation data

  To fix these errors, please make sure that your domain name was
  entered correctly and the DNS A/AAAA record(s) for that domain
  contain(s) the right IP address. Additionally, please check that
  your computer has a publicly routable IP address and that no
  firewalls are preventing the server from communicating with the
  client. If you’re using the webroot plugin, you should also verify
  that you are serving files from the webroot path you provided.

• Your account credentials have been saved in your Certbot
  configuration directory at /etc/letsencrypt. You should make a
  secure backup of this folder now. This configuration directory will
  also contain certificates and private keys obtained by Certbot so
  making regular backups of this folder is ideal.

[schoen]

Hi @MicrosiM,

I’m sorry about the problems that Certbot caused to your server. Were you following a particular tutorial or guide? What version of Certbot do you have?

I guess you don’t have a copy of the Apache configuration after Certbot modified it? That would be useful for understanding what went wrong here.

Certbot has a command called “rollback” that’s meant to be used when a change that it makes to your web server configuration is inappropriate or undesired. It does make its own backups of the files that it’s changing, and the “rollback” command can restore those backups. While this isn’t 100% guaranteed to work around every failure mode, it might have been able to fix your configuration problem.