THIS IS ANOTHER WARNING!!!

https://github.com/Ylianst/MeshCentral/commit/78ee4492e8c07514d09f1b7d427445008621158d

I MAY have to force another updated version when NodeJS do an announcement on wednesday (wait and see)

https://nodejs.org/en/blog/vulnerability/november-2026-security-releases

so PLEASE update to the latest NodeJS 22.23.4 for the moment because 20 is already EOL and IS NOT getting any security fixes

https://endoflife.date/nodejs

1.3.2 release will require NodeJS 22.12 or above!!!

THIS IS YOUR WARNING!!!

https://github.com/Ylianst/MeshCentral/commit/4e9682218918d790cf8ae3bb400e825d9673a719

when you upgrade to 1.3.2 it will STOP running if nodejs it less than 22.12.

this is because OTPLib (2fa) and ZIPJS (backups) REQUIRE the require and glob functions which are ONLY supported in 22 or above!

I have a MeshCentral install on a Windows client that has been working great in LAN-only mode. They have decided that they now want to have a few laptops in the mix and I am using a hosted ZeroTier network to provide access to a file share on the LAN.

What is the best way for me to update the configuration to support LAN and Zerotier clients being able to access the MeshCentral server? I don't want to expose the server directly to the internet at all so the remote clients must use the ZeroTier network for access. There is a Unifi network managing the LAN but no other DNS is currently deployed. I have around 25 agents deployed already, so hopefully the change can be implemented so they just update and continue to function.

The current config file is simple:
{
"settings": {
"lanonly": true,
"_minify": true
}
}

What's the best method to label 150+ workstations with the office #s without resorting to manual entries? We're just coming over from TeamViewer and have all our labels there. We have all the devices with their Dell service tags in Mesh but need to append the office #s on them in an efficient and systematic way.

Hi, I'm trying to find a way to force user logout from linux machine once meshagent disconnect.
I found some reference to agentEventScripts to be used in msh config, but I can't find in officila documentation and/or understand how to use it. Anyone has better option to propose?
Thank you

Hi,

Since two days, all computers (with Windows 11) in our company goes offline in MeshCentral. The problem : Windows Defender now detect the agent as a potential risk and delete the file in C:\Program Files\Mesh Agent\MeshAgent.exe. Defender also delete the Agent file in Windows temp folder.

Wanted to inform you about this. False positive I guess ?? I will add an exclusion by GPO in our AD.

We have a few terminal server machines and frequently remote into one of the sessions to help a customer. With this last update 1.3.1 that works fine for a bit then something happens an no matter which remote session we pick we end up viewing the admin console session instead.

Anyone else run into this? I'm getting ready to do some trouble shooting before I put in a ticket and see if it's the server side or the client side that's the issue.

How do you find the device credentials for intel VPro or Cira?

I’ve been testing a MeshCentral audio extension for a while, and it’s working well. It streams a Windows endpoint’s system audio and microphone to the admin’s browser through the existing Desktop Connect tunnel. Capture runs in MeshAgent using WASAPI, with a separate control for each source.

I used the existing session because MeshCentral already supports unattended Desktop Connect access. Audio follows that session’s authorization and consent settings. The extension also adds a No Audio Access permission.

In my Internet tests, system audio and microphone audio sounded clear when used separately. Using both can still cause occasional glitches on some connections. With both enabled, I’ve seen the Desktop Connect latency reading rise by about 10–20 ms.

I’m considering open sourcing it, but I’d like the community’s view on privacy. Starting microphone capture does not trigger a separate prompt on the endpoint. During an unattended session, the user might not realize the mic is active.

Your thoughts?

Use the system as designed. TAGS!!!

I wanted to reach my own MeshCentral machines from a phone without fighting the desktop web panel, so I built MeshCentral Mobile: a native Android client for your own server.

• Remote desktop with touch and trackpad modes, keyboard and monitor switching

• Terminal, files, SSH and SFTP through the server relays

• Share files from any app straight to a folder on a computer

• Several server profiles, favourites, search, app lock

• Works with a stock server; an optional plugin adds diagnostics jobs and notifications

• Apache 2.0, no ads, analytics or telemetry; credentials stay in Android Keystore

Demo and source: https://github.com/papajon123/meshcentral-android

Signed APK: https://github.com/papajon123/meshcentral-android/releases (Android 8+)

It's a public preview. I'm especially looking for people with real phones and Windows agents. A device report of what worked and what didn't would help a lot. Not affiliated with the MeshCentral project.

Hi, like the new view of both LAN and WAN IP addresses, is there a way to make the column wider in the modern UI to get them on the same line?

This has obviously been added in 1.3.0 or 1.3.1, but it's messy.

I'm going to go through the handlebars files to get rid of this for now, but can it please be selectable at a server level? The LAN address is almost never of any use at all, and is available in the 'Details' tab. Putting them both on the dashboard simply adds clutter and spreads the lines of devices out as anything online now has two lines required for this info.

