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:
- Add a brief tooltip or helper text next to the dropdown menu to clarify the requirement.
- Implement an auto-select logic where the vhost is automatically matched based on the domain undergoing the SSL update.
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: