Comparing MeshCentral 2 to ScreenConnect

Ylian

@StuartJordan said in Comparing MeshCentral 2 to ScreenConnect:

Kaspersky

I asked to be whitelisted by Kaspersky a few months back and they approved. I will need to check that again.

We have our own WebRTC stack in the MeshAgent which is quite unique. However, Firefox v64 just broke it (Looking into it), Chrome works. With WebRTC traffic goes directly from the browser to the agent bypassing the server. Should be faster, scale better and lower hosting costs.

Yes, I am traveling for the next 5 days, will be back with updates soon. Got plenty to work on.

Ylian

black3dynamite

I need to test MC with Sophos.

scottalanmiller

@Ylian said in Comparing MeshCentral 2 to ScreenConnect:

We have our own WebRTC stack in the MeshAgent which is quite unique. However, Firefox v64 just broke it (Looking into it), Chrome works. With WebRTC traffic goes directly from the browser to the agent bypassing the server. Should be faster, scale better and lower hosting costs.

Yes, we use that here and it's SCREAMING fast!!

black3dynamite

@scottalanmiller Are using Ubuntu current or LTS?

scottalanmiller

@black3dynamite said in Comparing MeshCentral 2 to ScreenConnect:

@scottalanmiller Are using Ubuntu current or LTS?

Current

FATeknollogee

I'm getting an error trying to setup LE:

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.meshexample.com:444.

My config.json:

  "settings": {
    "MongoDb": "mongodb://127.0.0.1:27017/meshcentral",
    "MongoDbCol": "meshcentral",
    "WANonly": true,
    "_LANonly": true,
    "_Minify": 1,
    "_SessionTime": 30,
    "_SessionKey": "MyReallySecretPassword",
    "_Port": 443,
    "RedirPort": 80,

scottalanmiller

No proxy in front of it, right?

scottalanmiller

Have you tried it with no RedirPort setting at all? I have nothing set and it works fine. 80 is the default.

FATeknollogee

@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:

No proxy in front of it, right?

No proxy.

FATeknollogee

@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:

Have you tried it with no RedirPort setting at all? I have nothing set and it works fine. 80 is the default.

You mean, try like this?

    "_RedirPort": 80,

Either way, I get the same error.

JaredBusch

@StuartJordan Self hosted SC is not horribly priced. Not as good as it used to be. But still a viable price.

Hosted is similar to other hosted solutions I believe. And is certainly higher than I would prefer.

I have legacy pricing for SC self hosted, so really hard to get better.

MC2 seems to actually do it.

black3dynamite

Email works for now using Ubuntu Server 18.10 live installer. Does nodemailer requires packages that is not included with a minimal install of Fedora?

scottalanmiller

@black3dynamite said in Comparing MeshCentral 2 to ScreenConnect:

Email works for now using Ubuntu Server 18.10 live installer. Does nodemailer requires packages that is not included with a minimal install of Fedora?

Not sure, but unlikely.

CloudKnight

Don't have the invite link on my install, I'm using the latest version apparently as well, any ideas?

FATeknollogee

@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:

Have you tried it with no RedirPort setting at all? I have nothing set and it works fine. 80 is the default.

I forgot to mention, my setup is using mongodb, not sure if that is related to the error!

Ylian

@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.

scottalanmiller

@StuartJordan said in Comparing MeshCentral 2 to ScreenConnect:

Don't have the invite link on my install, I'm using the latest version apparently as well, any ideas?

Is your SMTP set up?

FATeknollogee

@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

scottalanmiller

@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

netstat -tulpn | grep 80

syko24

@Ylian - Just curious is the "_" necessary in the config settings?

Ex: "_RedirPort" vs "RedirPort"