@scottalanmiller Published MeshCentral v0.4.5-f that should fix a problem with the web application.
@hobbit666 When you update the server, all agents are automatically updated.

@scottalanmiller The best way to see the smaller changes between releases is to look at GitHub commit log. MeshCentral v0.4.5-c has a first pass at a Czech translation, a bit better French translation, Internalization improvements, support for "MpsAliasHost" in settings section of config.json.

I just post on Twitter major changes. The quick releases are to fix issues on GitHub or respond to specific requests.

@black3dynamite I posted about an hour after I published MeshCentral v0.4.5-b. If you are set to auto-update, your server will generally check between midnight and 1am for any updates. So, 24 hours after I publish a new version, you should have it.

@Ylian Another trick in MeshCentral v0.4.5-b is that the MeshAgent should be able to be installed within a Docker container. We will start testing that a bit more. Should be useful to manage what is going on inside server containers remotely.

FYI. Just published MeshCentral v0.4.5-b, this is a super-update because it includes the next generation MeshAgent. You can check Twitter for updates, but this version includes a new remote desktop privacy bar, wallpaper toggling, improved Windows terminal and more.

@srsmith MeshCentral developer here. There is no Android application for MeshCentral, it just going to be the mobile web site. It's not a feature full as the desktop site, but should get the basics (and supports NFC/Bluetooth two-factor authentication on Android Chrome). Let me know if you try it and what you think of it.

FYI. MeshCentral just hit 500k downloads on npm-stat.com in about 2 years of being available.

You don't generally have to use "aliasport" unless the external port that agents will see if different from the port MeshCentral uses. This is not common.

As for the real certificate, you will not have to reinstall the agents. Agent use a special system to authenticate the server using a second certificate within the TLS connection, it's explained in Section 8 of this guide if you want to look at the details. So you can swap the HTTPS certificate when you want as long as the DNS name and port stays the same.

Also, MeshCentral has built-in support for Let's Encrypt and will auto-renew the certificate. You can find help on this in section 11 of the User's guide.

Hope it helps,
Ylian

@smartkid808 Yes, you can change the port, however you need to do this before installing agents as existing agents will not be able to find the server anymore. The "port" setting in config.json will change the port used by MeshCentral, "aliasport" will change the port MeshCentral tells the agents to connect to. So, if you have a port map in front of MeshCentral, use "aliasport" to indicate the "real" port that will be used. Hope it makes sense.

{
  "settings": {
    "Cert": "devbox.mesh.meshcentral.com",
    "Port": 4430,
    "AliasPort": 444
  }
}

Just added a new blog on the latest MeshCentral news. Lots more improvements this week. The blog highlights MeshCtrl the MeshCentral administrator command line tool.