Skip to content

Conversation

@Mstiekema
Copy link
Member

Yay! Very nice! I think everything is fixed with this, just have to run all the updated tasks to make sure all the subdomains are still working with the wildcard cert.

Maybe we can also destory a bit of the websites.yml with this PR? Who knows? Only time will tell..

@Mstiekema
Copy link
Member Author

IMPORTANT: Merijn please run the proper roles for make sure it works xoxo

@Riscky
Copy link
Member

Riscky commented Apr 5, 2022

This seems to fail for https://dev.svsticky.nl/ (The certificate is only valid for *.dev.svsticky.nl.). Do we need to request 2 separate certificates?

@Mstiekema
Copy link
Member Author

Do we need to request 2 separate certificates?

Nope, I only had to add the hostname as a seperate domain to the certbot command and poof it's working

@Mstiekema
Copy link
Member Author

TODO: Create a loop to request certs for *.domain.com and domain.com for the following sites:

  • svsticky.nl
  • savadaba.nl
  • execut.nl
  • dgdarc.com

@Riscky Riscky linked an issue Jun 8, 2022 that may be closed by this pull request
--cert-name {{ item }}
--dns-digitalocean
--dns-digitalocean-credentials /etc/letsencrypt/certbot-creds.ini
--domain "*.{% if 'staging' in group_names %}dev.{% endif %}{{ item }}"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

note: to make this work, every domain should get an extra domain record (dev.domainame pointing to the staging server).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement Proposes (changes to) a feature maintainability

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Request wildcard certificates

4 participants