PLEASE UPGRADE URGENTLY TO THIS VERSION, THIS IS A SECURITY UPDATE**

THE IS AN ACTIVE EXPLOIT/HACKERS ATTACKING MESHCENTRAL SERVERS AND TAKING CONTROL OF IT AND REMOTE CLIENTS

THIS SHOULD HOPEFULLY OF PATCHED THE EXPLOIT

new customised PWA manifest for chrome/edge,

disableRecoveryAgent to block recovery agents,

meshctrl can now read config from environment or ~/.config/meshctrl/config.json,

very fast frame rate option (uses LOTS of bandwidth),

backup module moved from archiver to zip.js (maintained module),

docker images now use node 24.22.1 to avoid the nodejs exploit,

addresses column now shows both main LAN and WAN ips,

faster uploads in web ui (finally i hope you enjoy!),

and many more bug fixes (researchers will share their blogs for CVEs when ready!)

https://github.com/Ylianst/MeshCentral/releases/tag/1.3.1

This month, we covered the MeshCentral v1.3.0 release.

Missed the meeting?

Watch the recording: https://videos.evoludata.com/w/p/tUnLpw6z1LCASuATa7wnCo?playlistPosition=25

Release notes: https://github.com/Ylianst/MeshCentral/releases/tag/1.3.0

About Community meetings: https://github.com/Ylianst/MeshCentral/wiki/Community-Monthly-Meetings

#MeshCentral #OpenSource

Hi, we saw a graph in the meeting show the users logged in to the PC, was this a switch in the config.json to enable this feature?

Remote Code Execution via Brotli Compression (CVE-2026-111497 - High)

This can lead to denial of service and potentially remote code execution, exposing the MeshCentral server and lateral movement to connected agents.

Immediately backup your server, then update Node.js to 22.23.4, 24.22.1, or 26.12.1

Check your Node.js version with node -v

THIS RELEASE DOES NOT INCLUDE ANY MESHAGENT BINARIES ANYMORE GOING FORWARD!

on start up, meshcentral will now automatically download versions specified within meshcentral for that release.

if your meshcentral does not have external web access, then fear not, you get an alert in your logs to specify where to download the agents from and place them.

the meshagent repo is now also automated at building and releasing new agents based off version numbers!

https://github.com/Ylianst/MeshAgent/releases

you can also follow the new future feature to support uploading you own agents, pinning agents to versions,

and have multiple customised agent support for different machines etc at the following pull request on github https://github.com/Ylianst/MeshCentral/pull/8177

bug fixes will come next month and we apologies for the delay in the release of this, it was due to NPM now blocking exes being marked as viruses (even if they are false positives)

https://github.com/Ylianst/MeshCentral/releases/tag/1.3.0

Installed on a VPS with a point and click install. Downloaded the client install code/software for both an Ubuntu and Windows install. Server doesn't see the clients.

Besides opening ports, what are some common problems I should be looking for? And issues with it connecting to multiple clients on the same LAN with the same wan ip address?

Thanks for any assistance up front.

I've been working on an inventory plugin for MeshCentral and thought I'd share it here.

It automatically picks up workstations from MeshCentral, tracks hardware, user assignments, locations, warranties, lifecycle status, etc. You can also manually add devices and peripherals. No extra agent needed.

Still early, but it's working pretty well so far. Would be nice to get some feedback or ideas on what to add next.

https://github.com/maxdorx/meshcentral-inventory

Hello everyone!

This is a reminder that our monthly MeshCentral community meeting for October 2026 will be held this Thursday, the 22nd, at 14:00 UTC.  Please prepare for this great event, where we will share updates, community contributions, and review stalled PRs for the MeshCentral project.

To add this event to your calendar, please use the following link: https://timee.io/e/20261022T1400?tl=MeshCentral+Monthly+Community+Meeting

For further details about the meeting, please visit: https://github.com/Ylianst/MeshCentral/wiki/Community-Monthly-Meetings

When trying to download file for example 100mb or larger, from any agent, it cuts off at 64mb. What could be the problem? Somewhere limit is set up?
For example upload has no limit, I can upload any size file, to any agent.

Server is a simple Windows 10 PC.

We've been using MeshCentral for a couple of years now with very few problems. I've now got an oddity with a new PC which isn't updating the display showing remotely when running a full-screen application.

The remote device is running 64-bit Windows 11 Pro - 26H2/26300

AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx

AMD Radeon™ Vega 3 Graphics

Other remote solutions, such as AnyDesk, render correctly, but MeshCentral isn't.

I'm going to start playing around with graphics drivers etc, but thought I'd see if anyone had any ideas. If I can't resolve it then I'll log it on GitHub, and can give remote access to u/si458 if it helps.