interbrite / letsencrypt-vesta

Automate Let's Encrypt Certificate Installation for VestaCP
Other
217 stars 64 forks source link

Vesta R16 removed v-list-web-domains-alias #27

Closed thinkingcap closed 8 years ago

thinkingcap commented 8 years ago

From error log

/usr/local/bin/letsencrypt-vesta: line 64: /usr/local/vesta/bin/v-list-web-domains-alias: No such file or directory

cfgalvani commented 8 years ago

@thinkingcap same problem here..

omz187 commented 8 years ago

I got these two errors when i tried to run the command: /usr/local/bin/letsencrypt-vesta: line 64: /usr/local/vesta/bin/v-list-web-domains-alias: No such file or directory /usr/local/bin/letsencrypt-vesta: line 224: /usr/local/certbot/certbot-auto: No such file or directory

If you having problems with it the way i managed to fix it was the /usr/local/certbot/ was missing which affects the v-list-web-domains-alias. (which doesn't exist anyway)

1) You need to re-upload the "cerbot" folder to /usr/local/certbot/ (if you cant find a copy ill send you mines as i manage to take it from a VPS which installed correctly )

2) Run a SSL install command Example: letsencrypt-vesta admin test.xyz (In SSH)

3) The error should now have changed to this: /usr/local/bin/letsencrypt-vesta: line 64: /usr/local/vesta/bin/v-list-web-domains-alias: No such file or directory /usr/local/bin/letsencrypt-vesta: line 224: /usr/local/certbot/certbot-auto: Permission denied Let's encrypt returned an error status. Aborting.

4) Go to /usr/local/certbot/ and set permissions for: All Folders = 755 (examples of folder: .get, letshelp-certbot ,tools ) All Other files in the directory = 644 (examples of files: .pep8, Dockerfile )

IMPORTANT PART Set these files below in that directory to = 755 certbot-auto letsencrypt-auto pep8.travis.sh tox.cover.sh

5) That should fix the problem, as if fixed mines

thinkingcap commented 8 years ago

@cfgalvani See my PR for a fix.

cfgalvani commented 8 years ago

@thinkingcap I saw yesterday that vesta has Letsencrypt support via CLI now. Thank you!

jpitoniak commented 8 years ago

I'm looking for a solution to this. The answer may just be to distribute a copy of the old v-list-web-domains-alias script in this project, but I need to test it before I do that. Hopefully this was an oversight on the Vesta team's part and the script will be restored on a future update.

jpitoniak commented 8 years ago

I updated the script on Saturday to pull the aliases using v-get-web-domain-value, which should resolve this issue.

glennharmon commented 6 years ago

I simply had to update the script to reflect the actual location of the certbot_auto file. It was not in the cerbot folder, but in /usr/local/letsencrypt/.