MeshCentral 1.1

Hello,

MeshCentral is ready for testing.

Installation is possible using the Software Center by adding my repository, check out the repo webpage for instructions.

After the installation go to the app settings and set a FQDN/hostname.

At the login screen you need to create an account first:
grafik

Still work in progress:

  • LDAP
  • Mail settings
  • Allow/block (agent) IPs
  • Branding

EDIT:

  • Migration from NS7
8 Likes

thnk you @mrmarkuz for this wonderful addition.

1 Like

I agree with @oneitonitram. Thanks for bring this to the test version. I appreciate it.

1 Like

Just out of curiosity if I did a migration. How would Meshcentral factor in to a NS8 migration. Will NS8 actually migrate it? or would I need to backup the data directories like Meshcentral videos tells you to do then copy them to the new install on NS8?

Thanks,
-SF-

i think migration though possible, due to the fact that a database is used for the agents, might be abit more tricky.

this is because, we are also relying on URL of meshcentral for the agents on the corresponding servers. o, unless you might also be looking to utilizing the same domain FQDN, then it might not work even after migration.

1 Like

I’m working on the migration. As soon as I got it working, I’ll share a manual.

5 Likes

Sounds great. Thanks for the follow up and letting me know.

-SF-

1 Like

@mrmarkuz

So far my testing is going good. I wanted to give you some feed back.

3 Likes

NS8-MeshCentral 1.1.27 released.

In my tests with Rocky Linux on Proxmox I needed to set the VM CPU to “host” to make mongodb work, check out GitHub - mrmarkuz/ns8-meshcentral for more info.

1 Like

Did some testing, everything seems to run fine… Except: the ldap-part, which you marked at work-in-progress. Can´t even get the logs to debug…

2 Likes

Thanks for testing!
I hope I can include LDAP soon…

2 Likes

Upgraded to MeshCentral 1.1.35: Release 1.0.2 · mrmarkuz/ns8-meshcentral · GitHub

EDIT:

I forgot to setup Renovate to upgrade mongodb (7.0.16) too. New release: Release 1.0.3 · mrmarkuz/ns8-meshcentral · GitHub

5 Likes

Hi, thank you for your work!

Is it possible to control android devices instead of just showing it up with the latest MeshCentral version?

1 Like

It’s possible to manage files and view screen and details but there’s still no remote screen control over Android devices: GitHub - Ylianst/MeshCentralAndroidAgent: MeshCentral Agent for Android Device

Morning Markus and Merry (Rest) Christmas,

after Installation i see only a white window with “Bad Gatway” in my Browser.
The CPU of the VM is set to “host”. But meshcentral-app and mongo-app are inactive.

Regards…

Uwe

Which CPU is used on the Proxmox host?
Did you already try to reboot the VM?

I can’t reproduce on Proxmox using a Rocky VM.
Is the Proxmox up to date?
Maybe you need to define our own CPU but I don’t think so: CPU with AVX support, | Proxmox Support Forum

My Proxmox runns on a Odroid H3+. CPU is 4 Core Intel Pentium Silver N6005 with 2 GHz (1 Socket).
Rebooting the VM does not bring any change.
I have another (current) instance of Meshcentral running on a virtual DEB 12 on the same Proxmox. This works perfectly.

Which virtual CPU does the Debian VM use? I think it emulates AVX.

The Intel Pentium Silver N6005 doesn’t support AVX, see also AVX intrinsics neede for GPT4ALL - Intel Community

To check if AVX is supported on the Proxmox host or in a VM you could execute:

grep avx /proc/cpuinfo

If there’s no result, AVX is not supported.

1 Like

Sorry, it is a Debian LXC. You are right, AVX is not supported on my Odroid.

1 Like

I released a MeshCentral light app to support low power and older CPUs.
This edition is without mongodb (which needs AVX) so it has lower perfomance but it shouldn’t matter unless you need a lot of MeshCentral clients.

4 Likes