Welcome Guest! To enable all features please Login or Register.



2 Pages<12
Go to last post Go to first unread
#51 Posted : Tuesday, September 19, 2017 2:39:34 AM(UTC)

Rank: Advanced Member

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

Joined: 2/6/2014(UTC)
Posts: 164
United States

Thanks: 5 times
Was thanked: 8 time(s) in 6 post(s)
I don't understand why everyone is running it this way, anyway. It's *much* easier to just piggyback onto an existing site that supports HTTPS by setting the WebServerListenUri to a subdirectory on the site (that doesn't already exist), such as:

key="WebServerListenUri" value="https://example.com:443/support/"

I suspect most people that have actually bought this software are running a server and at least one site, so this process integrates the ScreenConnect directly into the site as easily as changing this value.

Specifics here:
Users browsing this topic
Similar Topics
HTTP redirect to HTTPS, relay on separate IP port 80. Could not establish trust relationshi (Advanced Customization)
by gcouch 5/14/2014 10:30:02 PM(UTC)
2 Pages<12
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.