Closed krodik closed 6 years ago
I think this might be the issue that @drybjed mentioned to me on Twitter a day ago. I need to update the debops.pki
configuration to support the new ACME v2 tool.
This issue should now be fixed in the DebOps monorepo via https://github.com/debops/debops/pull/250.
I can confirm this issue has been resolved...
Can you explain how you fixed the issue @krodik? I'm seeing the same issue as well.
@carlalexander After running debops-update
I went and deleted the realm directory for the website under /etc/pki/realms/domain
on the actual server before I ran debops wordpress
(I might have re-run the sets of commands from your installation tutorial). That did the trick.
Note: Adding this pki_acme_tiny_version: '4ed13950c0'
didn't work for me as suggested here
@carlalexander is there any way to use multisite subdomain and obtain an ssl for each one of the subdomains?
I do it this way for my blog:
wordpress__pki__default_realm_subdomains: [ 'www', 'es' ]
But I've found some weird bugs with the nginx configuration that I fixed by hand. I need to find a solution to them and migrate them to the debops repo.
Were you able to get this working @krodik?
I did not...
How far did you get? What's the current issue?
Sorry for the late response... I didn't get it to work with multiple sub-domains. For some reason it would work on one domain and not on the others. I found myself hacking away the nginx configuration to the point I gave up. I settled with sub-folders instead for the project I was working on. I'm going to close this issue for now.
Hello,
I'm unable to obtain a certificate from let's encrypt. Everything seems normal, but I can't get to the website without Google chrome's warning of site not secured.
This is the output of my /etc/pki/realms/{domain.com}/acme/error.log
Thank you..