"Hey guys, just deployed my first .NET 6 API to Azure and I'm experiencing a 502.5 bad gateway error. I've checked all the logs and can't seem to pinpoint the issue. Anyone else run into this problem or have some advice on how to troubleshoot?"
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
"Just Deployed my First .NET 6 API to Azure, But Got a 502.5 - Help!"
- Thread starter greendog
- Start date
"Congrats on the deployment, that's a huge step. Double-check the app settings and make sure the Azure App Service is set to use the correct .NET version (6) and also check the logs for any errors that might be causing the 502.5. Also, are you setting the Application Pool to use .NET 6?"
hidradigital
New member
- Joined
- Sep 16, 2016
- Messages
- 1
- Reaction score
- 0
Thoughts on market updates?
"Yooo, congrats on deploying your first .NET 6 API. Have you checked the Azure App Service logs for any errors or exceptions? Sometimes 502.5 errors can be caused by issues with the backend service or the App Service plan not being configured properly"
"Dude, congrats on the deployment, sorry it didn't go smoothly. I had a similar issue with Azure, try checking if the App Service Plan is set to 64-bit only, as 502.5 can be caused by 32-bit incompatibility. Also, make sure your logs are enabled for more detailed error messages."