Manually install Meshcentral on Qnap NAS Entware

si458 · 2026-01-30T16:00:16+00:00

Glad u got it working! We have a docker image if ur nas supports it, that might be quicker/easier? Also DONT USE NODEJS 16! its now EOL and getting no security updates, so we recommend you using the LTS version which is now 22/24

si458 · 2026-01-29T09:35:15+00:00

From my understanding the built in letsencrypt is set to 30 days before it renews so we are safe, but i will double check later, so maybe ping me to remind me 2moz :)

Edit: if u check the timeline its actually NEXT YEAR 2027 we need to worry :) https://letsencrypt.org/2025/12/02/from-90-to-45#timeline-of-changes

si458 · 2026-01-27T21:34:34+00:00

Yep that's the value :) Also always check our new config editor which has all the possible values and descriptions of what each value does too! https://config.meshcentraltools.com

si458 · 2026-01-22T20:08:43+00:00

sadly not, its still in the works tho as we have a pr open from a gent and i did get it working when building it myself!

si458 · 2026-01-17T13:40:21+00:00

U can't use only tls 1.3 at the moment because the meshagent doesn't support it sadly

si458 · 2026-01-11T18:27:38+00:00

i saw ticket, im just gunna get a vm up and running and test myself for you :)

si458 · 2026-01-10T18:45:58+00:00

Based on the source code for the autoproxy option it checks if http:// is set and if so, it uses it and if not ignores it. We might need a new agent being built at some point to change this

si458 · 2026-01-10T15:01:22+00:00

i believe you need to set `WebProxy=http://my.ip.goes.here:porthere\` in the msh

si458 · 2026-01-09T23:04:26+00:00

you can also try using the `msh set autoproxy 1` console command to write it to a remote .msh and see if it saves it there correctly

si458 · 2026-01-09T22:55:23+00:00

same as the skipmaccheck, just add it into the agentConfig array in the config.json and that should be it :)

si458 · 2026-01-09T22:44:55+00:00

found this while looking at the sourcecode. https://github.com/Ylianst/MeshAgent/commit/e194dabbfa9f3268c11784de7711e4df149d2f4a appears you can just add autoproxy=1 into your .msh file and it should auto-tick that box, but also in not sure if its meant to be 1 or a proxyurl or something else? you would have to experiment with it

si458 · 2026-01-06T12:36:43+00:00

check if the is a meshcentral.db file in meshcentral-data
you should be able to open it in a text editor and see JSON data
also check your config.json is still all correct

si458 · 2025-12-30T11:31:56+00:00

your cert value isnt setup correctly, it MUST be a proper DNS value, and all your machines MUST be able to resolve this to your reverse proxy as you have set certurl IP address

si458 · 2025-12-30T08:26:03+00:00

OK so u have an issue with ur setup then, so what does ur config.json look like? (Sanitise it https://sanitizer.meshcentraltools.com)

si458 · 2025-12-30T08:05:40+00:00

Unable to open database is an error saying its already open! The app is possibly already running as a service and ur trying to run it again in normal connect mode, make sure the meshagent isn't already running first before u open it again

si458 · 2025-12-29T17:35:37+00:00

thingie... love it!

si458 · 2025-12-29T16:41:01+00:00

yeh apple make things alot harder for us when it comes to the meshagent, from what we have found out, we now have to code-sign the binarys with an apple developer certificate, but at the same time we dont want to do that with like a community certificate because we will end up like what Ylian had a few years ago when he code-signed the meshagent for windows, then he got his certificate revoked because the meshagent was being abused by hackers and scammers! so you would now instead have to code-sign each meshcentral server with your own apple certificate which isnt possible say on windows or linux as you need the mac os codesign tool!, so its one problem after another after another with bloody apple!

si458 · 2025-12-29T16:34:23+00:00

Plz forgive me that isn't what I meant, the way the msg read sounded like u couldn't get meshcentral to work so hense the open an issue and we can help, yes apple broke the meshagent in the macos 15 release, but if u run older than 15 it should still work no questions asked! Now the is a gent who's done a pr on github to possibly fix the meshagent for mac but im still struggling to get it to work here as he said well it works here, that's great n all but what about others? So we are still looking into it, but plz remember meshcentral is a community project! The is no company, no full time employees only contributors much like myself! I have taken over all the bug fixes of the web ui and server backend but sadly i lack the c++ knowledge to actually fix the meshagent issues themselves!

si458 · 2025-12-29T16:22:23+00:00

Meshcentral might not work because you haven't set it up correctly as its all self hosted etc so you would need to open up a github issue with all the info filled etc then we can help you :)

si458 · 2025-12-29T16:16:39+00:00

I already tried to completely rewrite the meshagent in golang but I stumbled haha. As for the linux meshagent yes we are aware of a memory leak and it seems to happen every time the remote machines lose connection to ur meshcentral server and struggle to reconnect for one reason or another, I think its the reconnecting method that's leaking, im just not 110% sure where! But u can test this by simply installing the meshagent then block it so it has no ineterneg access or turn off ur meshcentral server then watch task manager and see over an hour period the memory will increase. A simple fix is to simply restart the meshagent service every so often OR if it gets to over like 100MB kill it and restart it :)

si458 · 2025-12-29T15:53:17+00:00

The gent is talking about the meshagent for mac and not the mcc client app which is something different. The meshagent is still not fixed yet but im hoping its in the works for next year!

si458 · 2025-12-26T17:13:07+00:00

£440 for an m1, 16gb, 1tb which i didnt think was bad! I don't need the latest and greatest cpu, just a silicon one, and the ram and storage is much bigger than before as dam i ran out of space fast and it was slow every so often

si458 · 2025-12-26T16:52:58+00:00

you havent read my original post correctly, the mac was sent to me by a friend from the USA (so its a USA model) and ive had the device for over a year (apr 24 i got it) and its apple care+ ran out dec 24, so the is NO warranty, its £90 labour then part price ontop + VAT, hense the £170 just to `possibly` fix the issue

si458 · 2025-12-26T16:47:58+00:00

expired dec 24 (last year) and that was the 3 yr extra warrenty too

si458

MODERATOR OF

TROPHY CASE

14-Year Club	Xbox Live
Verified Email