Skip to content

SSL - LetsEncrypt the Console Proxy #3141

Closed

Description

@asender
ISSUE TYPE
  • Feature Idea
COMPONENT NAME
Console Proxy VM
CLOUDSTACK VERSION

4.11.1+

CONFIGURATION

LetsEncrypt the Console Proxy

Many new applications are now integrating letsencrypt. This could replace the old retired realhostip.com DNS resolver . Noone would need to muck around with certs again on the console proxy.

SUMMARY

New Global Option For Letsencrypt enable on console proxy. Letsencrypt domain name option for letsencrypt ssl auto renew

Activity

  1. DaanHoogland commented on Jan 29, 2020

    @DaanHoogland
    Contributor

    any plans for this @asender ?

  2. DaanHoogland commented on Dec 15, 2020

    @DaanHoogland
    Contributor

    @davidjumani @weizhouapache can you advice how this would impact novnc? it seems not relevant to the type of console but i am not sure.

  3. weizhouapache commented on Dec 15, 2020

    @weizhouapache
    Member

    @davidjumani @weizhouapache can you advice how this would impact novnc? it seems not relevant to the type of console but i am not sure.

    @DaanHoogland it provides a default certificate (like old realhostip.com) to systemvms. It is an enhancement . ajax/novnc console will not be impacted.

  4. added this to the 4.16.0.0 milestone on Dec 16, 2020
  5. modified the milestones: 4.16.0.0, unplanned on Jul 27, 2021
  6. 4 remaining items

  7. yadvr commented on Aug 17, 2022

    @yadvr
    Member

    My email/suggestion was to use RFC1918 networks for both public and management networks, of course this won't work for your use-case. You can use the traditional approach to setup/upload certificates (until something like this feature is fully automated).

  8. daviftorres commented on Sep 4, 2025

    @daviftorres
    Contributor

    Dear @asender,

    I’d like to apologise for having a different view on the certificate strategy for the Console Proxy (and System VMs in general).

    Since System VMs are ephemeral, they would request new certificates every time they are redeployed. This could quickly hit Let’s Encrypt rate limits (https://letsencrypt.org/docs/rate-limits/).

    A better approach is to use a dedicated instance (or even a container) to request certificates, for example a wildcard via DNS challenge, about 30 days before expiry. The instance can then push the certs to CloudStack for use by the System VMs.

    If you’re interested, I can also share how we set this up with HashiCorp Vault to securely store certificates and allow consumers to fetch only the ones they’re permitted to use.

  9. locked and limited conversation to collaborators on Sep 8, 2025
  10. converted this issue into a discussion #11597 on Sep 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions