Your comments
why cant they just use port 443.... it just makes it harder for client and migration to new servers when you have onpern..
+1 for this! We need to secure connectwise easly without some hoops to go thrue!
Customer support service by UserEcho
for future reference here is that i have done.
Step 1 install connectwise control see that its working.
Step 2 install IIS and Certify the web, dont forget to install https://www.iis.net/downloads/microsoft/url-rewrite
Step 3 in iis add a new url rewrite rule
Template: Blank
i named mine https redirect
input: url after path /
matches
pattern; *
Conditions
Input conditions
{HTTPS}
Match the pattern
Pattern off
Ignore case yes
input contiontons
{REQUEST_URI}
Dose Not Match the pattern
Pattern:
*.well-known/acme-challenge/*
Ignore case yes
Action Type: Redirect
Action URL/Redirect url: https://{HTTP_HOST}{REQUEST_URI}
Append Query String yes
Redirect type Found (302)
that takes care of http to https
here is the web.config iis 10
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system.webServer>
<rewrite>
<rules>
<rule name="HTTPS redirect" enabled="true" patternSyntax="Wildcard" stopProcessing="true">
<match url="*" />
<conditions logicalGrouping="MatchAll">
<add input="{HTTPS}" pattern="off" />
<add input="{REQUEST_URI}" pattern="*.well-known/acme-challenge/*" negate="true" />
</conditions>
<action type="Redirect" url="https://{HTTP_HOST}{REQUEST_URI}" redirectType="Found" />
</rule>
</rules>
</rewrite>
</system.webServer>
</configuration>
Change the WebServerListenUri from 8040 to 443