You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when a custom domain added to Appwrite has its SSL managed externally (e.g., via NGINX or Cloudflare), and Appwrite cannot complete the Let's Encrypt verification due to factors like front-facing proxies, the domain鈥檚 SSL certificate status is incorrectly marked as Failed.
This can be misleading as the domain may have a valid and active SSL certificate managed elsewhere. The current situation leads to unnecessary alarm and confusion if the page is check after a while.
馃帳 Pitch
We could display the status as Active with a tooltip message that clearly states that the SSL is not managed by Appwrite & renewal is subject to the provider rather than Failed, even if it cannot directly verify the certificate. This change would enhance user experience by providing a more accurate and reassuring interface.
馃憖 Have you spent some time to check if this issue has been raised before?
馃敄 Enhancement description
Currently, when a custom domain added to Appwrite has its SSL managed externally (e.g., via NGINX or Cloudflare), and Appwrite cannot complete the Let's Encrypt verification due to factors like front-facing proxies, the domain鈥檚 SSL certificate status is incorrectly marked as
Failed
.This can be misleading as the domain may have a valid and active SSL certificate managed elsewhere. The current situation leads to unnecessary alarm and confusion if the page is check after a while.
馃帳 Pitch
We could display the status as
Active
with a tooltip message that clearly states that the SSL is not managed by Appwrite & renewal is subject to the provider rather thanFailed
, even if it cannot directly verify the certificate. This change would enhance user experience by providing a more accurate and reassuring interface.馃憖 Have you spent some time to check if this issue has been raised before?
馃彚 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: