Plesk forum can be found here https://talk.plesk.com/
Hi @Bruce5051
I made some modifications and still getting same issue...
I'm not convinced that Plesk community will help.
Hi @Farid, I haven't seen the propagation of the DNS A records happen yet.
Using this online tool https://unboundtest.com/ is presently seeing https://unboundtest.com/m/A/venus-dating.com/G56QYYHM showing an IPv4 Address of 35.181.129.231
Query results for A venus-dating.com
Response:
;; opcode: QUERY, status: NOERROR, id: 44913
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version 0; flags: do; udp: 512
;; QUESTION SECTION:
;venus-dating.com. IN A
;; ANSWER SECTION:
venus-dating.com. 0 IN A 35.181.129.231
----- Unbound logs -----
May 17 18:22:50 unbound[9718:0] notice: init module 0: validator
May 17 18:22:50 unbound[9718:0] notice: init module 1: iterator
May 17 18:22:50 unbound[9718:0] info: start of service (unbound 1.16.3).
May 17 18:22:51 unbound[9718:0] info: 127.0.0.1 venus-dating.com. A IN
May 17 18:22:51 unbound[9718:0] info: resolving venus-dating.com. A IN
May 17 18:22:51 unbound[9718:0] info: priming . IN NS
And I see Ports 80 & 443 are CLOSED.
$ nmap -Pn -p80,443 venus-dating.com
Starting Nmap 7.80 ( https://nmap.org ) at 2023-05-17 18:26 UTC
Nmap scan report for venus-dating.com (35.181.129.231)
Host is up (0.16s latency).
rDNS record for 35.181.129.231: ec2-35-181-129-231.eu-west-3.compute.amazonaws.com
PORT STATE SERVICE
80/tcp closed http
443/tcp closed https
Nmap done: 1 IP address (1 host up) scanned in 0.54 seconds
Hi @Bruce5051
I don't know how but it seems like issue is now solved.
I deleted the DNS zone from Route 53, I just kept Domain registration on it and then I added again domain (website) into Plesk and don't know how and why but Let's encrypt succeed to install the SSL certificate, website is now online and ports are open...
But I'm just wondering how it could be possible as I removed the hosted zone "venus-dating" from Route 53.
When I go to Plesk record zone I can see several entries like this shown in my screenshot.
From Route 53 side Domain is displayed these zones below.
I'm a bit of where is the DNS zone hosted now... 
Kindly wait to see if there are more knowledgeable Let's Encrypt community volunteers willing to assist.
It seems like issue is now solved.
To resume I kept Route 53 as registrar for the domain.
I set Plesk to be the primary DNS Zone to let Let's encrypt issuing certificates automatically to the domains.
Many thanks for your help.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.