logo

The ConnectWise Control forum has moved to ConnectWise University! This forum has been locked and is in read-only mode. Click here for instructions on how to access the new forum.

Welcome Guest! You can not login or register.

Notification

Icon
Error

Options
Go to last post Go to first unread
stevenli  
#1 Posted : Tuesday, February 27, 2018 5:44:37 AM(UTC)
stevenli


Rank: Guest

Joined: 2/27/2018(UTC)
Posts: 1
Slovenia

Hi Guys,

I've tried for two days using IIS to do reverse proxy (from https to http) to on-premise screenconnect. Things seem to work except downloading clients(404 - File or directory not found. The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.) and connecting client (the target machine actively refused to relay 127.0.0.1:8041). Wondering if anyone, has successfully set up a reverse proxy from https to http, willing to share their config and settings. this might benefit those who have both screenconnect and iis installed on same server.

Best Regards
Steven

Scott  
#2 Posted : Monday, March 12, 2018 11:26:37 AM(UTC)
Scott


Rank: Administration

Medals: Level 4: Wise Old Owl! Received 100 Thanks!

Joined: 3/28/2014(UTC)
Posts: 2,862
United States

Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
Have you added a WebServerAddressableUri value to the web.config? This specifies the URI from where files are delivered.
ScreenConnect Team
leungda  
#3 Posted : Friday, May 4, 2018 2:02:38 PM(UTC)
leungda


Rank: Guest

Joined: 3/9/2018(UTC)
Posts: 6

Yes, it is exactly what I want to do

https request -> IIS reverse proxy -> http:8040 to actual server
reply request -> actual server

I tried but still doesn't really work

any help?
Michael L  
#4 Posted : Monday, May 7, 2018 1:52:04 PM(UTC)
Michael L


Rank: Administration

Medals: Level 1: Random Act of Kindness! Received One Thanks!

Joined: 8/18/2015(UTC)
Posts: 98
Man
United States

Thanks: 8 times
Was thanked: 14 time(s) in 12 post(s)
This thread might be helpful for you:

https://controlforum.con...ct-Using-SSL-on-IIS.aspx
ConnectWise Control (ScreenConnect) Support Team
frankg  
#5 Posted : Tuesday, June 12, 2018 8:49:27 PM(UTC)
frankg


Rank: Member

Joined: 4/24/2013(UTC)
Posts: 27
Location: frankg

We have a reverse proxy on the same machine (nginx on top of ScreenConnect)

Maybe this will help:


<add key="WebServerListenUri" value="http://+:8040/">
</add>
<add key="WebServerAddressableUri" value="https://my.scdomain.com:443">
</add>
<add key="RelayListenUri" value="relay://0.0.0.0:8080/"

folken  
#6 Posted : Thursday, July 5, 2018 2:13:34 PM(UTC)
folken


Rank: Guest

Joined: 7/5/2018(UTC)
Posts: 1
Australia

Originally Posted by: frankg Go to Quoted Post
We have a reverse proxy on the same machine (nginx on top of ScreenConnect)

Maybe this will help:


<add key="WebServerListenUri" value="http://+:8040/">
</add>
<add key="WebServerAddressableUri" value="https://my.scdomain.com:443">
</add>
<add key="RelayListenUri" value="relay://0.0.0.0:8080/"



The reason this doesn't' work is that the folder /bin/ is a reserved folder on IIS for ASP.net applications. You need to edit your web.config file as used by IIS and remove the protection of bin. This will then allow the reverse proxy to work correctly and you can download files.

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system.webServer>
<security>
<requestFiltering>
<hiddenSegments>
<remove segment="bin" />
</hiddenSegments>
</requestFiltering>
</security>

<rewrite>
<rules>

Edited by user Thursday, July 5, 2018 3:49:22 PM(UTC)  | Reason: Not specified

Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.