Hey there,

maybe someone here has had a smilar problem in the past. I set up a DigitalOcean droplet via Laravel Forge and deployed a simple NodeJS app. It's running smoothly as long as it's accessed via http.

When trying to set up LetsEncrypt I do however consistently get the same error. I added the output below (I removed the certificate id and domains, just in case).

Any pointers?

Thanks!

Creating well known challenge directory... Installing LetsEncrypt client... Cloning into 'letsencrypt1---419'... Note: checking out 'tags/v0.5.0'.

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 performing another checkout.

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

git checkout -b <new-branch-name>

HEAD is now at 4a81175... version 0.5.0 Configuring client... Restarting Nginx... Generating Certificate...

INFO: Using main config file /root/letsencrypt1---419/config

• Generating account key...
• Registering account key with ACME server...
• Done!

INFO: Using main config file /root/letsencrypt1---419/config

Processing w---.de with alternative names: www.w---.de

• Signing domains...
• Creating new directory /root/letsencrypt1---419/certs/w---.de ...
• Creating chain cache directory /root/letsencrypt1---419/chains
• Generating private key...
• Generating signing request...
• Requesting challenge for w---.de...
• Requesting challenge for www.w---.de...
• Responding to challenge for w---.de...
• Challenge is valid!
• Responding to challenge for www.w---.de...
• Challenge is valid!
• Requesting certificate...
• Checking certificate...
• Done!
• Creating fullchain.pem...
• Walking chain...
• ERROR: An error occurred while sending get-request to http://cert.int-x3.letsencrypt.org/ (Status 301)

Details:

ERROR: Walking chain has failed, your certificate has been created and can be found at /root/letsencrypt1---419/certs/w---.de/cert-1---426.pem, the corresponding private key at privkey-1---426.pem. If you want you can manually continue on creating and linking all necessary files. If this error occurs again you should manually generate the certificate chain and place it under /root/letsencrypt1---419/chains/4f06f81d.chain (see http://cert.int-x3.letsencrypt.org/)