Update documentation for Let's Encrypt errors
requested to merge 30146-let-s-encrypt-integration-doesn-t-scale-and-does-not-give-any-feedback-to-user-on-errors-3 into master
What does this MR do?
As part of #30146 (closed) this MR:
- removes old troubleshooting recommendation since it was fixed 8 months ago: gitlab-foss!30995 (diffs)
- add retrying process to docs
I tried to remember all the cases I've seen. 90% of the time the error will be generated by DNS propagation or long pages configuration reloading.
In these cases just pressing Retry button is enough. Other cases I've seen were related to not properly configured DNS(having AAAA records or CAA policy)
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Edited by Vladimir Shushlin