This page describes troubleshooting issues.
Azure authentication issues
...
If you get an error authenticating with Azure, try the following steps:
...
WARNING: Always be sure to secure the passwords of users created in Alert including the default Alert users (sysadmin, jobmanager, alertuser).
Alert Port issue related symptoms
The following issues are often caused by misconfiguring the server port when deploying Alert using the Helm files.
Issues
Incorrect link to the Alert server in emails
Connection problems with Azure Boards
Connection problems with SAML
Unable to reach the Swagger UI when using the link in the About Page
Solution(s):
Set the exposedNodePort in the Helm deployment files
Alert can not determine the exposed public port that is used so this must be manually configured so that Alert can create correct URLs when referencing itself.Change the forwardHeadersStrategy to "native"
If using a proxy or load balancer, this helps Alert figure out the "public" URL used to access Alert when using the UI.