Skip to content

chore(alt_cert): Note regarding issues when controller dns and alt cert #1141

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+4 −0
Open

chore(alt_cert): Note regarding issues when controller dns and alt cert #1141

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docusaurus/docs/guides/deployments/console.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,10 @@ Before generating an SSL certificate, ensure you have a valid DNS record pointin
your server. This can be done through your DNS provider’s control panel, dashboard, or directly via a domain
registrar.

:::note Important note on DNS
Ensure the DNS record for the Alternative Server Certificate is not the same DNS record used for the controller. This can cause issues when validating JWT tokens on the clients. This may show as `key is of invalid type: RSA verify expects *rsa.PublicKey` when enrolling a router.
:::

Ensure you wait for DNS propagation to complete before attempting ACME DNS-based challenge.

This may take a few minutes to a few hours, but you can use tools like [Google Admin Toolbox Dig](https://toolbox.googleapps.com/apps/dig/#TXT/)
Expand Down