CODEWITHSUNDEEP
azureazure-devopsweb-deployment
BHANG
BHANG

Reputation: 374

Azure Resources WebApp deployed but not accessible from url

I'm trying to access my app, hosted on azure. I've a finished c# solution. When I commit changes to Azure DevOps it triggers a (working & successful) build-pipeline. It runs tests, publishes an artifact & testresults.

enter image description here

In my ServicePlan status is Ready and I see Data Exchanges on DataIn & DataOut graphs.

enter image description here

The Deployment Center: Deployment Center

enter image description here

Bu when I click the https://mywebsite.azurewebsites.net, No webpage was found for the web address.

I have Some basic Azure DevOps expierence, but this Azure Portal is something else :)

My basic questions would be: Why is it not working?

Do I need a second pipeline, only for release? Or can I recycle the build pipeline?

Do I need some kind of deployment slots? Before I select a not-free slot, I want to know if this is necessary

What else could I be missing? (My Azure resources include a sql-server, a sql-db, the actual appservice & a app service plan)

Thanks!

Upvotes: 0

Views: 5383

Answers (1)

Vito Liu
Vito Liu

Reputation: 8298

If you deploy web app to Azure and login https://<app-name>.azurewebsites.net, then the page still shows Microsoft page instead you owner page. You need check the default document, please ensure that the default page is listed in here.

Steps: login azure portal->App Service->configuration->Default documents

In Azure Web Apps, the default document is the web page that is displayed at the root URL for a website. The first matching file in the list is used. Refer File structure on azure to know more about the files and directories on Azure Web App.

Update1

When I go to the azurewebsites.net url I get a 404: No webpage was found for the web address.

Check this doc:

If you receive an HTTP 404 (Not Found) error when you browse to the URL of your custom domain, verify that your domain resolves to your app's IP address by using WhatsmyDNS.net. If not, it might be because of one of the following reasons:

  • The custom domain configured is missing an A record or a CNAME record.

  • The browser client has cached the old IP address of your domain. Clear the cache, and test DNS resolution again. On a Windows machine, you clear the cache with ipconfig /flushdns.

Update2

the URL in my appservice is Azure-generated right?

Yes, then app service url is generated by Azure.

With making a new app service and going to the URL I do get a message app service is up and running.Time to take the next step and deploy your code.

And now, we should get this page, we need create new service connection and re-configure build and release pipeline and deploy your app.

enter image description here

Note: We need use the same user account and AAD domain to do this.

Upvotes: 2

Related Questions