DNS is succeeded propagated, yet the site can't be reached
In the process of configuring DNS (7/24/2021), I added an A record ("172.105.188.93") to my domain ("buddyshiphobarttoastmasters.com") as well as an rDNS. The DNS propagation has also gone through.
The IP address ("172.105.188.93") is working, but the domain is not. Results are shown below:
#
This site can’t be reachedli2076-184.members.linode.com refused to connect.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED
#
I can't figure out what the problem will be. Hope you can help me. Thanks in advance.
4 Replies
✓ Best Answer
The "http" version resolves fine but the "https" version does not. You need to pop an SSL certificate on the site.
That's not all… you have to configure your web server to serve on port 443 (https) and actually use the cert too. You can put all the certs on your Linode you want…one an hour for the next 24 if that floats your boat…but without step two, they'll all just be disc space wasters.
probably have to install Snap.
Only if your distro has snapd… While snapd is available on pretty much any distro if you're willing to install/manage it yourself, Canonical actively pushes it on Ubuntu. You don't need snapd to install certbot. I had certbot installed on Ubuntu 18.04 without snapd before I switched to Debian. I have certbot on Debian 10 and I'd give up my Linode before installing snapd on it.
-- sw
Looks like li2076-184.members.linode.com is redirected to https.
Edit:
IP doesn't match
PING li2076-184.members.linode.com (172.105.167.184) 56(84) bytes of data.
PING buddyshiphobarttoastmasters.com (172.105.188.93) 56(84) bytes of data
The "http" version resolves fine but the "https" version does not. You need to pop an SSL certificate on the site.
Go here: https://certbot.eff.org/
Put in your web-server (nginx or apache?) and whatever OS you are running, and follow the directions… probably have to install Snap.
ANC