Restarted Server, Now Everything is Broken (Certbot apache on Linux Mint 19.1)

I’ve been using certbot for almost a year to add SSL security to a couple web pages I’m hosting off my own machine. I have a few domains which primarily point to another webserver, but I have subdomain redirects that point to my ip to access resources I’m hosting on my own.

This has been working great and I’ve been using certbot with the apache installer using the cloudflare dns validator. This seems to be the only working combination for me.

Here’s the problem. I just restarted the linux machine and noticed that the apache service wasn’t running. Also, no matter what I do, I can’t get it started without error. And it’s at a point where I don’t know what’s wrong.

I get this error when trying to run ‘sudo service apache2 start’

Job for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xe" for details.

May 01 00:08:20 Icebox apachectl[12417]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1
May 01 00:08:20 Icebox apachectl[12417]: (98)Address already in use: AH00072: make_sock: could not     bind to address [::]:80
May 01 00:08:20 Icebox apachectl[12417]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
May 01 00:08:20 Icebox apachectl[12417]: no listening sockets available, shutting down
May 01 00:08:20 Icebox apachectl[12417]: AH00015: Unable to open logs
May 01 00:08:20 Icebox apachectl[12417]: Action 'start' failed.
May 01 00:08:20 Icebox apachectl[12417]: The Apache error log may have more information.
May 01 00:08:20 Icebox systemd[1]: apache2.service: Control process exited, code=exited status=1
May 01 00:08:20 Icebox systemd[1]: apache2.service: Failed with result 'exit-code'.
May 01 00:08:20 Icebox systemd[1]: Failed to start The Apache HTTP Server.

And when I try to run certbot it returns a similar error.

In the apache error log it reports this:

[Tue Apr 30 23:33:27.380864 2019] [ssl:emerg] [pid 2409] AH02572: Failed to configure at least one certificate and key for cloud.chillstice.com:443
[Tue Apr 30 23:33:27.380895 2019] [ssl:emerg] [pid 2409] SSL Library Error: error:140A80B1:SSL routines:SSL_CTX_check_private_key:no certificate assigned
[Tue Apr 30 23:33:27.380898 2019] [ssl:emerg] [pid 2409] AH02312: Fatal error initialising mod_ssl, exiting.
AH00016: Configuration Failed

I tried updating one of the ssl certs using certbot with the apache installer and the cloudflare dns validator and it worked properly, but it didn’t make any difference.

I realllllly need some help with this. If you need any more information from me, don’t hesitate to ask.

I think I might be on to something. I think httpd is binding to port 80 and preventing apache from doing the same. When I try to stop httpd, it says it’s not running. However, it still says that httpd is listening on port 80???

Also, I really with Timeshift would actually open. It prompts me for my passowrd, but the process dies after I enter the correct password. I want to roll-back to a stable config. Is there a command to verify the integrity of linux?

Hi @Chillstice

what's your domain name? Checking your domain name with external tools helps to see the answers.

The standard template from #help


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. crt.sh | 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:

I ran this command:

It produced this output:

My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

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

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

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

Sorry, I didn’t realize there was a standard help template.

My domain is: cloud.chillstice.com Port 443 should be hosting a Nextcloud instance.

I ran this command: sudo service apache2 start

It produced this output:

May 01 01:11:35 Icebox systemd[1]: Starting The Apache HTTP Server...
May 01 01:11:35 Icebox apachectl[12522]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
May 01 01:11:35 Icebox apachectl[12522]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
May 01 01:11:35 Icebox apachectl[12522]: no listening sockets available, shutting down
May 01 01:11:35 Icebox apachectl[12522]: AH00015: Unable to open logs
May 01 01:11:35 Icebox apachectl[12522]: Action 'start' failed.
May 01 01:11:35 Icebox apachectl[12522]: The Apache error log may have more information.
May 01 01:11:35 Icebox systemd[1]: apache2.service: Control process exited, code=exited status=1
May 01 01:11:35 Icebox systemd[1]: apache2.service: Failed with result 'exit-code'.
May 01 01:11:35 Icebox systemd[1]: Failed to start The Apache HTTP Server.

My web server is (include version):
Server version: Apache/2.4.29 (Ubuntu)
Server built: 2019-04-03T13:22:37

The operating system my web server runs on is (include version): Linux Mint 19.1 Tessa x86_64
4.15.0-48-generic

My hosting provider, if applicable, is: The domain chillstice.com points to an InterServer webserver, but the subdomain cloud points to this apache server that currently isn’t working.

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): Not on my machine, Interserver uses CPanel

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


I should clarify that I’m hosting various pages on virtualhosts and on eof them is a Nextcloud instance. It was installed using their snap package. I think it might have updated or changed the config because a new instance of Nextcloud is running on port 80 using httpd. I think this is preventing apache from running. This is weird to me because it was working fine through apache for 6 months. Only now, after a restart, did apache fail to start.

Yes, there is a running instance ( https://check-your-website.server-daten.de/?q=cloud.chillstice.com ):

Domainname Http-Status redirect Sec. G
http://cloud.chillstice.com/
75.71.147.56 200 0.340 H
https://cloud.chillstice.com/
75.71.147.56 -2 1.460 V
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 75.71.147.56:443

http works, https looks like a blocking firewall.

But there is a description

Installation abschließen

so it looks that you didn't finished that installation. May be part of the problem.

Yes that other Nextcloud instance is not configured. That’s because I want to use my already configured one.

Also, I made a HUGE DISCOVERY

I tried disabling the Nextcloud Snap package and I was able to start the Apache server properly. The snap must have been updated to include an auto-start script that uses httpd and port 80 to start the snap version of Nextcloud.

What a pain. Now I’m just trying to make sure everything is configured properly again. A few of my subdomains seem to be working properly right now including cloud.chillstice.com and s.chillstice.com (yourls link shortener server); however, my fastdl file servers fastdl.chillservers.com/sandbox for example is redirecting to the wrong domain for some reason.

2 Likes

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