I have gone through the same question links on the site and still I am unable to get answer for this question. I have registered an API, checked URL for site. Its exact location of file which I am executing. The OAuth is performed and I also get login screen. But when I try logging the error appears. I am still trying to understand what is going wrong.
Related
I have a simple ASP.NET site hosted on Microsoft Azure App Services. For some reason, sometimes when I visit the main url http://mysite.azurewebsites.net i get automatically redirected to a url which doesn't exist (eg http://mysite.azurewebsites.net/eQLRd/). The following error is then returned:
"The resource you are looking for has been removed, had its name changed, or is temporarily unavailable."
I checked the logs but cannot seem to find anything about this. Has anyone experienced this behaviour? I haven't been able to replicate this issue when working locally on IIS.
https://bucherid.azurewebsites.net/
the website can't be accessed normally and ended up with http error 500
But, when i logged in to
bucherid.azurewebsites.n*t/wp-login/
finally i can see the website content normally.
previously the site can be accessed normally and then from yesterday I don't know why but this http 500 happened.
are there solution for this?
from the failed requests traces, this is what appear
image
there's also error messages like this
"There is not enough space on the disk."
Based on the information you have provided, it can not tell what has caused this issue yet. I suggest you enable the Detailed error message functionality through the Azure portal. the screenshot below is to show where to turn on that.
After that done, you should have log files under the directory d:/home/LogFiles/DetailedErrors in your Azure server. You can refer to the link to know how to download them. These files will provide more specific details for the HTTP errors.
Additionally, you can also enable PHP run-time error log by changing the built-in PHP configurations. For more info, please refer to How to debug PHP in MS Azure.
Depending on your SKU, there are limitations in how much disk space you get. See the App Service Pricing page for details.
I have a problem which is similar to this one, but not quite.
We have a solution with two Azure Web Apps, built and deployed by Visual Studio Online. It has been working just fine for a few months, but suddenly all requests end in a 401.72 response:
HTTP Error 401.71 - Unauthorized You do not have permission to view
this directory or page.
Most likely causes: The authenticated user does not have access to a
resource needed to process the request.
Things you can try: Create a tracing rule to track failed requests for
this HTTP status code. For more information about creating a tracing
rule for failed requests, click here.
Detailed Error Information: Module EasyAuthModule_32bit
Notification AuthenticateRequest Handler
ExtensionlessUrlHandler-Integrated-4.0 Error Code 0x80004005
Requested URL https://[appname]:80/ Physical Path
D:\home\site\wwwroot Logon Method Not yet determined Logon User
Not yet determined
More Information: This is the generic Access Denied error returned by
IIS. Typically, there is a substatus code associated with this error
that describes why the server denied the request. Check the IIS Log
file to determine whether a substatus code is associated with this
failure. View more information ยป
Microsoft Knowledge Base Articles:
As far as I can figure out, no relevant configuration changes has been done.
Restarting the Web App and redeploying the solution didn't solve the problem
As it happens, we were due to recreate the environment anyway, and after this was done, the same deployment setup (with updated target) deployed successfully and it's working fine on the new Web App intsance.
Even if we now have a working environment, we'd really like to know what happened, so we can be sure it doesn't happen again.
Can anyone shed any light on this?
You had easy auth turned on. Do you expect it to be turned on? That appears to be causing the issue.
If you don't intend for it to be on, please turn it off via either portal (old|new) by navigating to your Web App and finding it in your settings.
If you do intend for it to be on, you need to check your configuration to make sure you've properly set up AAD. Maybe the App Configuration within AAD has changed?
If neither of those things helps, let me know.
I tried this example for openid in
http://weblogs.asp.net/haithamkhedre/archive/2011/03/13/openid-authentication-with-asp-net-mvc3-dotnetopenauth-and-openid-selector.aspx
I applied the same code in my newly created project , I get this error when i click the google icon in the logon page. I din change any code from the sample project I downloaded from this website, still I get this error .
This sounds just like an MVC controller problem. your Account controller is expected to have an Authenticate action. And since we're seeing a 404, I suggest you investigate what's wrong with your routes.
Keep in mind that this URL should respond to both GET and POST requests.
I am currently having a strange issue that has taken me by surprise, I have not had the issue before and I have no idea why I am getting it now.
I have an asp.net mvc 3 website which has a number of controllers all with actions. It is important to note that this issue is only present with one controller and the problem is with all Actions.
The error I am getting is "HTTP Error 503. The service is unavailable."
However, this error only occurs if I browse to the page using the domain name, for example...
subdomain.example.com/controller
but everything works fine if I browse with the ip address and port number...
xxx.xxx.xxx.xxx:xxxxx/controller
remember all other controllers work fine regardless of the method used to browse.
I have tried looking for answers to this and trying to find any useful logging information but have found nothing of use. Hopefully somebody here will have seen this issue before
Ok I have created a sample mvc project with a Reports controller that works so I don't believe it is a problem with MVC.
I'd reccomend looking at your routes and your web.config and make sure you don't have anything intercepting it there into an httphandler or module. Then I'd look at the IIS instance and check for virtual directories. You pretty much are trying to figure out where exactly it is failing - is it even reaching ASP.Net?
One last option to look into is your company proxy - does going to the URL directly go through the proxy? I know at my company this can happen - so there may be a rule there that is intercepting it.