How can we help you today? How can we help you today?
jhislander
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&gt;       </http>       <https>         <url>https://*:30443</url&gt;         <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 / comments
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 u...
0 votes