I finally got 1.7.0.2 to sync after many retries and experiments.

I think it may be due to one of the default nodes still being stuck at 83111   (addnode=107.170.217.4 ... this was yesterday)
It appeared that  my cleanwatercoin client was using this node, since it also kept getting stuck at 83111.

I moved wallet.dat somewhere else, and removed everything except cleanwatercoin.conf from my  ~/.cleanwatercoin directory
Removed all 'addnode=' lines and added
seednode=204.246.67.106:9340
(thanks doabitofgood.com)

Started up cleanwatercoin, and let it start syncing.
after a bit, I did:
cleanwatercoind getpeerinfo

107.170.217.4 was still on block 83111, and a couple others were not on the latest block. The rest were 84??? somethin..

Then stopped cleanwatercoin (well before block 83111), and changed cleanwatercoin.conf
to add connect= entries for all of the peers that were on the latest block..
Which resulted in:
connect=5.49.122.87:53591
connect=212.89.239.20:53591
connect=204.246.67.106:53591
connect=108.47.87.216:53591
connect=94.194.116.119:53591

Then I restarted cleanwatercoin-qt and it successfully synced to the latest block.
Stopped it again, removed the connect= entries, put my wallet.dat back, and it's all good...

Good luck,
-Free

We've had to unfortunately reboot your Droplet node3 due to an issue on the underlying physical node where the Droplet runs. We are investigating the health of the physical node to determine whether this was a single incident or systemic. If you have any questions related to this issue, please send us a ticket.