Suddenly blanc page and bad gateway 500 response trough API about ipam HOT 10 CLOSED

Good morning @Maurice-AxiansNL, from what I'm understanding immediately after you deployed the Azure IPAM solution using our deployment script, you are attempting to access the UI in your browser, and you're receiving a 500 error, is that correct?

If that is indeed correct, the first thing I would do is ask if you saw any error messages during the deployment. There arealso logs which are generates in the /logs folder after the deploy.ps1script runs.

The second thing I would check is the Log Stream which can be found as per the below picture:

Also, you can download the logs, and we're more than happy to help you review them and look for any obvious issues:

You can send them to me at Matthew.Garrett@microsoft so you don't have to post them here.

I'm sure we'll get to the bottom of whatever is going on together!

from ipam.

Apologies for not explaining it quite clearly.

The Azure IPAM has been running for several months and is now suddenly giving a blanc page and is not approachable via the API (Bad gateway error 500)

Thanks for the suggestions but those are about rolling out an IPAM webapp.

I use the API in other deployments to see what subnet is available for deploying a virtual network, and then I get the bad gateway error.

from ipam.

Thanks for clarifying @Maurice-AxiansNL. Are you running Azure IPAM as a Function App then?

from ipam.

That is correct.

App service with cosmosdb

from ipam.

Got it @Maurice-AxiansNL, in that case my above recommendations around checking the Log Stream for any errors, and possibly downloading the runtime logs to see why the Function App isn't starting are the same. There has to be something that caused this issue, it could be an Azure Policy, or perhaps a permissions change.

The logs should tell us more and can be found here:

Function App -> Deployment Center -> Logs (tab)

From there we can find out what is causing the Function App to fail and return a 500 error.

from ipam.

I'm sorry, I think I'm a bit confusing with the term Function app in this case.

I deployed the Azure IPAM type "App Service"

I attached a screenshot

from ipam.

Gotcha @Maurice-AxiansNL! When you deployed this, did you use the deploy.ps1 script that we provided, or did you deploy the Azure IPAM solution manually into Azure App Services?

If you did use the deploy.ps1 script, then by default, it deploys the Web UI and Engine containers into an Azure App Service. In that case, my advice from above still stands true that we should examine the App Service logs for a cause of the failure.

I'm more than happy to meet with you 1:1 and personally help you through this issue. If you send me an email at [email protected] and provide your time zone, I'll schedule something that is convenient for you, and together we'll get to the bottom of what is going on.

from ipam.

Thanks for offering your help. I am happy to take it up. Next 3 days I am abroad for work so let's plan something for next week.

Time zone is Amsterdam GMT+2

from ipam.

Sounds great @Maurice-AxiansNL ! Please send me an email at [email protected] so I can create a meeting invite for us next week. Talk to you soon.

from ipam.

After working with @Maurice-AxiansNL, we found the issue was that the Managed Identity was somehow missing, causing authentication issues. After a redeploy, everything is back up and running!

Closing this issue, thanks so much!

from ipam.