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.
Related
The Issue
I have cloned down an exiting web forms project and when I try to build, I get the error;
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Below this error, the "Detailed Error Information:" section provided a config file path that seems to point to the correct place, accept to the machine of the previous contributor of the solution.
Below is the approach I took to try resolving this issue
Initially, from this, I tried finding out where this incorrect file path is coming from but came across nothing even vaguely relative so I tried googling the error itself.
I came across this question:
How do I resolve "HTTP Error 500.19 - Internal Server Error" on IIS7.0
An answer provided by Bruce mentioned to:
"Check the directory and see if that user has appropriate rights to
it".
In an attempt to do this, I had a quick google and same across the following question: The requested page cannot be accessed because the related configuration data for the page is invalid error
From intermension's answer, I gathered that it was "ApplicationPoolIdentity" that was not assigned the correct permissions so in ettempting to resolve this, I visited the following link. IIS7 Permissions Overview - ApplicationPoolIdentity
I followed Jon Adams' steps successfully as shown here:
This was unsuccessful and I'm unsure of where to go now.
Thank in advance! :)
You can follow there steps:
Check which application pool your website is using
Change it to use ApplicationPoolIdentity if it is not.
Go to your website directory and search for Application Pool Identity user which has format IIS AppPool{AppPool Name} e.g. IIS AppPool\DefaultWebsite and give it read permissions
In IIS Manager select your website in the left pane and then in right pane double click the HandlerMappings icon to ensure that handlers list show up.
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 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.
We have migrated the our websites from one server to another server. all completed successfully but one website has issue of HTTP 400 bad request. I have googled alot but none of the solution works for me then I found this article which told me to set the website under the default website in. when i do that it works for me. but i want to make the previous one working. so please help me how can i do this and please let me know why it is working under default websites.
UPDATE: i have also enabled the log for tracing the error but its not creating a single log.
Thanks in advance.
I have created one test.aspx and my local machine it is working fine. Once I upload the same to server the page is not working. It's showing
500 - Internal server error. There is a problem with the resource you
are looking for, and it cannot be displayed.
It is impossible to help you without getting more info about the IIS configuration on your local machine and the server.
However, here's a quick stab of some things you should look at:
Check if Asp.net is installed on the server.
Make sure your app is targeting the proper .Net version that is on the server.
Check if all the assemblies your code is using are deployed correctly on the IIS server.
Add some exception handling and error logging to your code.
In particular, I'd venture to make a wild guess that your page is using some code that requires the IIS7 integrated pipeline and your server is either running IIS6 or is running IIS7 in classic mode. Though this is a stab in the dark and could turn out to be completely wrong. :-)
500 server errors are as useful as saying 'something broke'. They are the result of literally any exception you code throws plus anything else IIS croaks on. From your error msg, it sounds like an IIS config issue but it could still be your code. attaching a debugger to it would eliminate that possibility.
If you haven't looked at the server event log you can see if it registered anything.
There are a number of things that you can do to try to get a better, more specific exception. One way I try to diagnose them is to connect a remote debugger so I can see what's going on. If you have access to do so, I'd go that route.
You will need admin access to the server to install the Visual Studio remote debugging client (I'm assuming this is a .net app).
Another thing that can help are try/catch blocks and logging to a file or the event log--but have have to change your app most likely to implement that.
You have probably forgotten to upload the associated .dll. Have you tried right clicking on the project and using the publish feature?
If you are using IE, then you also need to turn off the "Show friendly error messages" option in Tools - Options - Advanced settings so that you get more details.
You may also need to change the web.config file so that error message details are shown, see the CustomErrors tag.