Versions Used:
SonarQube: 10.1.0 (Developer Edition)
Deployment method: Azure Container Instances
Deployment Overview:
SonarQube is deployed as an Azure Container Instance.
It is connected to an Azure Application Gateway which is meant to manage the traffic.
Issue Encountered:
Currently facing a 502 Bad Gateway error when trying to access SonarQube through the Application Gateway (Microsoft-Azure-Application-Gateway/v2).
Attempts to Resolve:
Verified network settings and configurations in the Azure portal.
Ensured that all resources are properly linked (IP addresses, subnets, and gateways).
Reviewed the application logs (available through Azure’s diagnostics) but did not find specific indicators pointing to the cause of the 502 error.
Questions
- Are there specific configurations within the Application Gateway that could be incorrectly set leading to this issue?
- Could there be a misconfiguration in how the container is set up in Azure that would lead to a 502 error?