Question

Pointing A Subdomain From Route53 To CENTOS Droplet Displaying Error : This site can’t be reached The connection was reset

Am trying to point a subdomain from Route53 to a Droplet I created. I keep getting, The Site Cannot be reached the connection was reset error.

Below is my setup

I have a virtual host setup on my centOS droplet like this:

<VirtualHost *:80> ServerName savings.corpreneur.com.ng

DocumentRoot /var/www/html/platform/public

<Directory /var/www/html/platform/public> Options Indexes FollowSymLinks MultiViews AllowOverride All Order allow,deny allow from all DirectoryIndex index.php </Directory>

#ErrorLog /var/www/html/platform/error.log LogLevel warn #CustomLog /var/www/html/platform/access.log combined RewriteEngine on RewriteCond %{SERVER_NAME} =savings.corpreneur.com.ng RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent] </VirtualHost>

As for my /etc/hosts file, I have the following content:

127.0.0.1 corpreneur corpreneur 127.0.0.1 localhost.localdomain localhost 127.0.0.1 localhost4.localdomain4 localhost4 139.59.150.44 savings.corpreneur.com.ng

On AWS Route53 I created A Record with the below Detail

Name: savings .corpreneur.com.ng Value: 139.59.150.44

And On My Droplet I have below

Record Hostname Value A savings.corpreneur.com.ng 139.59.150.44 NS savings.corpreneur.com.ng ns1.digitalocean.com NS savings.corpreneur.com.ng ns2.digitalocean.com NS savings.corpreneur.com.ng ns3.digitalocean.com

When I check the NS record, it shows DigitalOcean NS record https://dnschecker.org/#NS/savings.corpreneur.com.ng

When I Also Check the A record https://dnschecker.org/#A/savings.corpreneur.com.ng It shows the IP of the droplet

So could it be an issue with SELinux and not my setup?

I expect this to work but it doesn’t, am confused about this, what am I doing wrong. I need help on this. Thanks!


Submit an answer


This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Accepted Answer

Hi,

You have a redirect to HTTPS in your port 80 vhost. But you’re missing the SSL vhost (for port 443). So Apache isn’t listening on that port at all. Hence the connection reset error:

$ curl -I http://savings.corpreneur.com.ng/ HTTP/1.1 301 Moved Permanently Date: Fri, 28 Sep 2018 19:15:13 GMT Server: Apache/2.4.6 (CentOS) Location: https://savings.corpreneur.com.ng/ Content-Type: text/html; charset=iso-8859-1

$ curl -vvv https://savings.corpreneur.com.ng/

  • Trying 139.59.150.44…
  • connect to 139.59.150.44 port 443 failed: Connection refused
  • Failed to connect to savings.corpreneur.com.ng port 443: Connection refused
  • Closing connection 0

Thanks very much, I just needed to install cert-bot. Everything was taken care of with cert-bot auto.

Am grateful

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel