Open donald93 opened 2 years ago
Update: I tried setting things up with a completely fresh install so a new ASP, App Service, SQL Server, and database. I confirmed the App Service could connect to the SQL server through the vnet using the troubleshooter tool. Got the same errors.
Just a quick note on my findings.
We were getting the same error, when provisioning a new version of SQ to a second deployment slot.
In short, we solved the problem by adding an extra (App Service) configuration parameter sonar.search.port
with a value 0
My rough understanding of why this was happening is that the elastic search will run on port 9001, but (and here is the guess) if you already have a deployment slot running SQ with ES on this port, then a second slot cannot use the same port...
... hth ...
Hello, I'm seeing some issues trying set up a new App Service. There is an existing database I'm attempting to connect to. My SQL Server and App Service are set up on the same v-net and I've tested their connection through the App Service network troubleshooting. Here's the logs I'm seeing: