If this is an older droplet it is very possible that it was using an old managed kernel. Since the configuration that tells your droplet where to look for the kernel and how to boot is within your droplet, when you rebooted it attempted to look for a service that was discontinued a while ago. This guide, specifically the “Setting Up the Droplet for Internal Kernel Mangement” should help you to resolve this issue.