@smartkid808 If you see this error:
Error: ENOENT: no such file or directory, open '/home/wscheele/views/layouts/main.handlebars'
This was due to a new version of express-handlebars 3.1.0 that broke MeshCentral. I released a new version of MeshCentral last night v0.3.4-k with a fix for this.
This is an interesting suggestion! Can someone send a screen shot of that this landing page look like on other products?
FYI. Started work on a night-mode user interface for MeshCentral. It's in v0.3.4-b, but need to do a bunch more work to get it nice.
@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.
@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.
Charts. I need to add a inactivity timeout for one-sided relays sessions to fix the green line.
Automatic backup is a good idea. If you have any suggestions, don't hesitate to add them to the GitHub issues list. By the way, last batch of updates includes support for ARMv8 64bit, Web Notifications, some improvements to multi-display selection, working on better tracking of relay sessions. Plenty more bug fixes of course.
MeshCentral should not require make. If it does, this is a bug. I don't want the MeshCentral server to depend on anything but node itself. If you get an error during install, please post it here or better yet on GitHub, I will work to fix it. MeshCentral should remain super easy to install.
In other news, back to requests and fixing bugs this week. Last two weeks saw lots of work on Intel AMT IDER, but finally back to more normal tasks.
@scottalanmiller On Windows terminal currently launches within the MeshAgent process and causes a bunch of issues. Bryan who works on the agent will be looking into spawning a separate process for the terminal shell / powershell that should help. One huge bug with the current model is that "ping -t 1.2.3.4" can't be halted and will keep running even after the agent is stopped. To summarize, the Windows terminal needs more work.
I just released a JavaScript IDER server and added it to MeshCommander v0.7.5 and MeshCentral v0.3.2-p. Blog about this here. This is going to be really amazing for Intel AMT users. Now that this is done, I can go back to bug fixing.
@scottalanmiller Apologies, what are TUIs?
Ha yes, I have to do some more work on the timeline. However, normally I would see "Connectivity: MeshAgent" if the agent was online (just below "Active User"). Since it's not present, I imagine the agent is not currently connected?
Just published MeshCentral v0.3.2-l with early support for user notification when a remote session is connected. I expect to keep adding to this going forward, but wanted to release a starter version that just displays a toast notification when a remote session is connected. You can go in the device group page and edit this. You can also add "UserConsentFlags" in config.json domain section to force all device groups domain wide:
"__UserConsentFlags__" : "Set to: 1 for desktop, 2 for terminal, 3 for files, 7 for all",
"UserConsentFlags" : 7
Feedback appreciated,
Ylian
Thanks for reporting it, yes 0.3.2-b had a problem where some agents would disconnect in just the right way and cause a server fault. Should be fixed. Got a lot of small fixes done today.
As for a roadmap, I don't really want one as I don't want to be committing to stuff in advance. However:
It's really never ending. It's possible companies could take the open source version and provide a professional version and/or deployments. That would be great and I certainly want to encourage this.
@dafyre I did enjoy my vacations, but I have to say, I also enjoy working on MeshCentral. It's really fun. Just published MeshCentral 0.3.1-y:
LOL. I just got back this morning and about to step back on the coding treadmill. Got a lot of bug reports on GitHub I need to got thru in the coming days.
Nice! Today I added a "Log scale" option because some data was really off. I also made it so some data points start expiring as times goes on. One hidden feature, you can click on the series names at the top to toggle them.
@scottalanmiller Many thanks for reporting this on GitHub. Did a bunch of fixes to minification and NeDB code as a result. Very must appreciated.
The MeshCentral Router with relay mapping is indeed, very interesting. By the way, just Published MeshCentral v0.3.1-d with server data collection and charts. You probably want to update and wait a few hours to start getting pretty pictures. Data is logged every 5 minutes. Enjoy. Feedback appreciated.
