Add custom cert troubleshooting page to AutoOps for self-managed docs #4043
+124
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wajihaparvez
commented
Nov 21, 2025
| ::::{tab-item} Hardcode file path | ||
| :sync: hardcode-file-path | ||
|
|
||
| Use this method to specify the path directly. This method is often simpler for fixed or test environments. |
Contributor
Author
Vale Linting ResultsSummary: 3 suggestions found 💡 Suggestions (3)
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds a troubleshooting page to explain how to configure Elastic Agent with a custom SSL certificate. I added a new child page under the troubleshooting section to avoid overloading that page with info.
Closes https://github.com/elastic/opex-product/issues/666.