When hitting `add agent` there's a `mobile phone` option. They install the Agent and scan the QR code. You'll have to allow the agent file access. Also every time you need to connect they have to open the app and hit connect and allow the app to mirror the display. This only allows viewing no control. It's not perfect, but works good enough to walk people through things.
I fixed this last night, there was a breaking change to the "node-windows" module that caused trouble. MeshCentral Windows Installer 2.7 should fix this. Let me know if it works. Thanks.
I can't see a way this would be possible on a phone natively.
You would need an option implemented in meshcentral where shift is "held" on the client side.
Alternatively I think you could have AHK do this for you. Ie you run a prebuilt exe and it would hold shift for X seconds on the client end.
Not ideal but its a workaround, albeit a shit one. I use it to type my clipboard when paste isn't natively supported.
I have not tried to activate websocket compression on a large server yet, but you will send and receive less traffic at the cost of more CPU usage. In general, my understanding is the server will have some added latency and use a bit more memory.
If you are hosting MeshCentral on AWS EC2 for example, the first 1GB of outbound traffic is free each month, after that it's $0.09 per GB. So, depending on your usage, turning on compression may save you some hosting costs. AWS EC2 traffic is free for inbound traffic.
One thing to do before turning on compression is to enable minification. This reduces the size of the HTML web pages sent to the Browsers. ("minify":true in settings section of config.json).
Did you heard about "Apache Guacamole"? (Webpage). I dont know if it fits the MeshCentral standards or requirements. Or even if the "philosophy" of MeshCentral about using external apps like that.
But i know it works very fast, it has a well-documented API (You can use JavaScript).
I don't know. Maybe is easy to implement. Just an idea
Hi. If you run meshcentral from the command line it will close when you close the SSH session, this is normal behavior. If you want to run MeshCentral as a background service, try these commands:
sudo node ./node_module/meshcentral --install sudo systemctl start meshcentral sudo systemctl restart meshcentral sudo systemctl stop meshcentral sudo node ./node_module/meshcentral --uninstall
Note that you need to run these as "root", so you can add the "sudo" on front of the command line, but that is not needed if you are already root. For more details, take a look at the install guide and user guide you can find here. Hope that helps.
Looking at my Linux servers, I did not use the "Capabilities=" line at all since I use:
sudo setcap cap_net_bind_service=+ep /usr/bin/node
If you use "setcap" then you can run MeshCentral manually or using Systemd and it should work. If you use the AmbientCapabilities= it only works for Systemd. In any case, I just did a silent update of the documentation at https://www.meshcommander.com/meshcentral2.
Thank you very much for reporting this. I bet many others have run into this and not reported it.
You can take a look at the MeshCentral User's Guide. Currently section 16 is the NGINX setup section. The guide is linked from the MeshCentral main web site.
This is an interesting idea, however with the huge backlog of feature requests on MeshCommander and MeshCentral, it would be quite difficult to add this work for me. From the experience with Intel AMT, it also requires quite a bit of maintenance and each new generation requires software changes. I am certainly not opposed integrating it into the tools and I see there are some libraries on NPMJS.org to do iDRAC and iLO.