Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't add custom domain for status #1774

Open
shor0814 opened this issue Dec 26, 2024 · 2 comments
Open

Can't add custom domain for status #1774

shor0814 opened this issue Dec 26, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@shor0814
Copy link

shor0814 commented Dec 26, 2024

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:

  1. In Project Settings, Add a domain (works) and Verify (works) (mycompanyname.com)
  2. Click the Status Pages tab
  3. Click the name of the Status Page that you want to add the custom domain to
  4. Select Custom Domains
  5. Add a custom domain (subdomain=status, domain dropdown is mycompany.com domain),
  6. Do not select a certificate and click Create Status Page Domain
  7. Click the Check CNAME
  8. See error

Expected behavior
Should be a way to validate the subdomain, much like the verification for a domain.

Screenshots
Screenshot 2024-12-25 174651

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"

@shor0814 shor0814 added the bug Something isn't working label Dec 26, 2024
@shor0814
Copy link
Author

Reinstall fixed this, but now, I can't verify the CNAME.

image

image

Any hints?

@shor0814
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant