-
Notifications
You must be signed in to change notification settings - Fork 6
/
router_configuration_setup_example.txt
21 lines (19 loc) · 1.19 KB
/
router_configuration_setup_example.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
Web.config Setup Example:
This example is for a default ScreenConnect server without HTTPS, the Web server is listening on 8040 and the Relay on 8041.
Web requests that come in on either 80 or 443 are forwarded to the correct port but HTTPS is not applied because the server is not serving those requests.
Add the following block to the web.config file (C:/Program Files (x86)/ScreenConnect/web.config) just below the opening <configuration> block.
<configSections>
<section name="screenconnect.routing" type="ScreenConnect.RoutingConfigurationHandler, ScreenConnect.Server" />
</configSections>
<screenconnect.routing>
<listenUris>
<listenUri>tcp://+:80/</listenUri>
<listenUri>tcp://+:443/</listenUri>
</listenUris>
<rules>
<rule schemeExpression="http" actionType="issueRedirect" actionData="http://$HOST:8040/" />
<rule schemeExpression="ssl" actionType="forwardPayload" actionData="http://localhost:8040/" />
<rule schemeExpression="relay" actionType="forwardPayload" actionData="relay://localhost:8041/" />
</rules>
</screenconnect.routing>
If you only want to use 443 then that's the only port on which the listenUri should be configured and the actions should be updated accordingly.