Laravel Forge Letsencrypt Fails-CodePudding

This is a long shot, but wondering if anyone else has run into a similar issue.

I'm trying to set up a new site on Laravel Forge using DigitalOcean as my provider. I've got the server instance set up and the app is installed, but when I attempt to navigate to the site I get a SSL_ERROR_UNRECOGNIZED_NAME_ALERT error.

DNS is being provided by CloudFlare (proxied) and the A record resolves correctly. I went into my Forge dashboard to request a new SSL Cert from LetsEncrypt, but that failed with the error output below.

2022-12-03 00:00:35 URL:https://forge-certificates.laravel.com/le/1617562/1825058/ecdsa?env=production [4557] -> "letsencrypt_script1670025635" [1]
Cloning into 'letsencrypt1670025635'...
Note: switching to '91cccc0c234e4decf0a19595fa19a6f306788032'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c <new-branch-name>

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at 91cccc0 ensure newline before new section in openssl.cnf
    ERROR: An error occurred while sending post-request to https://acme-v02.api.letsencrypt.org/acme/new-order (Status 400)

Details:
HTTP/2 400 
server: nginx
date: Sat, 03 Dec 2022 00:00:39 GMT
content-type: application/problem json
content-length: 173
cache-control: public, max-age=0, no-cache
link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
replay-nonce: 5CA2cs4FJk70Onq0iakIYvXisgUnrGMELGxh0lXsKjFUAWU

{
  "type": "urn:ietf:params:acme:error:accountDoesNotExist",
  "detail": "Account \"https://acme-v02.api.letsencrypt.org/acme/acct/853465757\" not found",
  "status": 400
}

I've looked around a bit and I've seen similar issues, but none of the solutions being suggested seem relevant (or they didn't solve the problem after attempting them.) Any and all advice is appreciated. Thanks in advance!

CodePudding user response：

It looks like the issue is with your SSL certificate. You may need to generate a new certificate from LetsEncrypt and configure it in the Forge dashboard. If the issue persists, it may be worth checking your DNS settings to ensure that the A record is pointing to the correct server IP address. You may also need to check your Forge configuration to ensure that the domain name is configured correctly.