Comparing MeshCentral 2 to ScreenConnect
-
@FATeknollogee said in Comparing MeshCentral 2 to ScreenConnect:
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
@FATeknollogee When a port is busy, MeshCentral tries to bind to the next available port. So, since port 80 was busy, 81 was used. If you are on Windows, it's likely IIS is using port 80 already.
I've tried this on 2 separate installs & both times I get the same error.
Install is Ubuntu 18.10netstat -tulpn | grep 80 -
@Ylian - Just curious is the "_" necessary in the config settings?
Ex: "_RedirPort" vs "RedirPort"
-
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
@FATeknollogee said in Comparing MeshCentral 2 to ScreenConnect:
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
@FATeknollogee When a port is busy, MeshCentral tries to bind to the next available port. So, since port 80 was busy, 81 was used. If you are on Windows, it's likely IIS is using port 80 already.
I've tried this on 2 separate installs & both times I get the same error.
Install is Ubuntu 18.10netstat -tulpn | grep 80tcp6 0 0 :::80 :::* LISTEN 7566/node -
@syko24 said in Comparing MeshCentral 2 to ScreenConnect:
@Ylian - Just curious is the "_" necessary in the config settings?
Ex: "_RedirPort" vs "RedirPort"
Any text after _ is ignored.
-
@black3dynamite said in Comparing MeshCentral 2 to ScreenConnect:
@syko24 said in Comparing MeshCentral 2 to ScreenConnect:
@Ylian - Just curious is the "_" necessary in the config settings?
Ex: "_RedirPort" vs "RedirPort"
Any text after _ is ignored.
Ah so like an on off switch basically. Good to know. Thanks
-
@FATeknollogee said in Comparing MeshCentral 2 to ScreenConnect:
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
@FATeknollogee When a port is busy, MeshCentral tries to bind to the next available port. So, since port 80 was busy, 81 was used. If you are on Windows, it's likely IIS is using port 80 already.
I've tried this on 2 separate installs & both times I get the same error.
Install is Ubuntu 18.10@Ylian Any thing else I can try?
-
Just listing some additional differences between MC and SC:
ScreenConnect offers 2 factor authentication
(Email & SMS
Google Authenticator
YubiKey
Microsoft Authenticator
LinOTP
Duo Security "push" alerts)ScreenConnect has a lockout mechanism to prevent brute force attacks.
I have not seen these options in MC yet but possible feature requests.
-
@syko24 Yes, lockout and two-factor and both good ideas! Bit busy now, but that we certainly on the list.
-
@FATeknollogee Well, if port 80 is busy and MeshCentral is using 81 instead, try going to port 80 with a browser to see what is using it. You could also use a router and port map port 80 of your public IP address to port 81. That should work and you can ignore the warning. Not sure how much I can help with the freeing up of port 80
-
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
@FATeknollogee Well, if port 80 is busy and MeshCentral is using 81 instead, try going to port 80 with a browser to see what is using it. You could also use a router and port map port 80 of your public IP address to port 81. That should work and you can ignore the warning. Not sure how much I can help with the freeing up of port 80
There doesn't seem to be anything using port 80
root@control:~# netstat -tulpn | grep 80 tcp6 0 0 :::80 :::* LISTEN 7566/node -
@syko24 Right. The _ just causes MeshCentral to ignore that setting. I put a sample "config.json" in place to get people started, but really, MeshCentral will work just fine without any config.json file. MeshCentral will use all default values until indicated otherwise. The sample config.json basically does nothing until you start removing the _ chars.
-
root@control:~# netstat --tcp --listen --numeric-ports Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 localhost:27017 0.0.0.0:* LISTEN tcp 0 0 localhost:53 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN tcp6 0 0 [::]:80 [::]:* LISTEN tcp6 0 0 [::]:4433 [::]:* LISTEN tcp6 0 0 [::]:22 [::]:* LISTEN tcp6 0 0 [::]:443 [::]:* LISTEN -
@FATeknollogee On this screen, it looks like MeshCentral was able to grab ports 80, 443 and 4433 as normal. Looks good and port 81 was not used. Is there still a problem? Looks ok to me.
-
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
@FATeknollogee On this screen, it looks like MeshCentral was able to grab ports 80, 443 and 4433 as normal. Looks good and port 81 was not used. Is there still a problem? Looks ok to me.
Lets Encrypt will not install
-
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
@FATeknollogee On this screen, it looks like MeshCentral was able to grab ports 80, 443 and 4433 as normal. Looks good and port 81 was not used. Is there still a problem? Looks ok to me.
Same error:
MeshCentral HTTP redirection web server running on port 81. ERROR: Redirection web server must be active on port 80 for Let's Encrypt to work. MeshCentral v0.2.5-d, WAN mode. MeshCentral HTTPS web server running on control.mydomain.com:444 -
@FATeknollogee Is it not possible MeshCentral is being run twice? If port 80, 443 and 4433 are already taken by one instance of MeshCentral, running it again will take ports 81, 444 and 4434.
-
@Ylian Will "systemctl stop meshcentral.service" stop all running instances?
-
@Ylian Looks like I was running a few commands out of order.
First, I should:systemctl stop meshcentral.servicenext, enable LE in the config.json
and then runnode ./node_modules/meshcentral -
Updated to 0.2.5-e this morning.
-
Updating to 0.2.5-f now.
