To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you’re using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.
Your account credentials have been saved in your Certbot
configuration directory at /etc/letsencrypt. You should make a
secure backup of this folder now. This configuration directory will
also contain certificates and private keys obtained by Certbot so
making regular backups of this folder is ideal.
root@w3:~# ss -tln
State Recv-Q Send-Q Local Address:Port Peer Address:Port
LISTEN 0 128 :80 :
LISTEN 0 128 :22 :
LISTEN 0 128 :::80 :::
LISTEN 0 128 :::22 :::
root@w3:~#
1.Multiple IPs:
Name: vplaya.com
Addresses: 45.55.126.41
159.65.175.99
2. Unable to connect to http://vplaya.com/ via both IPs:
Connecting to vplaya.com (vplaya.com)|159.65.175.99|:80… failed: No route to host.
Connecting to vplaya.com (vplaya.com)|45.55.126.41|:80… failed: Connection timed out.
Ok, questions:
[1] Do you want your entire site to be behind CloudFlare?
[2a] Do you use both IPs (45.55.126.41, 159.65.175.99)?
[2b] Are they working?
By the way, DNS records are unordered. Each IP will receive approximately 50% of traffic.
Edit: That will make it tricky -- though possible -- to use Let's Encrypt HTTP validation. You might want to use DNS validation, if your ACME client has a Cloudflare DNS plugin.
Well it seems like I ran out option as i am not sure what to do now. Till there are any advises, I’ll have to fallback to a backup instance as I’ve been disconnected to too long.