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
Describe the bug
Add a custom domain, when I select Add CNAME to verify the CNAME, I get an error "Custom Domains not enabled for this OneUptime installation. Please contact your server admin to enable this feature." To Reproduce
Steps to reproduce the behavior:
In Project Settings, Add a domain (works) and Verify (works) (mycompanyname.com)
Click the Status Pages tab
Click the name of the Status Page that you want to add the custom domain to
Select Custom Domains
Add a custom domain (subdomain=status, domain dropdown is mycompany.com domain),
Do not select a certificate and click Create Status Page Domain
Click the Check CNAME
See error
Expected behavior
Should be a way to validate the subdomain, much like the verification for a domain.
Screenshots
Desktop (please complete the following information):
OS: Ubuntu
Browser Chrome
Version 131.0.6778.205
Deployment Type
Kubernetes
Additional context
My current values.yaml is below:
host: oneuptime.mycompany.com
# If hosted on non-ssl server then change this to http
httpProtocol: https
statusPage:
cnameRecord: oneuptime.mycompany.com
oneuptimeIngress:
enabled: true
hosts:
- oneuptime.mycompany.com
global:
storageClass: "local-path"
The text was updated successfully, but these errors were encountered:
For anyone wondering, I had to add status.mycompany.com (Cname record) to oneuptimeIngress.hosts so it containeed my main host, and any status hostsnames. Seems kind of odd, so still should be considered a bug. I did find the solution through an incident search for the same problem.
Describe the bug
Add a custom domain, when I select Add CNAME to verify the CNAME, I get an error "Custom Domains not enabled for this OneUptime installation. Please contact your server admin to enable this feature."
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should be a way to validate the subdomain, much like the verification for a domain.
Screenshots
Desktop (please complete the following information):
Deployment Type
Kubernetes
Additional context
My current values.yaml is below:
The text was updated successfully, but these errors were encountered: