That's strange. I've been running a tMasternode all this time on a server using the daemon, and had no problems. I just tried updating to the latest version, and I got this:
not capable masternode: Can't detect external address. Please use the Masternodeaddr configuration option.
Edit: I went straight to masternode debug to see if my masternode would automatically start, and seeing that ^^^ figured there was something wrong with my MN not having a single 1000 entry anymore. Despite that notice, though, my masternode started when I did dash-cli masternode start. So it didn't start automatically, but it did start![Smile :) :)](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
not capable masternode: Can't detect external address. Please use the Masternodeaddr configuration option.
Edit: I went straight to masternode debug to see if my masternode would automatically start, and seeing that ^^^ figured there was something wrong with my MN not having a single 1000 entry anymore. Despite that notice, though, my masternode started when I did dash-cli masternode start. So it didn't start automatically, but it did start