Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • infrastructure infrastructure
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 106
    • Issues 106
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 13
    • Merge requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Arch LinuxArch Linux
  • infrastructureinfrastructure
  • Issues
  • #30
Closed
Open
Issue created May 16, 2020 by Jelle van der Waa@jelle🚧Developer

Fix certificate bootstrapping issue by switch to DNS-01 challenge

Our current way of bootstrapping a new service does not really bootstrap an valid SSL certificate when deploying a role. As our nginx configuration does expects a certificate to be there, but it's not there yet and nginx needs to run so this is a classic chicken egg problem.

Hetzner has a DNS API now so we can switch to DNS verification.

  • https://community.hetzner.com/tutorials/letsencrypt-dns
  • https://github.com/Estivador/terraform-provider-hdns
  • https://github.com/ctrlaltcoop/certbot-dns-hetzner
  • https://github.com/alxrem/terraform-provider-hdns

Cons:

  • Every machine can now issue a wildcard certificate :/
Edited Jan 10, 2021 by Kristian Klausen
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking