 |
VOOZH | about |
|
VOOZH | about |
When you first create a new Ubuntu 14.04 server, there are a few configuration steps that you should take early on as part of the basic setup. This will increase the security and usability of your server and will give you a solid foundation for subsequent actions.
Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases.
When creating a new Ubuntu 14.04 server, there are some basic steps that you should take to ensure that your server is secure and configured properly. This tutorial series covers connecting to your server and general security best practices, and provides links to articles that will help you start running your own web server or application.
Browse Series: 2 tutorials
This tutorial series helps sysadmins set up a new web server using the LEMP stack, focusing on Nginx setup with virtual blocks. This will let you serve multiple websites from one Droplet.
You’ll start by setting up your Ubuntu 14.04 server and end with multiple virtual blocks set up for your websites. An Nginx configuration guide is included at the end for reference.
Former Senior Technical Writer at DigitalOcean, specializing in DevOps topics across multiple Linux distributions, including Ubuntu 18.04, 20.04, 22.04, as well as Debian 10 and 11.
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!
When I try to restart the SSH server after some modifications I get this error:
General Parameters: Pool Handle = EchoPool Reregistration Interval = 30.000s Local Addresses = { all } Runtime Limit = off Policy Settings Policy Type = RoundRobin Load Degradation = 0.000% Load DPF = 0.000% Weight = 0 Weight DPF = 0.000% 20-Apr-2014 01:51:53.0852: P3130.7f57bfb19780@stuff rserpoolsocket.c:354 doRegistration() 20-Apr-2014 01:51:53.0857: Error: (Re-)Registration failed: no registrar available Registration: Identifier = $62292d97
Plus, my shell prompt become’s locked and I have to reconnect.
This is with a fresh copy of Ubuntu 14.04 installed minutes ago.
Fred
It seems that denyhosts is marked unmaintained for 14.04.
I think you meant to say under Step Four:
“replacing “demo” with the user you created:”
@Dustin Fixed. Thanks for catching that!
@Rick Roberts: Right, denyhosts has been dead upstream for awhile, and Ubuntu and Debian have decided to stop providing it. Check out:
You should use fail2ban. I’ll remove the link to denyhosts above. Thanks!
If anyone following step 5 gets stuck with a “Connection refused” error (like I did), there may be a typo in your config file. While still logged in as root in your other terminal window, you can run the following to test the ssh config file for issues:
sshd -T
If there is an issue with a config file, it will tell you which one and on what line.
If you logged out for some reason, you can use DO’s console access to log in and fix any issues.
Cheers
I have followed this tutorial and it is all working, but now I have followed the sftp tutorial too and it keeps checking port 22. With this tutorial I changed that port “to something in between 1025 and 65536”, so my question is: how do I know get SFTP to work?
Piet:
If you’ve changed the port that SSH operates on, you can tell the sftp command or your file transfer client the new port you selected.
If you are running from the command line, you can specify a non-default port like this. If the port you selected is 4444, the command would look like:
sftp -P 4444 username@server.com
If you are using an (S)FTP client to connect to the server, you can input the new port in the options. For instance, in Filezilla, there is a field on the right-hand side labeled “Port” as you can see here:
https://i.imgur.com/4FBl4vX.png
Let us know if that works for you or not.
I may be missing something, but if the point is to make it more secure by removing roots access, and giving another user the permissions… haven’t we just chased our own tail?
We’re exactly where we started, except that it’s now also a username they need to know.
@drphilbobaggins: Having to guess the username is surprisingly helpful when it comes to server security. Run a server for long enough, and you’ll see many brute force attempts to SSH into the root account. So if you don’t want to disable the root user, at least create a new user and set PermitRootLogin to no in your SSH configuration.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
