@denisgomes Just a quick follow up…
Our Dev Team took a look further at this to be sure that it’s nothing on our end & has taken notice that one possible cause for that error could be when Object Cache causes a problem where the Dashboard gets information that the publickey value is set in DB while it’s actually not.
When the Dashboard hits the Child site to connect, Child gets information served from the Object-Cache where the publickey is already set, but in fact, the field is empty in the DB…
During our research, we have not found a way in PHP to programmatically skip the object cache, therefore the only way past this is to either clear the object cache & or deactivate/activate the Child Plugin.
We will continue to monitor this caveat and if we find a solution around that behavior we will be sure to include it in a future release.