freebsd bad droplet.conf symlink after 10.3 upgrade

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 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.


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

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.

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.