I've deployed an asp.net core 2.2 webapp to azure linux appservice using VS2019 deployment.
It was successful, but my front page is still Default Azure Page, and none of the controllers are working.
What am I missing?
I get the same result by running devops build/release.
I had to set environment variable WEBSITE_WEBDEPLOY_USE_SCM = false to be able to deploy the app.
I tried looking for Default Documents page on azure to remove the default page, but the azure page for it is gone.
I FTP'ed onto server, my app is there, there is no sign of any default.html.
How do I get my site to actually run and display after deployment success?
You need to check the Startup Command in your Azure App Service configuration settings.
Replace
YourApp.dll
with your applications dll name.
Related
I am currently deploying a C# console app as a Continuous Azure Web Job to an Azure App Service and I am using the Azure Web Jobs SDK 3.X(https://learn.microsoft.com/en-us/azure/app-service/webjobs-sdk-how-to).
The Web Job successfully deploys to the Azure App Service but the status of the Web Job is "Pending Restart". When I check the logs, the error I see is that a configuration value is being read in as NULL. I am setting this value in the App Service's configuration/Application Settings page but it seems my Web Job is unable to read it. Do these settings need to be set during deploy? Or do I need to be setting these configuration values in a different location?
My issue was that my app thought that my environment was Develop and it was looking for the appsettings.Development.json file. Once I corrected that issue, it looks like I am reading in my app settings correctly.
I'm getting a 404 trying to access my azurewebsite.net
My Resource group contains an AppServicePlan, an AppService, SQL Server & SQL Database, a KeyVault & SignalR.
Locally everything works, the AppService is running, AppServicePlan is Ready (1App/0Slots),
Connected Services for SignalR & SQL are configured (in the menu you get when right-clicking WebProject > Publish). KeyVault is configured & accessible. Not sure if these are problem free though, as I keep getting NuGet Errors, stating unable to update NuGet Package.
When I right-click my WebProject & Publish, I get Message Publish has been succeeded. But when I click on the link, I get a 404.
I'm working with two pipelines in AzureDevops
Seeing as official documentation is always lagging behind and showing older interfaces, it has not been much of a help.
I followed https://learn.microsoft.com/en-us/learn/modules/create-release-pipeline/5-deploy-to-appservice this tutorial, did everything stated, but the last step, I didn't get the desired result (an accessible website through azurewebsites.net).
I have a Export template with all connected services configured (I guess generated by azure?) but don't really know what to do with it.
Can anybody pinpoint what I am missing or doing wrong? Or tell me what else I would be needing, apart from the services I mentioned (like Certificates, Active Directory?)
Do I need a gitHub repo next to AzureDevOps Repo & Azure Resources?
Does publishing via VS interfere with my automated pipelinebuilds?
Thanks!
You can try to deploy to Azure App Service in Azure DevOps directly. I used the sample you shared and worked well on my side. Here are my steps:
1.Create the App Service instance in Azure and make sure the default home page is correct.
2.Clone the sample from GitHub to Azure DevOps Repo.
3.Change the deploy stage in the azure-pipelines.yml file on release branch and run pipeline. I removed variable groups and changed the configuration of AzureWebApp task:
4.Browse the page in Azure. I can get the same page as in the tutorial.
I have setup Sitecore 8.2 Update 3 as Azure App Service using Marketplace.
The setup completed and i got urls for cm and cd like
xxxxxx-cd.azurewebsites.net and
xxxxxx-cm.azurewebsites.net
But when I access these URLs I get this screen.
Also xxxxxx-cm.azurewebsites.net/sitecore gives page not found.
Am I missing anything?
According to your screen, the Azure App Service has been created, but there is nothing inside it. Seem like something went wrong and deployment script didn't deploy Sitecore's file to App Service. You can verify it using App Service Editor tool.
The reason why deployment went wrong could be this known issue: https://kb.sitecore.net/articles/755670.
I'm trying to learn to use the azure web app services to deploy a MEAN stack application.
I connected Web App deployments to a git repo and clicked deploy, which it appears to have done successfully.
When I load the webapp url in a browser, its a blank white screen.
How do I troubleshoot this scenario?
You should check if the correct ports are opened.
Good luck!
There are various steps for debugging Node.js web apps on Azure Web Apps here:
https://azure.microsoft.com/en-us/documentation/articles/web-sites-nodejs-debug/
Start off by enabling logging in your IISNode.yml file by setting loggingEnabled: true and devErrorsEnabled: true and seeing what the logs say.
I usually use KUDU to debug Node.js application on Azure Web Site (currently named Web Apps). I doubted this might because the root directory was incorrect, i.e. your website should be started under ~/your_project/app but in Azure it was launched under ~/your_project.
Here is a doc for KUDU. http://blogs.msdn.com/b/benjaminperkins/archive/2014/03/24/using-kudu-with-windows-azure-web-sites.aspx
When I try to publish my site using web deploy to Azure I get an error stating that one of my DLLs in the bin-Folder is still in use and cannot be replaced. So I want to stop the instance, deploy the site and restart it then.
I've found some informations on doing this using msdeploy.exe using the recycleApp-provider. I just can't figure out, how to use it in Azure CD scenarios because I have no control over msdeploy.exe here.