Cannot get initial cert to work

daneseelen · November 18, 2019, 7:07pm

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:
seelen.us

I ran this command:
sudo certbot --apache -m myname@gmail.com -d seelen.us -d www.seelen.us

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for seelen.us
http-01 challenge for www.seelen.us
Waiting for verification…
Cleaning up challenges
Running post-hook command: service apache2 reload
Failed authorization procedure. seelen.us (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://seelen.us/.well-known/acme-challenge/oGGPaS13hjVofNinsKUrRoznxcD90-4z3JcgUfMDuHY: Timeout during connect (likely firewall problem), www.seelen.us (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://www.seelen.us/.well-known/acme-challenge/Ai8plrmJd4SQ9GqbK3W05WFMDMJ8pT4Nq3pzoMTovv0: Timeout during connect (likely firewall problem)

IMPORTANT NOTES:

The following errors were reported by the server:

Domain: seelen.us
Type: connection
Detail: Fetching
http://seelen.us/.well-known/acme-challenge/oGGPaS13hjVofNinsKUrRoznxcD90-4z3JcgUfMDuHY:
Timeout during connect (likely firewall problem)

Domain: www.seelen.us
Type: connection
Detail: Fetching
http://www.seelen.us/.well-known/acme-challenge/Ai8plrmJd4SQ9GqbK3W05WFMDMJ8pT4Nq3pzoMTovv0:
Timeout during connect (likely firewall problem)

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.

My web server is (include version):
Server version: Apache/2.4.34 (Ubuntu)

The operating system my web server runs on is (include version):
Distributor ID: Ubuntu
Description: Ubuntu 18.10
Release: 18.10
Codename: cosmic

My hosting provider, if applicable, is:
Databasemart

I can login to a root shell on my machine (yes or no, or I don’t know):
yes

I’m using a control panel to manage my site (no, or provide the name and version of the control panel):
no

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):
certbot 0.27.0

rg305 · November 18, 2019, 8:02pm

That could use some updating - but probably irrelevant to this problem.

What does this say?:
apachectl -S

rg305 · November 18, 2019, 8:05pm

Confirmed access problem:

curl -Iki seelen.us
curl: (7) Failed to connect to seelen.us port 80: Connection refused
curl -Iki www.seelen.us
curl: (7) Failed to connect to www.seelen.us port 80: Connection refused
curl -Iki https://seelen.us/
curl: (7) Failed to connect to seelen.us port 443: Connection refused
curl -Iki https://www.seelen.us/
curl: (7) Failed to connect to www.seelen.us port 443: Connection refused

daneseelen · November 18, 2019, 8:18pm

I think you caught me on a reboot, you should be able to connect via http or https now. Sorry was trying something.

rg305 · November 18, 2019, 8:30pm

Ok.

daneseelen · November 18, 2019, 8:31pm

VirtualHost configuration:
*:80 is a NameVirtualHost
default server mta1.resource-team.com.ng (/etc/apache2/sites-enabled/000-default.conf:1)
port 80 namevhost mta1.resource-team.com.ng (/etc/apache2/sites-enabled/000-default.conf:1)
port 80 namevhost mta1.resource-team.com.ng (/etc/apache2/sites-enabled/owncloud.conf:1)
*:443 127.0.0.1 (/etc/apache2/sites-enabled/owncloud.conf:7)
ServerRoot: “/etc/apache2”
Main DocumentRoot: “/var/www/html”
Main ErrorLog: “/var/log/apache2/error.log”
Mutex watchdog-callback: using_defaults
Mutex rewrite-map: using_defaults
Mutex ssl-stapling-refresh: using_defaults
Mutex ssl-stapling: using_defaults
Mutex ssl-cache: using_defaults
Mutex default: dir="/var/run/apache2/" mechanism=default
Mutex mpm-accept: using_defaults
PidFile: “/var/run/apache2/apache2.pid”
Define: DUMP_VHOSTS
Define: DUMP_RUN_CFG
User: name=“www-data” id=33
Group: name=“www-data” id=33

rg305 · November 18, 2019, 8:33pm

There is no vhost config for: seelen.us, www.seelen.us
Start there.

