The new views really make a huge difference. Going to the top bar view, removing the bottom bar, adding dark mode. I have way more screen real estate and feel like I can get to what I need more quickly.

Got it all working. Thanks for everyone's assistance!

@Ylian said in MeshCentral Feature Request: User Groups: @scottalanmiller Feedback appreciated, let me know if it works for you. I did post a new blog on this topic today. We've started testing it and so far, yes, it is working!

0.4.6-x has released... "Fixed mobile application for user groups., Remove straight dep in lieu of module push if plugins are enabled, Only if plugins are enabled, add semver module, Add semver dependency for plugin version and compatibility checks."

@scottalanmiller That's one hell of a run on sentence! Do you actually speak without pausing or breathing?

@stacksofplates said in MeshCentral User New Device Reset 2FA: @travisdh1 said in MeshCentral User New Device Reset 2FA: I've switched from Google Authenticator to Authy, makes so device changes aren't so much of a pain. I use my Yubikey for that. I was using FreeOTP but it's a pain switching phones. I'm looking at Authy for that reason. Haven't decided yet. So everything is sitll in Google Authenticator.

Exported, cleaned up references to mongo and all better. No Mongo. Export the database (this uses the running database, so I had to have Mongo fixed) cd /opt/meshcentral node node_modules/meshcentral --dbexport" Go in the config file and remove the "mongodb" line(s) in settings nano /opt/meshcentral/meshcentral-data/config.json Restart meshcentral systemctl restart meshcentral # or /opt/meshcentral/mcstop /opt/meshcentral/mcstart Import the database cd /opt/meshcentral node node_modules/meshcentral --dbimport" Restart meshcentral systemctl restart meshcentral # or /opt/meshcentral/mcstop /opt/meshcentral/mcstart

@scottalanmiller said in Ubuntu 19.04 upgraded from 18.10 - Meshcentral not redirecting port 80: @pmoncho said in Ubuntu 19.04 upgraded from 18.10 - Meshcentral not redirecting port 80: @scottalanmiller said in Ubuntu 19.04 upgraded from 18.10 - Meshcentral not redirecting port 80: @pmoncho said in Ubuntu 19.04 upgraded from 18.10 - Meshcentral not redirecting port 80: I would need to move it outside of home dir to something like /opt? Should, of course. No software ever goes in the /home directory. But need to? No, root can use any directory. Will work on this. Thanks If you are using NeDB, it is super simple to move the data file. If you are using MongoDB, the database is always still there on the same port. Until MongoDB is gone!

@scottalanmiller said in MeshCentral never updates the display name: I would prefer hostname as a separate "detected" field that is always there, and the display name as one that doesn't change on us. I don't care what the default setting is, as long as it is a setting that I can choose, because I will hate having to update crap all the time.

Great question actually. I don't use hyper-v much.

0.2.9-z is working for us here. Thanks!

Upgraded from 18.04.2 LTS to current. Accepted default answers for individuals packages during upgrade. Had issue with MC and the meshcentral-data/meshcentral.db getting set with root:root perms and this caused a few errors with starting MC from meshcentral.service Changed perms to back to <user>:<user> and all is well. Don't know what would change those perms though? Either way, all is well now.

@scottalanmiller said in MechCentral Feature Request: Blank Background Wallpaper Option: A feature that I would really like to see on MeshCentral is the option to have background wallpaper blanked out. This reduces bandwidth needs and often goes a long way to improve responsiveness and look & feel when using remote access. Many customers and users have rotating backgrounds that just destroy remote connections. @Ylian Already submitted a request on github?

@vpr00 said in MeshCentral Performance Testing: Sometimes after i press connect, half of the image loads and it wont load any further. I have to press disconnect and connect again until it works. Have you experienced the same? It only happens with WebRTC though. Yes, we do see that from time to time.

Anyone? I went thru manuals evrything seems ok but no success. LetsEncrypt subfolder is not created even if production is false This is my config.json { "settings": { "cert": "MyDomain", "wanonly": true, "_minify": true, "letsencrypt": { "email": "MyEmail", "names": "MyDomain", "rsaKeySize": 3072, "production": true }, "webrtc": true, "allowhighqualitydesktop": true }, "domains": { "": { "title": "RDP support" } } }

@JaredBusch said in Install MeshCentral2 on Fedora 29 with MongoDB: @scottalanmiller said in Install MeshCentral2 on Fedora 29 with MongoDB: @bnrstnr said in Install MeshCentral2 on Fedora 29 with MongoDB: Is it possible to migrate from MongoDB to NeDB after we've been running for a while? Easier to just start over? Probably, but never considered doing that! I think @Ylian mentioned that is was possible or was going to be possible. in the main thread.. not 100% sure. Should be, they share a format. I've just never ingested a backup into NeDB before.

@JaredBusch said in MeshCentral - Unable to update: @scottalanmiller said in MeshCentral - Unable to update: @DustinB3403 said in MeshCentral - Unable to update: @scottalanmiller said in MeshCentral - Unable to update: Non-MongoDB install here. Update went smoothly. Didn't mongoDB just change their license too, to something so practically insane that using MongoDB for even free and open source projects makes it worthless to consider? Nope. They just made it only make sense for open source projects. Yes, they fucked it all up. But as long as everything is open source, it seems to still be ok to use. Yeah. For open source, it works fine. The physical product is good, but just not the license. Have to say, we've been testing Atlas, their "paid" service and it is unstable. So even their paid for product, if you pay to make it okay for non-open source projects, isn't viable. Like seriously unstable. We've had more outages in three weeks of testing with Atlas on Amazon AWS, then we've had with our in house MongoDB on Linode in five years!

@black3dynamite said in MeshCentral Agent Supported Linux Distros: I'm able to connect to the Desktop on Fedora 29 Gnome (Xorg). At the lock screen too. Same here.

Its actually Upload default server core, when the terminal has gotten stuck for me, I have cleared the core and then upload the default server core to get it to work again properly without rebooting the machine. Clearing the core gets only General, Events and Console tabs and loading the default loads all the rest. Maybe it helps in this case as well.

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

https://drive.google.com/drive/folders/11AyoZGllxZ5tenyMQ2_b1DDo7c2-Znhc?usp=sharing

@Dashrender said in MeshCentral - Anyone tried this?: @FATeknollogee said in MeshCentral - Anyone tried this?: @scottalanmiller said in MeshCentral - Anyone tried this?: Fedora is working now. Don't know why, installed again and it worked. Did the install on Fedora require any different or additional steps compared to the Ubuntu instructions? What flavor of Fedora did you use? I think the Fedora install might have only been the client side, not the server side. Thx for pointing that out.