Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

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!
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.
Accepted Answer
You could also add following code to wp-config.php to gain access to WordPress backend,
define('FORCE_SSL_ADMIN', true);
if ($_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https')
$_SERVER['HTTPS']='on';
Also I added the domain name in my Digital Ocean account and created an A (@) record pointing to the Wordpress droplet, as well as a www CNAME record aliasing that A (@) record.
Was that the correct thing to do?
After going through the steps above which restored access to the back end of my Wordpress site, I found the following:
I deleted the domain name entirely from my Digital Ocean account - it was causing excess redirects, and was not necessary. Only the Cloudflare DNS settings are necessary which point the domain (and the www version) to the IP address of the Wordpress droplet on Digital Ocean.
Then (again using FileZilla as above) I changed the URLs in wp-config.php to:
define('WP_HOME','http://your-site.com');
define('WP_SITEURL','http://your-site.com');
(removing the www from both of the URLs)
Everything now still works (including the admin login page at /wp-admin), and without the extra DNS re-directs.