Unable to connect to the server


#1

I’m trying to get SSL up and running and used the instructions on this page.

However, when I get to the point of testing using ssllabs I get “Unable to connect to the server”

In setup I chose to redirect all http traffic to https so as of right now I can’t access the site. My server has a few websites on it so I have Virtual Host set up. All other sites are still working fine. Is there something I need to do on Godaddy in order to get things working, or something else I may have missed? Thanks!


#2

Hi @fpt,

Could you please complete the whole help form? The answers could be very useful in understand better what’s going on.


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:

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):


#3

My domain is: www.bohttrophy.com

I ran this command: https://www.digitalocean.com/community/tutorials/how-to-set-up-let-s-encrypt-certificates-for-multiple-apache-virtual-hosts-on-ubuntu-14-04

It produced this output: Unable to connect to the server

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

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

My hosting provider, if applicable, is: Godaddy

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


#4

Thanks! Do you happen to know what the output of the Certbot command was when you ran Certbot?

Is it possible that there’s a host or network firewall (like a ufw rule or a hosting provider policy group rule) that prevents incoming connections on port 443? Can you tell with ss -tlp whether Apache is indeed listening on your TCP port 443?

Edit: I can see that your certificate was successfully issued and the the port 80 to port 443 redirect is in place and working. So I think that it’s very likely that there’s some kind of firewall rule in place that’s blocking port 443 connections at the moment. (Another possibility could be an Apache misconfiguration, but then I might expect that Apache wouldn’t start up at all! You could also look at Apache error logs within /var/log just to see if there’s anything relevant logged there.)


#5

Thanks, it does help to make sure port 443 is forwarded on my router to my Webserver. Simple fix for a simple question. Thanks again!


#6

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