I have been using a dedicated server at OVH for a few years now, and the quality of their
service has become worse and the last incidents prompted me to look for a new server.
Digital Ocean claims that they are user-friendly and since it is quite cheap, I just gave it a try.
Subscribing, setting up 2 factor authentification, starting a droplet was a blast. I picked Archlinux, and less than one minute after, my droplet was up and running.
The Arch image is quite old (June 2013) and updating the system is a little more tricky
than just running
These instructions were written a few hours after the installation, so they may be slightly inaccurate.
First, update the whole system. Because Arch
/usr/lib, you cannot just run
pacman -Syu. Run instead:
pacman -Syu --ignore filesystem,bash pacman -S bash pacman -Su
netcfg and install
pacman -R netcfg pacman -S netctl
ip addr to see your interface. In my case it was
Create a config file
Interface=enp0s3 Connection=ethernet IP=static Address=('<droplet_ip>/24') Gateway='<gateway>' DNS=('220.127.116.11', '18.104.22.168')
Enable the interface
netctl enable enp0s3
Then update the kernel via the web interface.
The network interface is going to change to something like
/etc/netctl/ens3 and change the
/lib/systemd/system/sshd.service to be sure that the ssh daemon doesn’t
fail on boot
[Unit] Description=OpenSSH Daemon Wants=sshdgenkeys.service #After=sshdgenkeys.service After=network.target [Service] ExecStart=/usr/bin/sshd -D ExecReload=/bin/kill -HUP $MAINPID KillMode=process Restart=always [Install] WantedBy=multi-user.target
Reboot and your server should be up to date.
And that’s it for updating Arch. It was not the easiest updates, but nothing impossible. It would have been nice if Digital Ocean was provided an up to date Arch image though.
Note: You can probably directly set the network interface to
In the worst case you can still access your machine with Digital Ocean’s web shell and fix things there.