@MordyT Interesting. I have never seen this error before. Yes, it's safe to re-install, but backup "meshcentral-data" and "meshcentral-files" first. "meshcentral-data" contains the critical certificates that make your server unique. Agents will not reconnect unless you have the right certs. At any time, you can re-install your server and put the "data" and "files" folder back and restart and you should be fine. If you are using MongoDB, make sure to backup the database on a regular bases. If you are not using MongoDB, NeDB will be used and all ".db" files will be in the "meshcentral-data" folder.

Basically, should be easy to recover. Please don't hesitate to ask if you need help.

@MordyT One more thing. If you can go in "MeshCentral-Data" and look at the size of the ".db" files... Is any of the files really big (Megabytes)? If so, what is the name of the file that is big and how big is it? With only 10 PC's, I can't expect any of the files in that folder to be of any significant size. - Thanks.

@scottalanmiller Agreed, I use...

node node_modules/meshcentral --dbexport bob.json

then setup MongoDB in the "meshcentral-data/config.json" and do

node node_modules/meshcentral --dbimport bob.json

However, I need to write this up more formally. This technique will also not migrate general events and power events, so I got some improvements to make.

@Ylian Actually... section 8.4 of the MeshCentral User's Guide does explain how to do the conversion.

@scottalanmiller Now that I have more experience with NeDB, it's possible MongoDB is mostly overkill. The only need for MongoDB is for server peering in the future. I will have each MeshCentral server listen to the change events from the database and use that to synchronize state. I started work on this, but it's still a ways out.

On the power timeline... yes yes... I need to fix this. One thing that would help is to download the power timeline raw data (The "Download Power Events" button on the top right of the power lines display) and make sure the raw data is correct. If it is, it's just me drawing it wrong. If it's not, I need to go fix something deeper in the server. Feedback on this would be appreciated.

@JaredBusch @scottalanmiller Yes, user groups of that form would be useful. Got lots going on right now.

@Dashrender In the "My Devices" screen, you can type a partial device name and it should filter devices. For users, type "user:abc" and any device with a logged in user that has "abc" in the name should show up. This said, feedback and suggestions welcome and should be posted on GitHub.

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

@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 MeshCentral should be able to (I think) support Wayland, what distribution are you using?

@scottalanmiller Thanks for the new link. Just bookmarked it.
@black3dynamite Thanks for the distro, I will pass that to Bryan so he can test the agent with it.

Changing the user access control system is going cause a bunch of trashing in the code, published MeshCentral v0.4.6-q just now with lots of changes in preparation for user groups. If you spot anything wrong, please let me know.

@Romo That is correct, the red "Agent Tag" is a "meshagent.tag" text file that is in the same folder that the "meshagent.exe". It can contain up to 1k of data sent to the server on each agent start. It's there so if you have some sort of automatic installation of the agent, you can put a serial number of something in that file and it gets sent up to the server. It pre-dates the other blue tagging that is server side only.

All this to say, the two tagging systems are completely separate. I can add you a "atag:<agenttag>" filter if you like? Let me know what you need.