I solved this - problem was, after I changed port on MC2, I needed to download new MeshAgents that are setup for that port and install them to monitored PCs

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 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!

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

@JaredBusch said in MeshCentral LE production cert: @FATeknollogee said in MeshCentral LE production cert: @pmoncho said in MeshCentral LE production cert: @scottalanmiller said in MeshCentral LE production cert: @JaredBusch said in MeshCentral LE production cert: @scottalanmiller said in MeshCentral LE production cert: Oh weird, it was flawless transitioning for us. Did you let it restart on its own or did you manually restart the service? You have to restart the service anytime you change a setting in the config file. You aren't supposed to have to. Or at least you weren't supposed to have to in the past. It was supposed to detect changes and reload on its own. Did you try removing the letsencrypt folder prior to restarting for production mode? I had to do that too, along a couple other things that are now fixed. This was the fix?? Yes.

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

@scottalanmiller said in MeshCentral2 Issue: @dafyre said in MeshCentral2 Issue: What I saw on my Fedora 29/Gnome desktop was that it showed up, but most of the remote features did not work. that's more of what I would expect. As discussed in another thread (I think)... that's due to Wayland being used for Gnome.

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

Using the filter has some cool usage like showing a collection of certain devices by adding a + at the end of each device. lib-dt-01+ cafe-dt-01+ cafe-dt-02+