I just updated all the Microsoft packages on my ASP.NET core app to the latest 2.1 versions (as well as updated the SDK to 2.1.4 on my CentOS server) and pushed the code to the server. I rebuilt the code server-side and deployed it to the web root. I can't get the server to respond now unless it runs as root. When attempting to connect through the Apache proxy, I get a 502 Proxy Error and when I attempt to connect directly to the SSL port the Kestrel server is listening on, I get ERR_CONNECTION_CLOSED in Chrome.
If I run the site manually as root user (dotnet WebsiteMainDll.dll) it works fine. If I run it manually as the user it should run as (sudo -u siteuser dotnet WebsiteMainDll.dll), it doesn't work.
There are no errors shown in the console. It just shows Now listening on https://0.0.0.0:44313 and is silent from that point on.
I have another instance of the site running on the pre-updated codebase and it works fine running as site user. This instance worked fine pre-update. What's going on?
dotnetand see if you can get more info.unknown option --verbositywhen attempting to run. I trieddotnet --verbosity diag WebsiteMainDll.dllanddotnet --verbosity=diag WebsiteMainDll.dll. I see the option in the help output, but it won't take it.dotnet -d run WebsiteMainDll.dll?.csprojinstead of the.dlland found that NuGet couldn't restore the packages due to an SSL error: github.com/dotnet/cli/issues/9391