500 error after starting docker container instance

James Baron 0

I'm getting a 500 error after starting a Docker container. I can see that the website is running from the command prompt into the running Docker using CMD.

C:\inetpub\wwwroot>\Windows\System32\inetsrv\appcmd.exe list site

SITE "Default Web Site" (id:1,bindings:http/*:80:,state:Started)

I added to my Web.config

<httpErrors errorMode="Detailed" />

If I stop the website, the 500 error goes away and the connection just hangs endlessly.

I can't load static resources either. So like http://myip/someimage.png does not load in my browser. Just a 500 error.

Anyone know how I can figure out what the error is?

Sam Wu-MSFT 7,531 Reputation points Microsoft Vendor

2023-10-17T03:06:01.1666667+00:00

@James Baron

You need more information to analyze your problem, try using failed request tracing to see details about 500 error, this will generate detail log file, which will help you to identify the problem.

James Baron 0

@Sam Wu-MSFT

Thank you for your kind response.

I followed the instructions here: https://video2.skills-academy.com/en-us/iis/configuration/system.applicationhost/sites/site/tracefailedrequestslogging#appcmdexe

and now I have in my applicationHost.config:

<system.applicationHost>
<sites>
	<site name="Default Web Site" id="1">
		<application path="/">
			<virtualDirectory path="/" physicalPath="%SystemDrive%\inetpub\wwwroot" />
		</application>
		<bindings>
			<binding protocol="http" bindingInformation="*:80:" /> 
		</bindings>
		<traceFailedRequestsLogging enabled="true" directory="%SystemDrive%\inetpub\logs\FailedReqLogFiles" />
	</site>
	<siteDefaults>
		<logFile logFormat="W3C" directory="%SystemDrive%\inetpub\logs\LogFiles" />
		<traceFailedRequestsLogging directory="%SystemDrive%\inetpub\logs\FailedReqLogFiles" />
	</siteDefaults>
	<applicationDefaults applicationPool="DefaultAppPool" />
	<virtualDirectoryDefaults allowSubDirConfig="true" /> 
</sites>

When I visit the URL, I get my 500 error. In the logs I get an entry:

2023-10-17 15:46:35 192.168.0.88 GET / - 80 - 10.92.0.6 Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/118.0.0.
0+Safari/537.36 - 500 19 13 12

but the \inetpub\logs\FailedReqLogFiles directory does not get created. I created the directory and no log files were created.

kobulloc-MSFT 26,346 Reputation points Microsoft Employee

2023-10-20T01:26:43.73+00:00

Hello, @James Baron !

If an answer has been helpful, please consider accepting the answer to help increase visibility of this question for other members of the Microsoft Q&A community. If not, please let us know what is still needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!

1 answer

Sam Wu-MSFT 7,531 Reputation points Microsoft Vendor

2023-10-18T03:20:45.76+00:00

@James Baron

First, please make sure that you have installed Failed Request Tracing, and make sure that Tracing is enabled in the Internet Information Services->World Wide Web Services->Health and Diagnostics.

If you still can't succeed, please run Process Monitor to see if IIS has the appropriate permissions to write the FRT logs.

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.
James Baron 0 Reputation points

2023-10-20T17:48:12.3066667+00:00

@Sam Wu-MSFT , I have run

Add-WindowsFeature Web-Http-Tracing

I also ran

$logacl = Get-Acl -Path "C:\inetpub\logs\LogFiles\" Set-Acl -path "C:\inetpub\logs\FailedReqLogFiles\" -AclObject $logacl

I now have

PS C:\inetpub\logs> Get-Acl .\FailedReqLogFiles\ Directory: C:\inetpub\logs Path Owner Access ---- ----- ------ FailedReqLogFiles BUILTIN\Administrators NT SERVICE\TrustedInstaller Allow FullControl...

I also added to my Web.config

<tracing> <traceFailedRequests> <add path="*"> <traceAreas> <add provider="ASP" verbosity="Verbose" /> <add provider="ASPNET" areas="Infrastructure,Module,Page,AppServices" verbosity="Verbose" /> <add provider="ISAPI Extension" verbosity="Verbose" /> <add provider="WWW Server" areas="Authentication,Security,Filter,StaticFile,CGI,Compression,Cache,RequestNotifications,Module,FastCGI,WebSocket" verbosity="Verbose" /> </traceAreas> <failureDefinitions statusCodes="200-399,500" /> </add> </traceFailedRequests> </tracing>

Still no new files in the C:\inetpub\logs\FailedReqLogFiles directory, although that directory now gets created without my having to.

Sam Wu-MSFT 7,531 Reputation points Microsoft Vendor

2023-10-23T09:14:43.2933333+00:00

@James Baron

You can also try to use failed request tracking in the iis feature.

Note: Please enable failed request tracking before using it.

James Baron 0 Reputation points

2023-10-23T14:12:19.19+00:00

I can't do it like this because this is Docker, but I did it in a GUI on another server, and then copied out the result into the Web.config. That's what I posted the last time.

MotoX80 34,421 Reputation points

2023-10-23T14:34:23.2466667+00:00

See if there is anything helpful in the HTTP error logs, C:\Windows\System32\LogFiles\HTTPERR\

Also try using C:\Windows\System32\curl.exe or Powershell's Invoke-webrequest locally and see if there is more error detail.

MotoX80 34,421 Reputation points

2023-10-23T17:08:29.0466667+00:00

Something else to try... In the system.webServer section of my web.config, I have this set.

<httpErrors errorMode="Detailed" />
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

500 error after starting docker container instance

1 answer

Your answer