Hi We have an iis server hit exactly the same issue and there are 4 warning 5201 before iis crashed.

Good afternoon

We are building an application with multiple microservices using .Net Core. In the startup code for each service, we fetch the configuration details such as database connection string from the azure key vault. While accessing the key vault, we are passing in the default azure credentials object.
Running the service from visual studio doesn’t cause any issues as I have already added my Azure Account in visual studio. However, there is an issue while trying to run the service by hosting it on IIS as I believe it is trying to access the key vault using IIS app pool identity account.

I have situations where we have web services deployed on customer sites and then encounter issues where clients fail to connect to them for reasons such as the port the service is running on has been blocked/not opened, certificate issues etc.

So I’m getting 500.19 error trying to publish and browse a simple web site to IIS. Here is my Web.config file

I have a web server that is bound to DuckDNS. I’m on that web server trying to navigate to the DuckDNS domain which points to the server I’m on. Is that not possible, if that makes sense.

I have a rewrite that is working and doing what it should besides binding the SSL certificate.
Backend server is for instance http://internalsite:9000/xxxx.
ReWrite takes any http request and rewrites it to https firstly. And then it also looks for any https://app.domain.com/xxxxxx to the backend url.