Masternodes v0.12.3.3

[Serzh]

Hey. Help is needed.
After masternode is updated to v0.12.3.3, it is not synchronized.

Spoiler: masternode is not synced yet, skipping inbound connection attempt

2018-09-19 19:19:01 CMasternodeSync:rocessTick -- nTick 1399 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2018-09-19 19:19:07 CMasternodeSync:rocessTick -- nTick 1405 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2018-09-19 19:19:13 CMasternodeSync:rocessTick -- nTick 1411 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2018-09-19 19:19:19 CMasternodeSync:rocessTick -- nTick 1417 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2018-09-19 19:19:25 CMasternodeSync:rocessTick -- nTick 1423 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2018-09-19 19:19:31 CMasternodeSync:rocessTick -- nTick 1429 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2018-09-19 19:19:37 CMasternodeSync:rocessTick -- nTick 1435 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2018-09-19 19:19:43 CMasternodeSync:rocessTick -- nTick 1441 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000

v0.12.3.2 worked fine.
What to do?

 

[splawik21]

On your remote do this:
dash-cli addnode 52.14.192.211 onetry

Took the IP from already updated node.
This will solve the problem.