Installed the Azure Functions Runtime as per the instructions here:
https://learn.microsoft.com/en-in/azure/azure-functions/functions-runtime-install
Configured all the things including the SQL etc correctly.
After doing that when to the https://localhost and tried to create a new Azure functions App.
When trying to create the Azure Functions App, it fails. I verified the Azure Functions Host Activation Service and the Docker Service are running.
Below is the error when trying to create the functions App from the local box:
For me, this issue was actually caused by WebDAV handler not allowing PUT verb. After I allowed all verbs in IIS for FunctionsAPI, it works like a charm.
You can use F12 in your web browser to help identify the root cause of the issue by going through the steps of creating a new function app.
Please check in the following Windows Event log for any errors on the Functions Management Role:
Microsoft-Windows-FunctionsRuntime/Operational
If you don't see any information there, please follow this instructions to capture a trace for the FunctionsAPI website with status code 400-999:
https://learn.microsoft.com/en-us/iis/troubleshoot/using-failed-request-tracing/troubleshooting-failed-requests-using-tracing-in-iis
Related
I have a web app, ironradio.org, that I've deployed on Azure from VSCode. I've made some updates to the site and am now trying to deploy the newest version. Now when I try to deploy using this button:
I get the error 403 - This web app is stopped in the output window:
I've already deployed several versions of the site using the same method and it's never failed before. Also, the app is definitely not stopped because I can still browse to the site and it shows up.
My best guess as to what's going on is that I associated the App Service with a new resource group since the last deployment, so maybe VSCode isn't recognizing that? Does anyone have any idea what's going on here?
I tried the link given in the error message, but it wasn't much help.
Microsoft foreseen this type of error and how it can affected its customers greatly and this is why the deployment slot is for you.
Firstly, you have to delete the app and reupload again except you set up continuous deployment which work mostly with GitHub and other version control platforms.
Apart from this, I will suggest you check out the deployment slot docs. It’s very simple and easy to use
https://learn.microsoft.com/en-us/azure/app-service/deploy-staging-slots
I am trying to deploy a Blazor Server app using .NET5 to an Azure App Service via Azure DevOps.
The Blazor app runs and works correctly locally. The Azure DevOps pipeline appears to also be building and deploying correctly. If I use the console in the Azure portal I can see that the files I would expect are in the wwwroot folder (which I guess is correct?). In Configuration > General Settings I can see that the App Service is correctly configured for .NET 5. On the network side there are currently no access restrictions. I've also turned off all auth in the app for now just to make sure that wasn't having an impact.
When I try to access the site at https://my-app.azurewebsites.net (not the real url, just an example in case it's relevant) I get a white page with the following text: "You do not have permission to view this directory or page.". When I look in the Diagnostics dump from the Kudu page I can see more detail error pages which say 403.14 - Forbidden and the message "The Web server is configured to not list the contents of this directory.". If I look in App Insights for the times when I try to access it I can see requests with 403 response too (for some reason with url: http://localhost/). Unfortunately this error seems to cover a multitude of errors and so while I've found various sources with similar problems, none of the solutions I've found so far have had any positive impact.
EDIT: So I did some more digging and I think some files might be missing. I tried creating a new Blazor Server app and publishing it manually via Visual Studio. This worked and the only difference I've found from my app is that I have no web.config, hostingstart.html, or static css/js etc (from wwwroot). None of these files are in the output directory when I build for either my app or the test app I created so it looks like they must be getting added separately by something in the VS manual publish process and Azure DevOps publish step isn't doing it. Still not sure what the correct way to fix this is (or even entirely sure if any or all of this stuff is relevant).
Has anyone out there got any idea what I might be missing?
So after working out what was going on here I was going to delete this but I figured possibly someone else will make the same mistake I did and this might help. Basically I'd copied another deployment pipeline for an Azure function app as the basis for the deployment pipeline for this and in that I just did a dotnet build and that's enough. However it seems for this kind of app to get wholesome output you need to run dotnet publish.
I am getting an error message while trying to save application settings which I have added for the Function App.
I had created a function app and have been using it for Azure functions. I had previously successfully added Application setting for a config parameter in the azure function application settings and have been using this in code. This time when I went to add another application settings suddenly it started giving the error "Cannot change the site to the App Service Plan EastUSPlan due to hosting constraints". Nothing has been changed and on previous occassions, I was able to add application settings this way. I have tried following the solutions in below link on using previous or pre URL for azure functions and also to clear cache and try on different browsers.
Azure App Service : can't save application settings
I want to successfully save a new config property in azure function as I was doing previously by adding an entry under Application Settings. How can I save the application settings entry in such a case?
Thank You.
One alternative workaround which worked for me was to delete the function app, create a new function app by the same name, add the application settings in the newly created function app (before deploying any code). It allowed me to save the application settings. Only after this, I deployed the code.
For now to unblock yourself you can use REST API :
Web Apps - Update Application Settings
PUT https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{name}/config/appsettings?api-version=2016-08-01
But Share the screen shot of the error from the portal. Also I may required further information from your side if the issue still persist so that I can get it rectified from portal perspective also.
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.
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