Posts made by Ylian

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

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

@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

@syko24 Yes, lockout and two-factor and both good ideas! Bit busy now, but that we certainly on the list.

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

@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 For SMTP setup, does your server show the "Invite" link as shown in red below? Also, can you go in the "My Server" tab, click on "Show server error log" and report back if you see anything in that log? - Thanks.

Just published MeshCentral v0.2.5-d where you can re-brand the top bar with your company logo. Personally, I would start with the "logoback.png" file in the "node_modules/meshcentral/public/images" and add your logo to it. Instruction are in section 19 of the new v0.1.9 User's Guide. Enjoy!

@Romo Just fixed Win7 "Interactive Services Detection" bug in MeshCentral v0.2.5-b. If it happens again, let me know.

@mattbagan Follow the instructions to run your own MeshCentral server. No need to log in to anything. On a different topic, MeshCentral.com still runs the old v1 code and I will be migrating it to v2 sometime next year.

@scottalanmiller You guys are going to flood me with bug reports! Yes, please file them on GitHub. Very must appreciated. I am going back to code now. Got plenty to go fix.

@FATeknollogee Ha yes. If you run MeshCentral like that, it will break the self-update capability. This is normal, since MeshCentral will not have the rights to change it's own files. It's the cost of better security. In the future, I want to detect this case and disable the self-update options. You will need to do "npm install meshcentral" again manually with higher privileges to update.

@Romo Perfect bug report for GitHub Just updated the terminal support for Windows in the MeshAgent and I just started seeing this yesterday. Looking into it.

@notverypunny Yes, we will be fixing that at some point. It's funny how MeshCentral is used by the "IoT / digital sign" people that don't want any notification and/or want the remote screen blanked to black. And support usage who want notification and user consent.

Hi. Ylian here. I am the guy behind MeshCentral. I am really busy writing code but wanted to say hi. In reading this thread I figured I would answer a few questions. So yes, MeshCentral2 is a complete re-write. The older version was designed about 10 years ago when the web was very different. Only some parts of the old agent code have been kept in the new one, but it's mostly all new. Coding started a bit over a year ago, so progress has been pretty good.

When setting up a MeshCentral server, the first account you create will be administrator on the server. All accounts after that are normal users. If you want to block new accounts, set newAccounts to 0 in the "config.json" file in the default domains section. Take a look at the very end of the User's Guide for an example config.json. If you have not do so already, look at the config.json file and user's guide, there are plenty of customization options.

We currently test on Windows7 and higher. Windows XP is increasingly difficult to support because we use features in the MeshAgent that are not supported in older operating systems (pretty much threading related).

If you have any feature requests, please don't hesitate to add them to the list of issues on MeshCentral Github. Not sure if you guy saw this on the blog, but we just added audio/video chat support.

Any feedback and bug reports are very much appreciated. Obviously I can't always do magic. Just as a fun exclusive fact for this thread: If you press "shift" when you hit the full screen icon in remote desktop, it will use browser full screen.

Ylian