There is a weird thing when setting up a Masternode that should be changed I guess, as it doesn't make much sense. After starting a hot wallet on Linux VPS, after it successfully loads all blocks it returns:

2019-12-19 13:27:58 ProcessNewBlock : ACCEPTED Block 2126550 in 6 milliseconds with size=983
2019-12-19 13:27:58 CActiveMasternode::ManageStatus() - not capable: Hot node, waiting for remote activation.

However, if you try to start the Masternode from remote (controller) wallet right after that message, it will NOT start successfully, it will probably get stuck or even freeze the wallet so it needs a restart. Or even worse, you might end up needing to create a whole new masternode.

Why is the wallet returning this message "Hot node, waiting for remote activation.", if the ONLY right message when masternode should be started from remote wallet is:

2019-12-19 13:31:01 CMasternodeSync::GetNextAsset - Sync has finished
2019-12-19 13:31:01 CActiveMasternode::ManageStatus() - not capable: Hot node, waiting for remote activation.