I have a big problem with the Asp.Net Core 2 Server:

As soon as a Web page generates an error on the productive system, it kills the entire IIS server as an application.

This means that an Asp.Net Core application can crash the web server with every error. The system will not start up by itself.

Blame is probably the internal Kestrel web server, which with Asp.Net Core for central use. This Kestrel web server generates only a single task in the Windows server.

And this hangs up.

In the previous Asp.Net Framework with Webforms and Asp MVC applications, the IIS loom always ran on several tasks and has fully exploited the web server computers with all kernels.

So multitasking, multiserver ...

502 - Web server received an invalid response as gateway or proxy server.

Problem with the page you are looking for. It can not be displayed. When contacting the upstream content server, the web server (as a gateway or proxy) received an invalid response from the content server.