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

Notification

Icon
Error

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


Rank: Advanced Member

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

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

Thanks: 5 times
Was thanked: 11 time(s) in 9 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:
https://docs.connectwise...existing_SSL_certificate
srutledge  
#52 Posted : Wednesday, September 20, 2017 4:55:35 PM(UTC)
srutledge


Rank: Guest

Joined: 10/7/2016(UTC)
Posts: 5
Location: Georgia,US

How does Piggybacking actually work? Does this mean that IIS is already running on the server? If it running, then isn't it already listening on that port?
shawnkhall  
#53 Posted : Wednesday, September 20, 2017 5:11:18 PM(UTC)
shawnkhall


Rank: Advanced Member

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

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

Thanks: 5 times
Was thanked: 11 time(s) in 9 post(s)
yes and yes. it's a function of .net and IIS - and by far the simplest way to set it up. i spent *hours* trying to get SC to work via SSL when running on its own, but the piggybacking option (once i finally discovered it) took literally 10 seconds to setup. the hardest part was browsing to the web.config file to make it work.
scuneedinghelp  
#54 Posted : Sunday, January 21, 2018 12:37:21 PM(UTC)
scuneedinghelp


Rank: Guest

Joined: 1/21/2018(UTC)
Posts: 1
Location: North Carolina

I have having a lot of trouble getting 80 traffic to forward to https://:443

I am running on Ubuntu
Version 6.4.15361.6527
My SSL Cert is in place
https://mydomain.com - loads fine
https://www.mydmain.com - loads fine
http://mydomain.com - does not load/redirect
http://www.mydomain.com - does not load/redirect


I followed the directions about the HttpsRedirectModule.cs file to the App_Code folder I created

Here is my current web.config

<add key="WebServerListenUri" value="https://+:443/">
</add>
<add key="RedirectFromBaseUrl" value="http://*:80/">
</add>
<add key="RedirectToBaseUrl" value="https://*:443/">
</add>


Any suggestions. I have made some adjustment I have forgotten all the ones I have tested.

Thanks for any help you can provide.
Users browsing this topic
Guest
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.