I have gotten busy again. Then I got a chance to take a vacation. I am still trying to figure this out. I have tried to move to a solution, but haven’t gotten far. I am now running MeshCentral Version 1.0.10.
I have a new screen shoot of log with what is now happening after updating MeshCentral from your update you put in.
Not sure if this will help.
Thanks, it was a bug, I think due to copy/paste between meshcentral and meshcentral-light.
Meshcentral 1.0.11 released, see Release 1.0.11 · mrmarkuz/ns8-meshcentral · GitHub
So I did the update to 1.0.11. Here is what I am getting now in the logs for MeshCentral. I still don’t see they connection between pc and MeshCentral. (all pc’s are greyed out) I am still unsure what to do next. But it looks like it may have something to do with the web cert. per logs… of course I am not sure. Still need others help on this one…
It seems the cert doesn’t match to the clients anymore. I’m going to recheck…
Is this something that I need to adjust on my side or is this on the github side of things?
No, I need to recheck the migration. I’ll report my findings.
Hi all,
i now finaly have time to upgrade my home net and in preparation i also will upgrade my old NS7 Meshcentral server to the latest NS8 version is the Migration now stable for Meshcentral?
Unfortunately not but there’s a script to update the certificate, see Accessing TLS certificates - #6 by Turbond
I need to test it in the migration procedure.
EDIT:
I found that the migration is working when the FQDN is the same on NethServer 8.
I tested it more times and sometimes I needed to copy the data files twice to make it work but I’m not sure if it’s really necessary or if I just was too impatient…
thanks i have 4 weeks of vacation so i hope “plenty” of time to upgrade my systems had some hardware recovery so i replace older systems with newer ones and i plan to go through every system and rebuild most of them.
Will see if i get stuck currently with the old ns7 version i just create the certs on my meshcentral server and then copy them to the reverseproxy which is also a ns7 that worked flawles so will see how the new setup works
