Comments
Sort by recent activity
I found the problem. While there was no IIS installed on the server, Window's http.sys kernel driver was active and felt responsible for all https requests on the server. In our case this was because we had installed the Windows Admin Center gateway on the same server as SQL Monitor. To solve this I added a second IP to the server. The I limited http.sys to one of the IP addresses. In the Webserver.Kestrel.config I configured the other IP for SQL Monitor. After doing this the services starts and https for the site works.
/ comments
I found the problem. While there was no IIS installed on the server, Window's http.sys kernel driver was active and felt responsible for all https requests on the server. In our case this was becau...
Hi David, C:\Program Files\Red Gate\SQL Monitor\Web\Webserver.Kestrel.config is unchanged and only has the http Port 80 endpoint. C:\ProgramData\Red Gate\SQL Monitor\Webserver.Kestrel.config
has the following content: <?xml version="1.0" encoding="utf-8"?> <configuration> <kestrel> <endpoints> <http> <url>http://*:80</url> </http> <https> <url>https://*:443</url> <certificate> <subject>*.name.com</subject> <store>My</store> <location>LocalMachine</location> <allowInvalid>false</allowInvalid> </certificate> </https> </endpoints> </kestrel> </configuration>
The closing url tag is broken here, but is correct in the config file. I made sure I only have one certificate with the matching subject in LocalMachine\My but but there could be more, it would be better to use the thumbprint to identity the certificate.
/ comments
Hi David,C:\Program Files\Red Gate\SQL Monitor\Web\Webserver.Kestrel.config is unchanged and only has the http Port 80 endpoint.C:\ProgramData\Red Gate\SQL Monitor\Webserver.Kestrel.config
has the ...