Comments
2 comments
-
Hi there,I am glad to hear that you found the solution to your issue."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."Sincerely,David KimProduct Support Engineer
-
After a gazillion trials, I finally got it working. I had exactly the same problem as indiwa. My solution though, was to use a different port for https.
Here is my Webserver.Kestrel.config located under C:\ProgramData\Red Gate\SQL Monitor
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<kestrel>
<endpoints>
<http>
<url>http://*:8080</url>
</http>
<https>
<url>https://*:30443</url>
<certificate>
<path>C:/ProgramData/Red Gate/SQL Monitor/SQLMonCert.pfx</path>
<password>B4cC@wJ=Q3hr*y+9Hud3*xDco</password>
</certificate>
</https>
</endpoints>
</kestrel>
</configuration>
A couple of notes:
Even though I had changed the port already, [SQL Monitor Web Service] kept crashing after five or ten seconds of a start, until I stopped it myself after a restart. After that, it didn't crash again. Why? No idea, but I guess the crashing was hindering some stuff to be written down somewhere.
Also, it would be nice with "real " examples in the documentation for the Webserver.Kestrel.config. In my case, I got confused with the / and the [ ]cheers, Javier
p.s: fake password in case you are wondering
Add comment
Please sign in to leave a comment.
C:\Program Files\Red Gate\SQL Monitor\Web\RedGate.SqlMonitor.UI.Website.logging.jsonc
BTW The PowerShell script on the documentation page linked below does not work for non-English servers.