By b4c5af3e867
After upgrading to 10.3 (freebsd-update style), my /etc/rc.digitalocean/droplet.conf is symlinked to “.conf” instead of “<droplet>.conf”. the quick fix was to copy my “<droplet>.conf” to “.conf” and reboot.
Why isn’t /etc/rc.d/digitalocean grabbing my droplet id from http://169.254.169.254/metadata/v1/id and creating the symlink? it times out such that DROPLET_ID is an empty string and thus the “.conf” symlink.
i compared my /etc/ files with a brand new 10.3 droplet and i didn’t see any noticeable differences.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
That is a good question and one we’ll look into. Since this question was originally posted we have provided a 10.3 image as well as made several updates to our base image creation and deployment process.
I did an in-place upgrade from 10.2 to 10.3 and it died after reboot with no network. After 3 days of agony, I contacted support and was told to update the main rc.conf with the xxxxx.conf. Now it’s working.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.