Azure App Service - Fail after enabling Authentication - azure

We have an app which get data from Azure DevOps Services using RestAPI with token. Without authentication it is working fine.
After enabling authentication get errors 500/431 without any explanation. Authentication set for single tenant and with new application registration.
THE ONLY WAY TO GET AROUND THIS PROBLEM WAS TO USE A CONTAINER BUILD FROM AZURE - USE VS CODE TO PUBLISH & BUILD - USING A CUSTOM CONTAINER FAILED ALWAYS
I tried the following without success:
Setting - WEBSITE_AUTH_DISABLE_IDENTITY_FLOW - Azure Web App + Node.js + Azure AD = Error 431
Added specific permission for - Azure DevOps Services on the Identity provider tab.
Any advice would be most appreciated

The error 500 may occur if you have enabled App Insights monitoring on client-side.
Please check whether you have enabled that option or not like below:
APPINSIGHTS_JAVASCRIPT_ENABLE = true
If it is enabled, disable it by assigning false parameter as suggested in this SO Thread by L. González.
These 500/431 errors occur due to many reasons and to know the exact issue behind the error, try enabling diagnostic logging.
To know more about diagnostic logging please refer this MsDoc
Try restarting the App Service and raise Azure Support Ticket if still the issue persists.
Reference:
how do I fix the azure web app error 500? - Stack Overflow

Related

Azure Devops release pipeline unauthorized for some projects

I am trying to release multiple projects in 1 solution using Azure Release pipeline
They are all connected to the same Azure Subscription, but some do deploy to the given app service while others give an unauthorized error.
Ive looked into it and i read that adding website_webdeploy_use_scm to the app service should help the Unauthorized error, but this didnt help for me.
What else could i look at? I connect through Azure Devops so i just selected the subscription from the list it automatically gathers from Azure because im logged in using the same logins as i use for Azure Portal
the full error is:
Connected to the remote computer ("xxxx.azurewebsites.windows.net") using the Web Management Service, but could not authorize. Make sure that you are using the correct user name and password, that the site you are connecting to exists, and that the credentials represent a user who has permissions to access the site. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_USER_UNAUTHORIZED.
Error: The remote server returned an error: (401) Unauthorized.
according to the error I'd suggest you check service principal permissions. it probably lacks the permissions required to manage those webapps.
So after refresh publishing profile in Azure Portal and trying it again it fixed itself so im not sure if that caused it or not but it worked!
another fix is to delete the slot and make it again

Send email when an application error occurs in Azure web app

Use case is as soon as an error occurs in application, support team should receive a notification.
Looking for an out of box solution in Azure.
Current system configured for Diagnostic logs with below settings:
Application Logging (Blob) - On
Logging Level - Error
Retention period - X days.
As far as I know, azure app service has Alerts feature. By using this feature, you could define which metrics will send the email.
About how to use it, you could refer to below images:
1.Find the alters in your from azure portal app service.
2.Click add alerts
3.Define alert rule

HTTP 500 error using Azure Easytables with Node.js backend

Having created a mobile app in Azure using EasyTables with a Node.js backend, I get an HTTP 500 error trying to post a new item.
Log in to the Azure console and in the project backend run:
npm i sqlite3
That fixes it.
(Answering my own question because I couldn't find this anywhere on StackOverflow. Props to #benjamintam from Readify for the solution)
If your mobile app application is running on Azure cloud not on locally, the issue is a little odd, as the sqlite 3 supporting is for Azure Mobile Apps development on local. You can refer to https://azure.github.io/azure-mobile-apps-node/module-azure-mobile-apps_src_configuration_DataProviders.html for the detailed description.
If your issue occurs on your Mobile Apps running on Azure, please double check whether you have completed the project's initialization. You can refer to https://azure.microsoft.com/en-us/documentation/articles/app-service-mobile-android-get-started/#configure-the-server-project for the steps.
Meanwhile, you can manually add the data connection to Azure SQL in the Azure portal,
And if successfully, you can find the configuration MS_TableConnectionString in Application settings in your Mobile Apps.
Any further concern, please feel free to let me know.

How to resolve error 500 on Azure web app?

What I have:
VS2015U2
ASP.NET 5 MVC 6 website
Deployed to Azure Web App
The site works locally
When I deploy to Azure I get internal server error (500)
I'm unable to Attach a debugger since they messed up something with the latest versions (tried manually too https://azure.microsoft.com/en-us/blog/introduction-to-remote-debugging-on-azure-web-sites/)
I have app.UseDeveloperExceptionPage(); but I guess the site is failing during configuration so it doesn't display any other information.
So how to resolve this? I need to see the .net exception but I have no idea how to do that.
Try adding Application Insights to the app. You should see errors on startup of your application.
I would also take a look at your startup code to see if you are writing to disk anywhere during configuration or app.start. This might be the case if you are using AAD in any capacity.
You can also hit up the KUDU console by targetting https://sitename.scm.azurewebsites.net . You will be able to navigate in the debugging console to see the RAW logs from IIS. That might shed some light into the situation. See KUDU for more info.
I solved this problem like show below.HTTP 500 error interested about that is not allowed to access the server.Go to azure portal address and choose your database.Press"Set server firewall " and Allow Azure services and resources to access this server choose "Yes" save that page and refresh your service.Than you can see your data
Use the KUDU console at https://sitename.scm.azurewebsites.net
Go to web.config file and check if the process path is correct.
I used the Azure Log Stream to help figure out what was going on. As Karishma Tiwari - MSFT said, the issue ended up being my web.config file (which was built for .NET 3.5 and not 4.7)
Here's the tutorial to set up Log Streaming: https://blogs.msdn.microsoft.com/azureossds/2016/09/28/how-to-identifyreview-errors-on-php-applications-in-azure-web-apps-using-log-stream-service/
My particular app's solution was to update my Azure App Service to use .NET 3.5, in its Application Settings, like so:
For me it worked after I turned "Allow Azure services and resources to access this server
" to Yes
I got this error even though I had enabled Application Logging (Filesystem), Detailed error messages and Failed request tracing in App Service logs
This page isn’t working
mysite.azurewebsites.net is currently unable
to handle this request.
HTTP ERROR 500
However by navigating to Log stream and selecting Application Logs I could see a detailed error message:
I know this question has already been answered but here is a recent view of the Azure Portal where I found a solution to this problem

Azure Preview Portal reporting error configuring storage

I'm trying to use the Azure Preview. When I try to configure my storage account I receive the following error:
Monitoring Failure: The server encountered an error while retrieving the metric selection. Retry the operation.
This has been occurring since yesterday. I see the error on both ie10 and Chrome.
I tried to create a new storage account and see the same error.
When I run the app the application fails to connect to the storage account with the following error (from node.js):
Config: C:\DWASFiles\Sites\mychild\VirtualDirectory0\site\wwwroot
Creating Blob Service profile
Creating Blob ...
Fail.{"code":"EACCES","errno":"EACCES","syscall":"connect"}
As you're not the only one seeing this problem (myself included), I don't think this is anything to do with what you've done. I suspect that this is a general problem that Microsoft are having. I'd recommend logging a support call with the Azure support team if you need this problem resolved.

Resources