i just moved from my old host to Godaddy, which seems to be a worst web host with no support.
i moved my asp website (written in classic asp) to the new godaddy windows hosting. but when i run the site i get the below error
HTTP/1.1 New Application Failed
this site worked perfectly with my previous host.
below is what i have in my web.config file
<?xml version="1.0"?>
<configuration>
<system.webServer>
<httpErrors errorMode="Detailed" />
<asp scriptErrorSentToBrowser="true"/>
</system.webServer>
<system.web>
<customErrors mode="Off"/>
<compilation debug="true"/>
</system.web>
</configuration>
can someone tell me why am i getting that error and how can i fix it?
any help will be appreciated.
I had the same issue moving a website from one hosting account (classic windows) to another (plesk), both on GoDaddy. After much headache troubleshooting, I managed to fix it by removing the whole <asp> tag from the web.config file;
<!-- <asp scriptErrorSentToBrowser="true"/> -->
IIS 8 (only option in plesk) does not support this option altogether and configuring detailed error messaging is done differently using:
<httpErrors errorMode="Detailed" existingResponse="PassThrough" />
You can find further instructions on this GoDaddy support page
I just encountered the same error this morning after renaming some Websites in IIS. A restart of IIS got my sites up and running again in seconds. Presumably the .config files are read on startup and 'likely' the cause of this error for me.
Related
Before opening this ticket, I read dozens of other questions here on StackOverflow, youtube etc, but all suggestions that I found not solve my problem.
What I intend is to host a .net core 6 web api on windows server 2016 using IIS.
I've managed to host a client site (Angular) without problems, but the API always gives me a 500.19 error:
I have configured port 5041, but I have already tried with others, such as 80, 8080 without success.
I already have installed the Asp.Net Core Runtime and Hosting Bundle:
This is my web.config:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<location path="." inheritInChildApplications="false">
<system.webServer>
<handlers>
<add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" />
</handlers>
<aspNetCore processPath="dotnet" arguments=".\EvoStats.API.dll" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" hostingModel="inprocess" />
</system.webServer>
</location>
</configuration>
I saw someone else who solved your problem by putting the full path of dotnet, I did that too, but it didn't solve in my case:
<aspNetCore processPath="C:\Program Files\dotnet\dotnet.exe" ...
I also configured the Application Pool to not manage the code using .net CLR
I don't know what I can do more :(
I appreciate your help.
I already managed to solve it.
The problem was with the access permissions to the wwwroot folder.
Something strange, because I have a site (Angular) working on this folder, before giving Full Control to the user IIS_IUSRS.
Hope this solution helps others.
I've been trawling through related questions for several weeks looking for an answer, and none of the previous solutions are working for me. I know this is a common (and vague) problem.
I'm hosting a web app in IIS on Windows Server 2016. The application is built in VS2019 and runs fine in IIS Express. The default web site hosted by IIS is working, but when I add a second site pointing to my published application, I'm getting a 500 error.
However, when I check the IIS logs, all I see are 200 responses, which is odd. There is also no error in Event Viewer to give me more details. The best lead I have found so far is that the problem may be caused by the web.config file.
The generated XML is this:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<location path="." inheritInChildApplications="false">
<system.webServer>
<validation validateIntegratedModeConfiguration="false" />
<handlers>
<add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified" />
</handlers>
<aspNetCore processPath="dotnet" arguments=".\MalechusDotCom.dll" stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout" />
</system.webServer>
</location>
</configuration>
<!--ProjectGuid: bc59438b-f089-4db2-98d6-cc60312db351-->
Is there anything else I can check to try to isolate the issue?
I got similar problem . setting dotnet exe complete path resolved my problem. Try this one:
<aspNetCore processPath="C:\Program Files\dotnet\dotnet.exe" arguments=".\MalechusDotCom.dll" stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout" />
Update above line of code with complete processPath value. Make sure C:\Program Files\dotnet\dotnet.exe path exist in your system or find equivalent path. this vary system to system.
I am adding a web.config file to my classic ASP project.
Here is the Web.config file,
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system.webServer>
<asp enableChunkedEncoding="false" />
</system.webServer>
</configuration>
When I run on my localhost, I get this error,
HTTP/1.1 New Application Failed
I have added in a location path pointing to "Default Web Site" that seems to load the page, but not what I want to do, since this is not just for my local machine.
I'm not sure where to go from here to get the page to load.
I have managed to publish an asp.net-5 app on a server with IIS, but now I get a 500 Internal Server Error. How can I get more information on what's wrong ?
In the wwwroot/web.config, I have added:
<system.web>
<customErrors mode="Off"/>
<compilation debug="true" />
</system.web>
<system.webServer>
<validation validateIntegratedModeConfiguration="false" />
<httpErrors errorMode="Detailed" />
<asp scriptErrorSentToBrowser="true"/>
</system.webServer>
I have also temporarily changed the Startup to show errors like in development by commenting out the if (env.IsEnvironment("Development")) around the
app.UseBrowserLink();
app.UseErrorPage(ErrorPageOptions.ShowAll);
app.UseDatabaseErrorPage(DatabaseErrorPageOptions.ShowAll);
I also set the Configuration to 'Debug' in the publish wizard, but I still get the error 500 page without further information.
How can I make it display the stack trace and all other debug informations ?
(I also tried to look for the error in the Windows logs but couldn't find anything)
I could get the trace by viewing the page from within the server.
So it actually behaves like when setting the <customErrors mode="RemoteOnly"> in asp.net < 5. I still wonder how to allow remote hosts to view trace in asp.net-5...
When uploading a 42MB file through my ASP.NET Web Application, an issue is occuring where the following errors appear depending on the browser being used:
Google Chrome:
Oops! This link appears to be broken
FireFox:
XML Parsing Error: no element found
Internet Explorer
The webpage cannot be found
I don't believe this is an issue with file size restrictions as I have the following in my web.config:
<httpRuntime maxRequestLength="409600" executionTimeout="9000" />
This is working fine on our development server (IIS6), but not on the live server (IIS7)
Why is this and how can I prevent this from happening?
IIS7 doesn't seem to read:
<httpRuntime maxRequestLength="409600" />
The IIS7 alternative seems to be:
<system.webServer>
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="209715200"></requestLimits>
</requestFiltering>
</security>
</system.webServer>