Certificates installed; can't load https pages

I successfully installed Lets Encrypt certificates. But still I cannot load https versions of my pages, it tries to load for a while with ‘establishing secure connection’ at the bottom, then gives the ‘this site can’t be reached, the connection was reset’ error. SSL Checker gives: ||### bacstream.live resolves to 44.233.31.65|
| — | — |
||### Server Type: nginx/1.14.0 (Ubuntu)|
||### No SSL certificates were found on bacstream.live. Make sure that the name resolves to the correct server and that the SSL port (default is 443) is open on your server’s firewall.|

I do have port 443 open on AWS server firewall settings.

My domain is: bacstream.live

I ran this command:

It produced this output:

My web server is (include version): Ubuntu 18.04

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

My hosting provider, if applicable, is: AWS

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

1 Like

Hi @farrelldawn

checking your domain via https://check-your-website.server-daten.de/?q=bacstream.live - that’s a blocking firewall answer:

Domainname Http-Status redirect Sec. G
http://bacstream.live/ 44.233.31.65 No GZip used - 415 / 1426 - 29,10 % possible 200 Html is minified: 102,30 % 0.356 H
small visible content (num chars: 329) Streaming Status Pages     Status of Connections     Status of the Stream     Feed for Computers? Live Stream “Full 1080 Resolution”     Feed for the App: Live Stream “Low Resolution”     Feed for Computers?: Live Stream “720 Resolution”            
http://www.bacstream.live/ 44.233.31.65 No GZip used - 415 / 1426 - 29,10 % possible 200 Html is minified: 102,30 % 0.370 H
small visible content (num chars: 329) Streaming Status Pages     Status of Connections     Status of the Stream     Feed for Computers? Live Stream “Full 1080 Resolution”     Feed for the App: Live Stream “Low Resolution”     Feed for Computers?: Live Stream “720 Resolution”            
https://bacstream.live/
44.233.31.65 -2 1.527 V
ConnectFailure - Unable to connect to the remote server
https://www.bacstream.live/
44.233.31.65 -2 1.526 V
ConnectFailure - Unable to connect to the remote server

It’s not a “not working https”, that would produce a timeout (10 seconds, not 1,5 s).

AWS has additional firewalls, find these and open these.

Works https internal from that machine?

2 Likes

You ask ‘works https internal from that machine?’ I’m not sure exactly what you’re asking, but no, I can’t get the https site to load from anywhere, including this computer that I have been doing all the work on.

I have 22, 80, 443, and 1935 set to open on AWS - I’m not sure what else to open - as far as I understand 443 is one that needs to be open to allow https traffic.

1 Like

A console on the ip 44.233.31.65, then

curl https://bacstream.live/

If it doesn’t work internal, it can’t work external. If it works internal, it’s a firewall- or router problem.

2 Likes

OK - using that I get the response curl: (7) failed to connect to bacstream.live port 443: connection refused

So this is saying 443 is blocked somewhere along the way? Could it be at the domain registrar level? The IP server clearly has a rule showing 443 open.

1 Like

No, that says, your port 443 may not work, so your nginx vHost may not work / doesn’t exist etc.

Looks that you didn’t installed the certificate. But you didn’t shared the required informations, so you have to fix it.

2 Likes