how to share access to a droplet [Apache]

Posted March 3, 2020 840 views
DigitalOcean Accounts

how to share access to a droplet [Apache]

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.

Submit an Answer
3 answers

Hey @dcayce, if you are using a Team Account you can invite someone to join your Team ( which will give them access to your account.

If you’re just wanting to give them SSH access to the Droplet, here’s a guide on how to do that (if the Droplet is already created):

If the Droplet is yet to be created, you can add other SSH keys during the Droplet create moment.

Hopefully that answers your question, but let me know if not.

There are a couple different layers to address this one. If you are only wanting to share access to your CMS (think WordPress), you will want to refer to the documentation for that specific application. I’ve linked that of WordPress here.

If you want to share access to the Droplet, you will want to consider the level of access you want to provide. In any case, it is recommended that you do not share access to the root user. With that in mind, we have some great documentation available on Adding and Removing Users.

For a little more context, we also have a guide on setting up SFTP users. If you are wanting to provide full SSH access to the other users, this Q&A post may come in handy.

by Melissa Anderson
by Kathleen Juell
FTP, short for File Transfer Protocol, is a network protocol that was once widely used for moving files between a client and server. It has since been replaced by faster, more secure, and more convenient ways of delivering files. In this tutorial, we'll show you how to configure vsftpd to allow a user to upload files to his or her home directory using FTP with login credentials secured by SSL/TLS.

I’m using an Apache server so the setup is slightly different than yours, though still easy to sort through. It turns out this was a simple problem within the app where an address was incorrect, and not a server problem at all!
The use of <VirtualHost> does not affect what addresses Apache httpd listens on. You may need to ensure that Apache httpd is listening on the correct addresses using Listen.