{"action":"created","issue":{"url":"https://api.github.com/repos/serghey-rodin/vesta/issues/1008","repository_url":"https://api.github.com/repos/serghey-rodin/vesta","labels_url":"https://api.github.com/repos/serghey-rodin/vesta/issues/1008/labels{/name}","comments_url":"https://api.github.com/repos/serghey-rodin/vesta/issues/1008/comments","events_url":"https://api.github.com/repos/serghey-rodin/vesta/issues/1008/events","html_url":"https://github.com/serghey-rodin/vesta/issues/1008","id":196817233,"number":1008,"title":"Attempting to enable LetsEncrypt on domain produces error in /tmp","user":{"login":"didyouexpectthat","id":1329077,"avatar_url":"https://avatars.githubusercontent.com/u/1329077?v=3","gravatar_id":"","url":"https://api.github.com/users/didyouexpectthat","html_url":"https://github.com/didyouexpectthat","followers_url":"https://api.github.com/users/didyouexpectthat/followers","following_url":"https://api.github.com/users/didyouexpectthat/following{/other_user}","gists_url":"https://api.github.com/users/didyouexpectthat/gists{/gist_id}","starred_url":"https://api.github.com/users/didyouexpectthat/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/didyouexpectthat/subscriptions","organizations_url":"https://api.github.com/users/didyouexpectthat/orgs","repos_url":"https://api.github.com/users/didyouexpectthat/repos","events_url":"https://api.github.com/users/didyouexpectthat/events{/privacy}","received_events_url":"https://api.github.com/users/didyouexpectthat/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":9,"created_at":"2016-12-21T00:36:07Z","updated_at":"2016-12-24T21:49:26Z","closed_at":"2016-12-24T04:43:36Z","body":"### Operating System (OS/VERSION):\r\nDebian Jessie 8.6\r\n\r\n### VestaCP Version:\r\n0.9.8.17\r\n\r\n### Installed Software (what you got with the installer):\r\ndefaults + filesystem quota\r\nforce-https enabled\r\n\r\n### Steps to Reproduce:\r\nPreviously had letsencrypt installed before it became cool (aka pre-.16)\r\nAuto-update took place from .16 to .17\r\nSee letsencrypt option in domain now\r\nCheck the box for letsencrypt support, then apply\r\nUI errors:\r\n``Error: /tmp/tmp.CP6ftxhWgr/xyz.crt not found``\r\nI do see something populate in /tmp but disappears so quickly, can't capture the output.\r\n\r\n### Related Issues/Forum Threads:\r\nI tried to Google this error, checked github, and but not finding anything. Not sure entirely how the new letsencrypt UI support works.\r\nAlso notice that upgrade did not add those letsencrypt cronjobs I noticed.\r\n\r\n### Other Notes:\r\nDidn't find anything on the documentation about letsencrypt.\r\nI don't believe I ever installed letsencrypt-vesta. \r\nI did try v-add-letsencrypt-user for my admin user and other users that may need to get certificates but this did not help.\r\nhttps://vestacp.com/docs/\r\nAlso not seeing what log would give me more insight to follow for this one.\r\n```\r\n==> error.log <==\r\n2016-12-20 16:34:15 v-change-web-domain-sslcert  'admin' 'xyz' '/tmp/tmp.CP6ftxhWgr' 'no' [Error 3]\r\n```\r\nDocumentation says error 3 is 3\t\"E_NOTEXIST\tObject doesn't exist\" \r\n\r\n"},"comment":{"url":"https://api.github.com/repos/serghey-rodin/vesta/issues/comments/269101688","html_url":"https://github.com/serghey-rodin/vesta/issues/1008#issuecomment-269101688","issue_url":"https://api.github.com/repos/serghey-rodin/vesta/issues/1008","id":269101688,"user":{"login":"iamra","id":6845602,"avatar_url":"https://avatars.githubusercontent.com/u/6845602?v=3","gravatar_id":"","url":"https://api.github.com/users/iamra","html_url":"https://github.com/iamra","followers_url":"https://api.github.com/users/iamra/followers","following_url":"https://api.github.com/users/iamra/following{/other_user}","gists_url":"https://api.github.com/users/iamra/gists{/gist_id}","starred_url":"https://api.github.com/users/iamra/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/iamra/subscriptions","organizations_url":"https://api.github.com/users/iamra/orgs","repos_url":"https://api.github.com/users/iamra/repos","events_url":"https://api.github.com/users/iamra/events{/privacy}","received_events_url":"https://api.github.com/users/iamra/received_events","type":"User","site_admin":false},"created_at":"2016-12-24T21:49:26Z","updated_at":"2016-12-24T21:49:26Z","body":"I can confirm this has corrected the error for me. I completely removed Letsencrypt-vesta by reversing the directions as stated by @didyouexpectthat, then I changed the proxy template back to default, disabled ssl to clear the previous cert, then checked Lets Encrypt Support and saved. Cert was issued successfully. Vesta keeps getting better! "}}
{"actor":{"display_login":"iamra"}}