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.
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
After sharing my Azure Portal Dashboard yesterday I think I accidentally deleted my default dashboard as it had the same name as the shared one. Now when I log into the Portal I'm getting the following message:
Dashboard not found We could not load the dashboard named 'private/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'. Refresh the portal to
try again.
I have created a new dashboard and can select it from the drop down, but I was wondering if anyone knew a trick to make the new dashboard the default, and prevent this message from appearing.
My issue was that I had bookmarked an old dashboard link. Double-check your bookmarks and make sure that you're using the correct version: https://portal.azure.com/
The reason this was happening for me was permissions. Also make sure you assign the user/user group to the share access section of the dashboard as demonstrated here
Whenever I create a new App on Azure I cannot edit any of the Application Settings as it says they are deleted? What is going on here?
TIA,
Alex
This can happen when you have created an App Service, deleted it, and then made it again with the same name.
Try from a different browser or clear your cache.
I have an Azure WebApp and have activated the "Active Directory Authentication" in the Azure Preview Potal. Let's call it https://mysite.azurewebsites.net (not a real URL) Whis works as expected. However, when we add a deployment slot, we can't get authentication to work properly. When accessing the staged WebApp, e.g. https://mysite-staging.azurewebsites.net (not a real URL), we get redirected to
https://login.microsoftonline.com/<our-directory-guid>/oauth2/authorize?response_type=id_token&redirect_uri=https%3A%2F%2Fmysite-staging.azurewebsites.net/....
But the login portal gives us an error message:
AADSTS50011: The reply address 'https://mysite-staging.azurewebsites.net/<our-appliction-guid>/login' does not match the reply addresses configured for the application: .
The problem is, the WebApp does not show up as an application in our directory, so we can't set up alternate reploy URLs for it.
Is there any way to specify alternate addresses for WebApps, so that Azure AD login will work for deployment slots?
When you create the deployment slot, you need to re-setup the authentication for it, as if it's a new application. (From an app-service perspective, it is.)
The steps are roughly:
In the portal, go to your deployment slot under your app-service.
go to authentication/authorization
Go through all the steps to setup your authentication/authorization the same as for your production app. (Authenticate via AzureAD, Choose the provider, etc.)
Under "Manage App" in the staging environment, go to settings, and add new reply URL's for your staging environment. You should have your regular reply URL, and then the staging version:
https://myapp.azurewebsites.net/signin-oidc
https://myapp-staging.azurewebsites.net/signin-oidc
You should then be able to get in.
One weird thing that happened to me, is this didn't work, then I went into the staging authentication, and turned it off. That made everything work, and it correctly authenticated and didn't let me in if I wasn't signed in.
(I realize I'm posting this answer years after the original question, but after spending the better part of a week figuring it out, and this question repeatedly came up on searched, I wanted to document what I ended up doing in case someone else has a problem.)
I sure this will not fix the deployment slot is still pointing to live app but this fix this error as it is very silly.
AADSTS50011: The reply address 'https://mysite-staging.azurewebsites.net//login' does not match the reply addresses configured for the application: .
When you configure your URL under the application settings in Azure AD, you forgot… a trailing slash! That’s it! Can you believe that?
In other words, change this:
http://yoururlforyourapp
to this:
http://yoururlforyourapp/
Done! You’re welcome.
From http://www.matvelloso.com/2015/01/30/troubleshooting-common-azure-active-directory-errors/
Unfortunately it looks like you ran into some bugs in that version of the preview portal.
The Reply URL issue is likely because you created the staging slot after you configured auth on the production slot. In that version, we cloned the auth settings so your staging slot ended up pointing to the existing AAD application without adding the new Reply URL. This issue has been fixed by not auto-cloning auth settings when a new slot is created.
In any case, you should be able to find your application in the AAD management portal. If you're not able to see it, it could be because you need to change the "Show" dropdown filter from "Applications my company uses" to "Applications my company owns". Locating it and adding the staging Reply URL would have also worked around the issue mentioned above.
The error message you saw when trying to re-configure auth on your staging slot was likely another bug in the management portal if you were only seeing it on that staging slot.
The Authentication / Authorization blade has been radically updated since your question was asked, and all of these issues should be fixed now. Sorry for the inconvenience. I hope you were able to make progress in spite of these issues.
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.