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
lineit  
#1 Posted : Friday, June 27, 2014 12:52:15 PM(UTC)
lineit


Rank: Newbie

Joined: 6/27/2014(UTC)
Posts: 4
Australia

Hi,

I've configured a sub-domain to point to my router via DDNS. Confirmed working as it works off port 8040 to load Screen Connect. Next stage is to configure SSL. I've bought the certificate and installed it. Changed the web.config file to show "<add key="WebServerListenUri" value="https://+:443/" />". I've added a port forwarding to router 443 traffic to the server. Yet it says the page can not be found. Tried browsing with the https:// at the front and :443 at the back of the address and no luck.

Advice would be appreciated.

Scott  
#2 Posted : Friday, June 27, 2014 1:04:07 PM(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)
Hmm, from your description it looks like you did everything correctly.

It's probably easiest if you shoot an email to us at support@screenconnect.com so we can take a closer look. Please reference this forum post in your message.
ScreenConnect Team
Paul Moore  
#3 Posted : Friday, June 27, 2014 2:00:52 PM(UTC)
Paul Moore


Rank: Advanced Member

Medals: Level 3: Shirt off your back! Received 25 Thanks!

Joined: 9/16/2011(UTC)
Posts: 334

Thanks: 5 times
Was thanked: 70 time(s) in 44 post(s)
If you're on IIS, I suspect you've installed the cert actually in IIS, meaning it's using port 443, not ScreenConnect.

Any more info?
ScreenConnect Reporting - Collects live & historical information including session times.
http://goo.gl/nrF3e9
lineit  
#4 Posted : Friday, June 27, 2014 2:18:39 PM(UTC)
lineit


Rank: Newbie

Joined: 6/27/2014(UTC)
Posts: 4
Australia

I'm using Fedora 19 as my server. I've emailed support with the follow steps.


1. Used the SSL configurator to generate a package for Linux
2. Create the signing request and signed up for a Comodo SSL certificate.
3. Renamed the issued Comodo SSL certicate and packaged it into a 443.cer and 443.pvk
4. Installed the httpcfg package onto Fedora 19
5. Copied the 443.pvk and 443.cer to the directory /opt/screenconnect/App_Runtime/etc/mono/httplistener/. *Had to create the folder “httplistener”
6. Ran the command “httpcfg -add -port 8081 -pvk 443.pvk –cert 443.cer
Paul Moore  
#5 Posted : Friday, June 27, 2014 2:27:40 PM(UTC)
Paul Moore


Rank: Advanced Member

Medals: Level 3: Shirt off your back! Received 25 Thanks!

Joined: 9/16/2011(UTC)
Posts: 334

Thanks: 5 times
Was thanked: 70 time(s) in 44 post(s)
If you're using intermediate certs with Comodo, Mono won't work.

You might want to look at the nginx route.
http://forum.screenconne...and-Nginx.aspx#post10876

Edited by user Friday, June 27, 2014 2:29:07 PM(UTC)  | Reason: Not specified

ScreenConnect Reporting - Collects live & historical information including session times.
http://goo.gl/nrF3e9
lineit  
#6 Posted : Friday, June 27, 2014 3:06:53 PM(UTC)
lineit


Rank: Newbie

Joined: 6/27/2014(UTC)
Posts: 4
Australia

Thanks for the reference.

I'll give it a try tomorrow. Tried to change the port back to 8040 and it didnt load either. So I'll reinstall Screen Connect and use the reference if it doesnt work then.
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.