Trouble issuing certificate for longbeachmarina.net

My domain is: longbeachmarina.net

I am trying to create a certificate with Let's Encrypt and it gives me problems with the domain:
longbeachmarina.net

It produced this output:
Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/8559307478.

Details: Type: urn:ietf:params:acme:error:dns

Status: 400
Detail: No valid IP addresses found for longbeachmarina.net

My web server is (include version):
My host OS is CentOS Linux 7.8.2003 (Core). I am running Plesk Obsidian, Version 18.0.31
Update #1, last updated on Nov 11, 2020 01:52 AM

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

My hosting provider, if applicable, is: Media Temple

I can log in 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): yes

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): unknown

1 Like

Welcome to the Let's Encrypt Community :slightly_smiling_face:

1 Like

Hello @joefino !

longbeachmarina.net: No address associated with hostname
Do you have a public IP address? If so I don't know how to find it.
That's a must have. (To serve your domain name)

2 Likes

Sorry @Rip. Didn't see you responding for some reason.

2 Likes

NP... I knew you were lurking nearby!
At least we know where to start OP on his journey!

2 Likes

How can that even be possible? There is an A Record in GoDaddy for the site that resolves to my IP: 72.10.32.154

Please forgive my DNS ignorance on this.

2 Likes

Hi @joefino

only your www version has an ip address - see https://check-your-website.server-daten.de/?q=longbeachmarina.net

Host Type IP-Address is auth. ∑ Queries ∑ Timeout
longbeachmarina.net A yes 1 0
AAAA yes
www.longbeachmarina.net A 72.10.32.154 Ashburn/Virginia/United States (US) - GoDaddy.com, LLC Hostname: ssd-ingeniumio.com yes 1 0
AAAA yes

Your non-www doesn't have one.

So add the same A-record with your main domain (may be @ as domain name).

3 Likes

Thanks. I had no idea it was this messed up. I’m relying on the client’s IT team to make the DNS changes, and do not have direct access to it myself.

3 Likes

I wouldn't worry too much. It's a more common mistake than you might imagine (and a simple one to fix).

:slightly_smiling_face:

1 Like