Skip to content

fix(ux): SSL Certificate process #314

@c-bizarro

Description

@c-bizarro

I’ve identified a friction point in our current SSL certificate workflow for subdomains. Currently, the system requires users to manually specify the domain vhost, but this requirement isn't explicitly stated in the UI. This often leads to the following API error:

{"status":400,"body":"VirtualHostHostnameIsRequired","readableMessage":""}

To streamline this process and reduce failed requests, I propose the following improvements:

  1. Add a brief tooltip or helper text next to the dropdown menu to clarify the requirement.
  2. Implement an auto-select logic where the vhost is automatically matched based on the domain undergoing the SSL update.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    approved

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions