Skip to:
Summary: ASP.NET Core app seems to work fine locally, but when deployed to Azure, I'm getting "ConfigHandler has already been started" exception message.
Repro:
Deploy this project to Azure Web Service - https://github.com/mgroves/MattsTwitchBot
manually is fine
debug mode
I've pasted what I think are the relevant pieces of code below and logs
if nothing jumps out as a problem, let me know and I will create a more minimal example
Open website
Excepted:
Website to work without exception
Actual:
404 error from website, exception in log (attached)
Notes:
This seems to work just fine locally. The problem only seems to happen when deployed to Azure Web Service. Maybe a race condition?
Code snippets:
Jira formatting is horrible, so I attached it too.
Resolving this, please reopen if you feel it is not resolved.
I believe this is fixed; need to verify.
it looks like the INamedBucketParameter issue has regressed, so I'm unable to compile with 3.0.5 from nuget
I will try to get around and check this week.
is this fixed by NCBC-2638? You can validate against 3.0.5 DI in NuGet.
Summary: ASP.NET Core app seems to work fine locally, but when deployed to Azure, I'm getting "ConfigHandler has already been started" exception message.
Repro:
Deploy this project to Azure Web Service - https://github.com/mgroves/MattsTwitchBot
manually is fine
debug mode
I've pasted what I think are the relevant pieces of code below and logs
if nothing jumps out as a problem, let me know and I will create a more minimal example
Open website
Excepted:
Website to work without exception
Actual:
404 error from website, exception in log (attached)
Notes:
This seems to work just fine locally. The problem only seems to happen when deployed to Azure Web Service. Maybe a race condition?
Code snippets:
Jira formatting is horrible, so I attached it too.