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

Followed @JaredBusch link to instructions and worked like a charm.

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

@Ylian said in Comparing MeshCentral 2 to ScreenConnect: What is the "correct" alternative to MongoDB on Fedora? Maybe I can build a different database binding... There is none, no document database is included with Fedora now.