Hi, I just set up a new certificate on a server that had no certificates. The process appeared to be a success, only I can’t get to my site at all now.
I can’t ping dev.co-brand2.com, and I can’t ping 52.73.108.54. I can still ssh in to either, though.
SSL Labs can’t find it either. I restarted Apache, and I even rebooted the machine. What’s going on?
Thanks for the reply. I’m not sure which file you want to see, but here’s 000-default-le-ssl.conf:
<IfModule mod_ssl.c>
<VirtualHost *:443>
# The ServerName directive sets the request scheme, hostname and port that
# the server uses to identify itself. This is used when creating
# redirection URLs. In the context of virtual hosts, the ServerName
# specifies what hostname must appear in the request's Host: header to
# match this virtual host. For the default virtual host (this file) this
# value is not decisive as it is used as a last resort host regardless.
# However, you must set it for any further virtual host explicitly.
#ServerName www.example.com
ServerAdmin webmaster@localhost
DocumentRoot /var/www/html
# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the loglevel for particular
# modules, e.g.
#LogLevel info ssl:warn
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
# For most configuration files from conf-available/, which are
# enabled or disabled at a global level, it is possible to
# include a line for only one particular virtual host. For example the
# following line enables the CGI configuration for this host only
# after it has been globally disabled with "a2disconf".
#Include conf-available/serve-cgi-bin.conf
<Directory /var/www/html/redmine>
RailsBaseURI /redmine
PassengerResolveSymlinksInDocumentRoot on
</Directory>
ServerName dev.co-brand2.com
SSLCertificateFile /etc/letsencrypt/live/dev.co-brand2.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/dev.co-brand2.com/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf
</VirtualHost>
</IfModule>
I suggest running ss -ntlp to find out whether Apache is listening on port 443. If so, the problem is a firewall policy forbidding inbound connections on port 443. (This seems like the most likely possibility to me.)
Yes, so that means that you have a firewall blocking it (either a local firewall like a ufw rule, or a network firewall like a hosting provider default policy).
The ping application normally uses ICMP or UDP as protocols. It doesn't use TCP on port 80 (HTTP) or 443 (HTTPS) out of the box (you can specify a such on the command line though). certbot doesn't change firewall settings, nor does it change anything outside your webbrowser (in your case Apache). So the failure of ping doesn't have anything to do with certbot, at least, not by my knowledge.