Error Code: 15 - SSL - Lets Encrypt

[droidman]

Still suffering from this today.

[pepsi]

The aforementioned fix in v-add-letsencrypt-domain should address the issue. It has already been committed to the GitHub repo and will be included in the next release. Make sure you're on the latest version of VestaCP.

[fanok]

I have same problem.
v-add-letsencrypt-domain file is right $domain and I did reinstallation.
The problem same still.

[Mariop]

I have same problem.
v-add-letsencrypt-domain file is right $domain and I did reinstallation.
The problem same still.

I have exactly the same problem. Can not decide.
Did you succeed? .

[droidman]

No, still waiting for an update. Sometimes it works on new vesta installations, sometimes i make a new server and fails and never works, same datacenter, same configuration, very weird

[Mariop]

No, still waiting for an update. Sometimes it works on new vesta installations, sometimes i make a new server and fails and never works, same datacenter, same configuration, very weird

I'm also waiting for the update. Why then do it for a very long time.
This is a global problem ...

[droidman]

yeah, free projects like vesta save us every day but they look a lot slower than paid solutions for obvious reasons, i would love to be able to help them fix the problem but unfortunately that is not my area of expertise

[sansansan]

Hi!

Have the same problem.
Os:Ubuntu 16.04
Web:nginx + php-fpm

Nothing helps. I have error 15 when are I'm trying to add the Lets Encrypt to a domain and click Save.

[dsystem]

Some updates have occurred on this subject after the release of version 0.9.8-24

You can do direct update of github -> https://github.com/serghey-rodin/vesta

Backup existing

Code: Select all

zip -r /root/vesta-back.zip /usr/local/vesta

Get latest version from Git

Code: Select all

git clone https://github.com/serghey-rodin/vesta.git /root/vestaNew
yes | cp -rf /root/vestaNew/* /usr/local/vesta

[m0ze]

Faced the same problem today, after several attempts and two reinstalls I've fixed this error by disabling two options for my domain on CloudFlare account: "force HTTPS" and "fix HTTP" (later I've tested this steps for two other domains - all the same things). Maybe this will help someone.