The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.
This error comes on a newly deployed website on azure.
http://newdemo1.azurewebsites.net/Calculator
Works for me when I browse to http://newdemo1.azurewebsites.net/Calculator
Where exactly are you seeing this error? Have you made changes since logging this question ?
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 deleted azure webapp through azure portal. It seems it is deleted because when I run:
az webapp list
my deleted web app is not showing. But I can still access it oldwebapp.azurewebsites.net.
And it's showing in google search as well. Is there any cache I need to clear or other places I can check to fully remove it?
Also checked other places if there is any connection to this old web app, but didn't find any or don't know where to look.
I have also encountered a similar situation and found that the resource has been deleted after checking in portal. Sometimes visit it using InPrivate window also succeed.
It seems that this is a bug, and you don't need to care about it, or if necessary, you can also submit a bug in a GitHub Issue.
If you need to use the url again by creating a new webapp with the same name, try deploy a new project and access it, it should be refresh to the new one.
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 own a domain name and am trying to map it to an Azure Web App that I successfully created.
I created an A record, C record, and Txt (as required by Azure) on Godaddy and configured Custom Domains in Azure (as pictured below). The message I'm getting back now is:
The resource you are looking for has been removed, had its name
changed, or is temporarily unavailable.
Any suggestions?
By looking in https://www.digwebinterface.com/
https://www.digwebinterface.com/?hostnames=dnnappserver.scm.azurewebsites.net%0D%0Asmarttapp.com%0D%0Awww.smarttapp.com&type=&ns=resolver&useresolver=8.8.4.4&nameservers=
Everything seems perfect and even mapping is correct. Even site are working by custom domain :)
I'm trying create a web app on Azure, but no matter what i name my URL, it always warn me that
Could not validate web app name
What could have cause this problem? Any ideas that could fix this problem? thank you. I'm thinking about deploying my app on Winhost if the issue won't be solved (please hear me out, I've tried a lot of names here but it still says the samething).
It is the preview (i.e. BETA) portal. I have experienced lots of weirdness like this. Try the old portal - manage.windowsazure.com
I hit this after deleting an API App to recreate on a new App Service Plan with the same name.
(In Chrome) I cleared storage for the site https://portal.azure.com, refreshed the page (F5), and the problem was immediately solved.