daneseelen · November 18, 2019, 8:59pm

Thanks for the help!

I think I got this right-

root@seelen:/etc/apache2/sites-available# apachectl -S
VirtualHost configuration:
*:80 seelen.us (/etc/apache2/sites-enabled/seelen.us.conf:1)
*:443 seelen.us (/etc/apache2/sites-enabled/seelen.us.conf:34)
ServerRoot: “/etc/apache2”
Main DocumentRoot: “/var/www/html”
Main ErrorLog: “/var/log/apache2/error.log”
Mutex watchdog-callback: using_defaults
Mutex rewrite-map: using_defaults
Mutex ssl-stapling-refresh: using_defaults
Mutex ssl-stapling: using_defaults
Mutex ssl-cache: using_defaults
Mutex default: dir="/var/run/apache2/" mechanism=default
Mutex mpm-accept: using_defaults
PidFile: “/var/run/apache2/apache2.pid”
Define: DUMP_VHOSTS
Define: DUMP_RUN_CFG
User: name=“www-data” id=33
Group: name=“www-data” id=33

rg305 · November 18, 2019, 9:04pm

http://seelen.us /etc/apache2/sites-enabled/owncloud.conf:1
http://www.seelen.us /etc/apache2/sites-enabled/owncloud.conf:19
conflicts with:
http://seelen.us /etc/apache2/sites-enabled/seelen.us.conf:1 [alias http://www.seelen.us]

Did you get that corrected?

daneseelen · November 18, 2019, 9:06pm

Your Right, hows this, allow it still will not work lol.
root@seelen:/etc/apache2/sites-available# apachectl -S
VirtualHost configuration:
*:80 seelen.us (/etc/apache2/sites-enabled/seelen.us.conf:1)
*:443 seelen.us (/etc/apache2/sites-enabled/seelen.us.conf:34)
ServerRoot: “/etc/apache2”
Main DocumentRoot: “/var/www/html”
Main ErrorLog: “/var/log/apache2/error.log”
Mutex ssl-cache: using_defaults
Mutex default: dir="/var/run/apache2/" mechanism=default
Mutex mpm-accept: using_defaults
Mutex watchdog-callback: using_defaults
Mutex rewrite-map: using_defaults
Mutex ssl-stapling-refresh: using_defaults
Mutex ssl-stapling: using_defaults
PidFile: “/var/run/apache2/apache2.pid”
Define: DUMP_VHOSTS
Define: DUMP_RUN_CFG
User: name=“www-data” id=33
Group: name=“www-data” id=33

rg305 · November 18, 2019, 9:07pm

OK, retry:

daneseelen · November 18, 2019, 9:09pm

Oh son of a &*(&

I guess I gotta wait-

An unexpected error occurred:
There were too many requests of a given type :: Error creating new order :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/
Please see the logfiles in /var/log/letsencrypt for more details.

rg305 · November 18, 2019, 9:11pm

OK , try:
sudo certbot --apache -m myname@gmail.com -d seelen.us -d www.seelen.us --dry-run

daneseelen · November 18, 2019, 9:14pm

–dry-run currently only works with the ‘certonly’ or ‘renew’ subcommands (‘run’)

rg305 · November 18, 2019, 9:16pm

How about:
sudo certbot --apache -m myname@gmail.com -d seelen.us -d www.seelen.us --staging

daneseelen · November 18, 2019, 9:18pm

certbot certonly --apache -m myname@gmail.com -d seelen.us -d www.seelen.us --dry-run

This is running now, but it is hanging I will wait a minute or two to see what happens

rg305 · November 18, 2019, 9:19pm

Slow is much better than ERROR: YOU FAILED - LOL

rg305 · November 18, 2019, 9:29pm

Any news?
It’s NOT still running! Is it?
[that would be bad and weird… beird]

daneseelen · November 18, 2019, 10:11pm

No I got pulled away, prob will in a bit, it just stayed hung up. What is really weird is when I run certbot now, I have to reboot apache in order to get the webpage to work again.

daneseelen · November 18, 2019, 10:13pm

scratch that, I may need to adjust the owncloud conf or php files now is all.