One place for hosting & domains


      What Is a VPS? A Beginner’s Guide to Virtual Private Servers

      If you are finally ready to get your website up and running, it’s probably safe to say you’re looking into purchasing web hosting. And it’s a battlefield out here for beginners. There’s a glossary of new terms — what is a kernel?! — and acronyms seemingly dropping from the sky. One that you’ll hear a lot: VPS hosting.

      But fret not, beginner. This guide will answer all your burning Virtual Private Server questions:

      Ready to learn everything there is to know about a VPS hosting environment? Let’s dive in!

      What Is a Virtual Private Server?

      First, let’s define what VPS actually stands for — virtual private server.

      In layman’s terms, a server is a powerful computer that stores all of the data and files that make up your website. When someone types your domain name into their web browser, that powerful computer “serves up” your website to the searcher’s screen.

      Now for the virtual aspect: VPS uses virtualization technology to split that one powerful server we just talked about into multiple virtual servers. Think of it this way: it’s one piece of physical hardware that functions like several separate servers.

      The word private means just what it implies. Your virtual server is reserved for you, so you won’t have to share RAM, CPU, or any data with other users.

      How Does VPS Work?

      VPS Hosting simulates the experience of a dedicated server even though you’re still sharing the physical server with other users.

      Your web hosting provider installs a virtual layer on top of the operating system (OS) of the server using virtualization technology. Separating the server into individual compartments with virtual walls, this layer allows each user to install their own OS and software.

      Because a VPS separates your files from other users on the OS level, it truly is a private server. This means your website lives within a secure container with guaranteed server resources — think memory, disk space, CPU cores, etc. You don’t have to share any of it with others.

      How VPS Compares with Shared Hosting & Dedicated Hosting

      To truly understand how VPS works, it’s important to get familiar with some of the basics of web hosting, including other common plans. Here’s a brief breakdown of the differences between shared, dedicated, and VPS hosting.

      1. Shared Hosting

      Shared hosting is the most common form of web hosting and works well for many new website owners. When you purchase a shared hosting plan, you’re sharing key resources like CPU, RAM, and hard drive space with other website owners using that same server.

      Let’s use an analogy to make understanding this concept a little easier.

      Think of a shared server as a large apartment complex, and all of the individual apartments are rented by other website owners. All of you need a place to live — just like your website’s files — but going out to buy a huge family home would be too expensive for your needs. Sharing common areas and utilities in an apartment block helps keep costs down. And the same is true for shared hosting.

      There are a few downsides to shared hosting, though, mostly because you’re sharing. For instance, if someone else on your shared server has a huge spike in traffic, that could affect your website’s performance. However, if you’re just getting your website off the ground and don’t have huge traffic volume, shared hosting is a great way to get online!

      Looking for an entry-level plan? Check out our affordable shared hosting packages.

      2. Dedicated Hosting

      Dedicated hosting is the opposite of shared hosting. Rather than pooling resources (and sharing the costs) with other website owners, you have one dedicated server that is reserved for your website only.

      Sounds great, right? The catch is that it’s more expensive, but you get 100% control over your resources and can customize the software to meet your individual needs. This type of hosting package is best for websites with robust technical demands. For example, dedicated hosting could be right for you if:

      • you are getting large amounts of traffic each day.
      • you need to install your own operating system.
      • you are handling thousands of financial transactions.
      • your website requires custom software.

      Need a powerful solution? Check out our dedicated hosting plans.

      3. VPS Hosting

      VPS hosting sits squarely between shared and dedicated. When you choose VPS, there will be other websites hosted on the same hardware as yours (remember that powerful server we talked about earlier?).

      But — and it’s a big one — your website is the only domain allocated to your particular virtual compartment. And that means you get your own operating system, dedicated storage, powerful CPU, scalable RAM, and unlimited bandwidth.

      With a VPS, you are getting many of the benefits of a dedicated server — for an affordable price. In short, VPS hosting can give you more bang for your buck.

      We Know You’ve Got Lots of VPS Options

      At DreamHost, we’ve never been comfortable fitting in with the crowd. Here are a few ways our VPS offering stands apart: 24/7 customer support, an intuitive panel, scalable RAM, unlimited bandwidth, and SSD storage. Plans start at $10/mo.

      When Should You Switch to VPS?

      The best way to evaluate whether or not you need to upgrade to VPS is to take stock of your website. Here are eight tell-tale signs it’s time to go virtual.

      1. You’re Worried About Security

      If you need enhanced security features, advanced monitoring capabilities, more backup space, improved website reliability, or plan on taking any form of online payment, then you may want to consider VPS. With VPS, you get reliable resources and can count on top-notch security features.

      2. You Start to Experience High Traffic Volumes

      If you are just starting your website and don’t receive very much traffic, then shared hosting is the ideal solution. However, if your website’s audience is consistently growing, you’ll want to consider upgrading. You don’t want to run the risk of your website running slowly or, even worse, your server crashing because it can’t handle the traffic. If you anticipate an increase in visitors, do yourself a favor and switch to VPS.

      3. Your Website is Consistently Running Slowly

      Shared hosting is not meant for websites that use large amounts of RAM. As your website grows and you add more and more content, you will start to see a decrease in your website’s load times. As soon as this happens, it’s an indication that you are maxing out your limits. Upgrading to a VPS will enable you to scale your website without having to worry about slow load times.

      4. You Have An Online Store

      The moment you plan on running an online store is the moment you should upgrade your hosting plan. Why? Because with VPS, you have a secure and dedicated virtual server where you are more likely to pass a PCI compliance test. The Payment Card Industry Data Security Standard was established by major credit card brands to protect against cardholder data theft.

      If you are accepting credit cards on your website via a payment gateway, you want to do everything you can to ensure the safety of your consumers’ financial information. Since VPS is more secure than shared hosting, it’s the better option for ecommerce websites.

      5. You Need To Install Custom Software

      Shared hosting is great for website owners who build their site with WordPress or other common Content Management Systems. However, if you reach the point where you need to install custom software, use a custom server configuration, or engage in any other advanced programming, then you’ll want a hosting option that affords you more control.

      Similarly, several standard tax, billing, bookkeeping, and other integrative programs require around-the-clock server availability as well as high-speed internet. To run these applications successfully, you’ll need either a VPS or dedicated hosting account.

      If you operate on a shared server, you’ll only run into frustration when you learn advanced actions are forbidden or that apps don’t have the support needed to function properly. Instead of dealing with this potential problem, upgrade to VPS hosting and immediately gain more control over your programming actions.

      6. You Run Into Server Errors

      Do you encounter “Service Unavailable” errors, any 50X errors, or the “Internal Server Error” often? When you see errors, it’s likely that your potential customers are too. While you can troubleshoot downtime issues, there is simply no room for server errors if you’re running an online business. Pre-empt this problem by upgrading to VPS.

      7. You’re on a Budget

      While it’s true that a dedicated hosting package can address many of the problems on this list, it’s important to remember that a dedicated plan is a much pricier option. If you need to improve your bandwidth, increase your security, and get more RAM, then the most affordable option is to opt for VPS hosting.

      8. You Build Websites For Your Clients

      Is it part of your job to build websites for your clients? With a VPS, you can host an unlimited number of domains all while making sure you have enough RAM for each site to function properly.

      What Is VPS?

      Good question! We regularly report on all things web hosting and tech. Subscribe to our monthly newsletter so you never miss an article.

      How to Choose the Best VPS Hosting Plan for Your Website?

      Now that you know what a VPS is and when you should upgrade, let’s talk about what makes a great VPS plan and how to find the best web hosting provider. After all, you wouldn’t trust your website with just anybody, right?

      Self-Managed Versus Managed VPS Services

      When selecting VPS hosting, you usually have two plan options:

      1. Self-managed VPS service (sometimes called unmanaged VPS)
      2. Managed VPS service

      You need to be familiar with server administration, troubleshooting, and managing the applications, software, and services installed on your VPS if you choose a self-managed service.

      If you are either unfamiliar with these admin skills or you just want your hosting company to take care of it for you, then opting for a managed VPS plan is the way to go.

      All of DreamHost’s VPS plans are fully managed, meaning you can skip worrying about the nitty-gritty technical details and focus on what really matters: creating great content for your website. If you’re looking for root access, though, consider opting for DeamHost’s cloud hosting.


      You might think this tip might fall into the obvious category, but it’s worth sharing: Make sure the hosting package you select is compatible with your operating system. DreamHost, for instance, doesn’t offer Windows hosting since most of our users prefer to run a Linux VPS.


      The VPS hosting service you select should have uptime ratings of 99.5% and above. Anything lower from your web host is simply unacceptable. For the record, DreamHost boasts one of the industry’s highest uptime scores at 99.98%. Stop it, we’re blushing.


      When purchasing a VPS hosting package, make sure your service provider offers the latest and greatest in hardware, including solid state drives (SSD) — the fastest storage technology. SSD makes running high-speed applications easier thanks, in part, to the lack of moving parts.

      24/7 Customer Support

      When it comes down to it, you simply don’t know when you’ll experience a site meltdown. So make sure you purchase a VPS hosting package from a company that offers 24/7 customer support.

      Backup Service

      Imagine you are revamping your site when something goes wrong and you lose everything because you forgot to backup your site. Shivers. This is an all-too-common occurrence, and it can cost you money, time, and more than a few gray hairs. Make sure when you purchase VPS service, you choose a provider that makes backups easy.

      Ready for Your Own Private Server?

      Made it all the way to the end of this guide? Well, pat yourself on the back because you are a VPS beginner no more!

      What it all boils down to is this: If your website is growing and beginning to attract some well-deserved attention, you’ll want its performance to keep pace. And that means it’s time to increase your site’s resources by upgrading to a VPS server.

      While VPS hosting is more expensive than a shared plan, the benefits of this kind of hosting solution give you a lot of bang for your buck – without having to spring for a much-pricier dedicated hosting plan. Wondering which VPS host to choose? Consider DreamHost! Our VPS plans start at just $10/mo.

      Source link

      How To Manage Remote Servers with Ansible eBook

      Download the Complete eBook!

      How To Manage Remote Servers with Ansible eBook in EPUB format

      How To Manage Remote Servers with Ansible eBook in PDF format

      Introduction to the eBook

      This book is designed to introduce you to using Ansible to manage your servers. You’ll learn how to install and configure Ansible on a control node, and then how to use it to configure and run commands on remote servers. You’ll also learn how to collect tasks into complete Playbooks to automate server setup from start to finish.

      This book is based on the How To Manage Remote Servers with Ansible tutorial series found on DigitalOcean Community. The topics that it covers include how to:

      1. Become familiar with configuration management tools and processes, and the benefits of using them to manage your infrastructure.

      2. Install and configure Ansible on an Ubuntu 20.04 control node, ensuring that your servers are properly set up and that you are able to execute remote instructions through Ansible.

      3. Build inventory files and organize your servers into groups to selectively control how and where Ansible commands are run.

      4. Run Ad Hoc commands to execute individual tasks on one, or multiple remote servers.

      5. Package individual commands into Playbooks that you can use to automate the provisioning of multiple servers, and how to run specific sets of tasks in Playbooks using tags.

      Each chapter is usable on its own as a reference, or as part of a progressive guide to learning how to manage your servers with Ansible. If you’re familiar with a topic, or are more interested in a particular section, feel free to jump to the chapter that best suits your purpose.

      Download the eBook

      You can download the eBook in either the EPUB or PDF format by following the links below.

      Download the Complete eBook!

      How To Manage Remote Servers with Ansible eBook in EPUB format

      How To Manage Remote Servers with Ansible eBook in PDF format

      Source link

      How To Manage Multiple Servers with Ansible Ad Hoc Commands


      Ansible is a modern configuration management tool that facilitates the task of setting up and maintaining remote servers. With a minimalist design intended to get users up and running quickly, it allows you to control one to hundreds of systems from a central location with either playbooks or ad hoc commands.

      Unlike playbooks — which consist of collections of tasks that can be reused — ad hoc commands are tasks that you don’t perform frequently, such as restarting a service or retrieving information about the remote systems that Ansible manages.

      In this cheat sheet guide, you’ll learn how to use Ansible ad hoc commands to perform common tasks such as installing packages, copying files, and restarting services on one or more remote servers, from an Ansible control node.


      In order to follow this guide, you’ll need:

      • One Ansible control node. This guide assumes your control node is an Ubuntu 20.04 machine with Ansible installed and configured to connect to your Ansible hosts using SSH keys. Make sure the control node has a regular user with sudo permissions and a firewall enabled, as explained in our Initial Server Setup guide. To set up Ansible, please follow our guide on How to Install and Configure Ansible on Ubuntu 20.04.
      • Two or more Ansible hosts. An Ansible host is any machine that your Ansible control node is configured to automate. This guide assumes your Ansible hosts are remote Ubuntu 20.04 servers. Make sure each Ansible host has:
        • The Ansible control node’s SSH public key added to the authorized_keys of a system user. This user can be either root or a regular user with sudo privileges. To set this up, you can follow Step 2 of How to Set Up SSH Keys on Ubuntu 20.04.
      • An inventory file set up on the Ansible control node. Make sure you have a working inventory file containing all your Ansible hosts. To set this up, please refer to the guide on How To Set Up Ansible Inventories. Then, make sure you’re able to connect to your nodes by running the connection test outlined in the section Testing Connection to Ansible Hosts.

      Testing Connection to Ansible Hosts

      The following command will test connectivity between your Ansible control node and all your Ansible hosts. This command uses the current system user and its corresponding SSH key as the remote login, and includes the -m option, which tells Ansible to run the ping module. It also features the -i flag, which tells Ansible to ping the hosts listed in the specified inventory file

      • ansible all -i inventory -m ping

      If this is the first time you’re connecting to these servers via SSH, you’ll be asked to confirm the authenticity of the hosts you’re connecting to via Ansible. When prompted, type yes and then hit ENTER to confirm.

      You should get output similar to this:


      server1 | SUCCESS => { "changed": false, "ping": "pong" } server2 | SUCCESS => { "changed": false, "ping": "pong" }

      Once you get a "pong" reply back from a host, it means the connection is live and you’re ready to run Ansible commands on that server.

      Adjusting Connection Options

      By default, Ansible tries to connect to the nodes as a remote user with the same name as your current system user, using its corresponding SSH keypair.

      To connect as a different remote user, append the command with the -u flag and the name of the intended user:

      • ansible all -i inventory -m ping -u sammy

      If you’re using a custom SSH key to connect to the remote servers, you can provide it at execution time with the --private-key option:

      • ansible all -i inventory -m ping --private-key=~/.ssh/custom_id

      Note: For more information on how to connect to nodes, please refer to our How to Use Ansible guide, which demonstrates more connection options.

      Once you’re able to connect using the appropriate options, you can adjust your inventory file to automatically set your remote user and private key, in case they are different from the default values assigned by Ansible. Then, you won’t need to provide those parameters in the command line.

      The following example inventory file sets up the ansible_user variable only for the server1 server:


      server1 ansible_host= ansible_user=sammy
      server2 ansible_host=

      Ansible will now use sammy as the default remote user when connecting to the server1 server.

      To set up a custom SSH key, include the ansible_ssh_private_key_file variable as follows:


      server1 ansible_host= ansible_ssh_private_key_file=/home/sammy/.ssh/custom_id
      server2 ansible_host=

      In both cases, we have set up custom values only for server1. If you want to use the same settings for multiple servers, you can use a child group for that:



      This example configuration will assign a custom user and SSH key only for connecting to the servers listed in group_a.

      Defining Targets for Command Execution

      When running ad hoc commands with Ansible, you can target individual hosts, as well as any combination of groups, hosts and subgroups. For instance, this is how you would check connectivity for every host in a group named servers:

      • ansible servers -i inventory -m ping

      You can also specify multiple hosts and groups by separating them with colons:

      • ansible server1:server2:dbservers -i inventory -m ping

      To include an exception in a pattern, use an exclamation mark, prefixed by the escape character , as follows. This command will run on all servers from group1, except server2:

      • ansible group1:!server2 -i inventory -m ping

      In case you’d like to run a command only on servers that are part of both group1 and group2, for instance, you should use & instead. Don’t forget to prefix it with a escape character:

      • ansible group1:&group2 -i inventory -m ping

      For more information on how to use patterns when defining targets for command execution, please refer to Step 5 of our guide on How to Set Up Ansible Inventories.

      Running Ansible Modules

      Ansible modules are pieces of code that can be invoked from playbooks and also from the command-line to facilitate executing procedures on remote nodes. Examples include the apt module, used to manage system packages on Ubuntu, and the user module, used to manage system users. The ping command used throughout this guide is also a module, typically used to test connection from the control node to the hosts.

      Ansible ships with an extensive collection of built-in modules, some of which require the installation of additional software in order to provide full functionality. You can also create your own custom modules using your language of choice.

      To execute a module with arguments, include the -a flag followed by the appropriate options in double quotes, like this:

      ansible target -i inventory -m module -a "module options"

      As an example, this will use the apt module to install the package tree on server1:

      • ansible server1 -i inventory -m apt -a "name=tree"

      Running Bash Commands

      When a module is not provided via the -m option, the command module is used by default to execute the specified command on the remote server(s).

      This allows you to execute virtually any command that you could normally execute via an SSH terminal, as long as the connecting user has sufficient permissions and there aren’t any interactive prompts.

      This example executes the uptime command on all servers from the specified inventory:

      • ansible all -i inventory -a "uptime"


      server1 | CHANGED | rc=0 >> 14:12:18 up 55 days, 2:15, 1 user, load average: 0.03, 0.01, 0.00 server2 | CHANGED | rc=0 >> 14:12:19 up 10 days, 6:38, 1 user, load average: 0.01, 0.02, 0.00

      Using Privilege Escalation to Run Commands with sudo

      If the command or module you want to execute on remote hosts requires extended system privileges or a different system user, you’ll need to use Ansible’s privilege escalation module, become. This module is an abstraction for sudo as well as other privilege escalation software supported by Ansible on different operating systems.

      For instance, if you wanted to run a tail command to output the latest log messages from Nginx’s error log on a server named server1 from inventory, you would need to include the --become option as follows:

      • ansible server1 -i inventory -a "tail /var/log/nginx/error.log" --become

      This would be the equivalent of running a sudo tail /var/log/nginx/error.log command on the remote host, using the current local system user or the remote user set up within your inventory file.

      Privilege escalation systems such as sudo often require that you confirm your credentials by prompting you to provide your user’s password. That would cause Ansible to fail a command or playbook execution. You can then use the --ask-become-pass or -K option to make Ansible prompt you for that sudo password:

      • ansible server1 -i inventory -a "tail /var/log/nginx/error.log" --become -K

      Installing and Removing Packages

      The following example uses the apt module to install the nginx package on all nodes from the provided inventory file:

      • ansible all -i inventory -m apt -a "name=nginx" --become -K

      To remove a package, include the state argument and set it to absent:.

      • ansible all -i inventory -m apt -a "name=nginx state=absent" --become -K

      Copying Files

      With the file module, you can copy files between the control node and the managed nodes, in either direction. The following command copies a local text file to all remote hosts in the specified inventory file:

      • ansible all -i inventory -m copy -a "src=./file.txt dest=~/myfile.txt"

      To copy a file from the remote server to your control node, include the remote_src option:

      • ansible all -i inventory -m copy -a "src=~/myfile.txt remote_src=yes dest=./file.txt"

      Changing File Permissions

      To modify permissions on files and directories on your remote nodes, you can use the file module.

      The following command will adjust permissions on a file named file.txt located at /var/www on the remote host. It will set the file’s umask to 600, which will enable read and write permissions only for the current file owner. Additionally, it will set the ownership of that file to a user and a group called sammy:

      • ansible all -i inventory -m file -a "dest=/var/www/file.txt mode=600 owner=sammy group=sammy" --become -K

      Because the file is located in a directory typically owned by root, we might need sudo permissions to modify its properties. That’s why we include the --become and -K options. These will use Ansible’s privilege escalation system to run the command with extended privileges, and it will prompt you to provide the sudo password for the remote user.

      Restarting Services

      You can use the service module to manage services running on the remote nodes managed by Ansible. This will require extended system privileges, so make sure your remote user has sudo permissions and you include the --become option to use Ansible’s privilege escalation system. Using -K will prompt you to provide the sudo password for the connecting user.

      To restart the nginx service on all hosts in group called webservers, for instance, you would run:

      • ansible webservers -i inventory -m service -a "name=nginx state=restarted" --become -K

      Restarting Servers

      Although Ansible doesn’t have a dedicated module to restart servers, you can issue a bash command that calls the /sbin/reboot command on the remote host.

      Restarting the server will require extended system privileges, so make sure your remote user has sudo permissions and you include the --become option to use Ansible’s privilege escalation system. Using -K will prompt you to provide the sudo password for the connecting user.

      Warning: The following command will fully restart the server(s) targeted by Ansible. That might cause temporary disruption to any applications that rely on those servers.

      To restart all servers in a webservers group, for instance, you would run:

      • ansible webservers -i inventory -a "/sbin/reboot" --become -K

      Gathering Information About Remote Nodes

      The setup module returns detailed information about the remote systems managed by Ansible, also known as system facts.

      To obtain the system facts for server1, run:

      • ansible server1 -i inventory -m setup

      This will print a large amount of JSON data containing details about the remote server environment. To print only the most relevant information, include the "gather_subset=min" argument as follows:

      • ansible server1 -i inventory -m setup -a "gather_subset=min"

      To print only specific items of the JSON, you can use the filter argument. This will accept a wildcard pattern used to match strings, similar to fnmatch. For example, to obtain information about both the ipv4 and ipv6 network interfaces, you can use *ipv* as filter:

      • ansible server1 -i inventory -m setup -a "filter=*ipv*"


      server1 | SUCCESS => { "ansible_facts": { "ansible_all_ipv4_addresses": [ "", "" ], "ansible_all_ipv6_addresses": [ "fe80::a4f5:16ff:fe75:e758" ], "ansible_default_ipv4": { "address": "", "alias": "eth0", "broadcast": "", "gateway": "", "interface": "eth0", "macaddress": "a6:f5:16:75:e7:58", "mtu": 1500, "netmask": "", "network": "", "type": "ether" }, "ansible_default_ipv6": {} }, "changed": false }

      If you’d like to check disk usage, you can run a Bash command calling the df utility, as follows:

      • ansible all -i inventory -a "df -h"


      server1 | CHANGED | rc=0 >> Filesystem Size Used Avail Use% Mounted on udev 3.9G 0 3.9G 0% /dev tmpfs 798M 624K 798M 1% /run /dev/vda1 155G 2.3G 153G 2% / tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup /dev/vda15 105M 3.6M 101M 4% /boot/efi tmpfs 798M 0 798M 0% /run/user/0 server2 | CHANGED | rc=0 >> Filesystem Size Used Avail Use% Mounted on udev 2.0G 0 2.0G 0% /dev tmpfs 395M 608K 394M 1% /run /dev/vda1 78G 2.2G 76G 3% / tmpfs 2.0G 0 2.0G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup /dev/vda15 105M 3.6M 101M 4% /boot/efi tmpfs 395M 0 395M 0% /run/user/0


      In this guide, we demonstrated how to use Ansible ad hoc commands to manage remote servers, including how to execute common tasks such as restarting a service or copying a file from the control node to the remote servers managed by Ansible. We’ve also seen how to gather information from the remote nodes using limiting and filtering parameters.

      As an additional resource, you can check Ansible’s official documentation on ad hoc commands.

      Source link