Issue with SSL Certificates with Apache on Debian

Hi

I followed the guide document at https://www.linode.com/docs/security/ss … -you-begin">https://www.linode.com/docs/security/ssl/ssl-apache2-debian-ubuntu#before-you-begin to have 'SSL certificate with Apache'

Apache2 started OK but my site doesn't work and when tested with the command 'openssl s_client -CApath /etc/ssl/certs/ -connect example.com:443' I get the following errors:

connect: Connection refused

connect:errno=111

Please, can someone tell as what I am doing wrong.

Thanks

5 Replies

At first look at Apache error logs

Is Apache running? If you run sudo netstat -lvpnut you should get something like the following:

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
. . .
tcp6       0      0 :::80                   :::*                    LISTEN      4049/apache2
. . .

If you don't see something listening on port 80, then Apache isn't running.

Hi Vance

I am not configuring Apache to use the SSL Certificate anymore but please, could you look at the following and advise me if things look OK. If not, what is wrong and how do I fix it? Thanks

'sudo netstat -lvpnut' command outputs the following:

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State                            PID/Program name
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN                           3316/rpcbind
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN                           3338/sshd
tcp        0      0 0.0.0.0:25              0.0.0.0:*               LISTEN                           4045/master
tcp        0      0 0.0.0.0:37945           0.0.0.0:*               LISTEN                           3325/rpc.statd
tcp        0      0 127.0.0.1:3306          0.0.0.0:*               LISTEN                           3785/mysqld
tcp6       0      0 :::111                  :::*                    LISTEN                           3316/rpcbind
tcp6       0      0 :::80                   :::*                    LISTEN                           5733/apache2
tcp6       0      0 :::42097                :::*                    LISTEN                           3325/rpc.statd
tcp6       0      0 :::22                   :::*                    LISTEN                           3338/sshd
tcp6       0      0 :::25                   :::*                    LISTEN                           4045/master
udp        0      0 0.0.0.0:947             0.0.0.0:*                                                3316/rpcbind
udp        0      0 127.0.0.1:957           0.0.0.0:*                                                3325/rpc.statd
udp        0      0 0.0.0.0:46153           0.0.0.0:*                                                3325/rpc.statd
udp        0      0 0.0.0.0:111             0.0.0.0:*                                                3316/rpcbind
udp6       0      0 :::947                  :::*                                                     3316/rpcbind
udp6       0      0 :::111                  :::*                                                     3316/rpcbind
udp6       0      0 :::35980                :::*                                                     3325/rpc.statd

Everything looks good here. If you had your server still trying to serve an SSL certificate you'd see an entry for :::443, but as you got rid of the SSL configuration there is no issue.

If you try running the SSL certificate again, set the directory block for your SSL enabled site to be "", setting your IP address before the colon.

Good luck!

@sohsoh5:

Everything looks good here. If you had your server still trying to serve an SSL certificate you'd see an entry for :::443, but as you got rid of the SSL configuration there is no issue.

If you try running the SSL certificate again, set the directory block for your SSL enabled site to be "", setting your IP address before the colon.

Good luck!

Brilliant! thanks for the reply, this gave me some reassurance

Regards

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct