Add an SSH user to Digital Ocean - Revision history

Kyle.Madsen: /* = Troubleshooting */

2024-10-08T20:04:13Z

= Troubleshooting

← Older revision		Revision as of 20:04, 8 October 2024
Line 24:		Line 24:
	=== Troubleshooting ==		=== Troubleshooting ==
	SSH errors		SSH errors
			:Change /etc/ssh/sshd_config
	Change /etc/ssh/sshd_config		::permitRootLogin yes
			:::back to no
	permitRootLogin yes		::AllowUsers test username

	back to no

	AllowUsers test username

Kyle.Madsen at 20:03, 8 October 2024

2024-10-08T20:03:08Z

← Older revision		Revision as of 20:03, 8 October 2024
Line 24:		Line 24:
	=== Troubleshooting ==		=== Troubleshooting ==
	SSH errors		SSH errors

	Change /etc/ssh/sshd_config		Change /etc/ssh/sshd_config

	permitRootLogin yes		permitRootLogin yes

	back to no		back to no

	AllowUsers test username		AllowUsers test username

Kyle.Madsen at 20:02, 8 October 2024

2024-10-08T20:02:50Z

← Older revision		Revision as of 20:02, 8 October 2024
Line 21:		Line 21:
	## create a new file with "username" as the title and the content of the authorized_keys file created above.		## create a new file with "username" as the title and the content of the authorized_keys file created above.
	# This should allow the user to login via SSH as long as they have the matching private key in their local SSH folder and know the associated password.		# This should allow the user to login via SSH as long as they have the matching private key in their local SSH folder and know the associated password.

			=== Troubleshooting ==
			SSH errors
			Change /etc/ssh/sshd_config
			permitRootLogin yes
			back to no
			AllowUsers test username

Kyle.Madsen at 01:54, 12 June 2023

2023-06-12T01:54:57Z

← Older revision		Revision as of 01:54, 12 June 2023
Line 5:		Line 5:
	# Create a new user		# Create a new user
	## <code>sudo su</code>		## <code>sudo su</code>
	## <code>adduser "username" ~~--disabled-password~~</code>		## <code>adduser "username"</code>
	# Add the new user to the sudo group		# Add the new user to the sudo group
	## <code>usermod -aG sudo "username"</code>		## <code>usermod -aG sudo "username"</code>

Kyle.Madsen: Created page with "== Add an SSH enabled user to Digital Ocean == === Steps to build the local account and allow SSH connection === # Generate an SSH key pair. # Log into the server via already..."

2023-06-06T17:50:04Z

Created page with "== Add an SSH enabled user to Digital Ocean == === Steps to build the local account and allow SSH connection === # Generate an SSH key pair. # Log into the server via already..."

New page

== Add an SSH enabled user to Digital Ocean ==
=== Steps to build the local account and allow SSH connection ===
# Generate an SSH key pair.
# Log into the server via already established SSH user.
# Create a new user
## <code>sudo su</code>
## <code>adduser "username" --disabled-password</code>
# Add the new user to the sudo group
## <code>usermod -aG sudo "username"</code>
# change to new user to create and give folders correct permissions
## <code>sudo su - new_user</code>
## <code>mkdir /home/"username"/.ssh</code>
## <code>chmod 700 /home/"username"/.ssh</code>
## <code>touch /home/"username"/.ssh/authorized_keys</code>
## <code>chmod 600 /home/"username"/.ssh/authorized_keys</code>
# Copy the text of the .rsa file to the new authorized_keys file.
## The above is best practice but does not seem to work on our servers. Below are the extra steps to allow a user to authenticate via ssh.
# Become root sudo user again
## <code>sudo su</code>
# Navigate to <code>/etc/ssh/authorized_keys</code>
## create a new file with "username" as the title and the content of the authorized_keys file created above.
# This should allow the user to login via SSH as long as they have the matching private key in their local SSH folder and know the associated password.