Hello There, Guest! Login Register


Thread Rating:
  • 1 Vote(s) - 4 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[Beginner] 3 Things you have to do before you use your VPS!
#1
Hey Guys! Wink

This is an Thread for beginners with Linux or VPS's. But first what is an VPS?
virtual private server (VPS) is a virtual machine sold as a service by an Internet hosting service. " ~Wikipedia.org

Now what did you can do with that VPS? Everything! Its a bit like an Computer but
withput any GUI or something like this you work in an simple Shell from Linux.
You can setup the following things on an Linux VPS: (not all)
-> Ubuntu
-> Debian
-> CentOS
-> etc.

Where i can host an VPS? Here or at an Hosting Company. There you can
use anything you want. But now what did you have to do if you first get your
server?

1. apt -get update
2. apt -get upgrade
3. Setup FTP, Phpmyadmin etc.

These all things are linked here for you:
https://www.youtube.com/watch?v=W2ccsmomCs4
-> English YouTube Tutorial.

Text Tutorial

When you first learn how to set up a VPS, you’ll probably be confused by all the different accounts, passwords and everything.
Put it this way: when you’re setting up a VPS, there are multiple levels. First, there’s the hosting company’s account. Then there’s the WHM (top-level) account. Then there’s the cPanel (second level) accounts.

Getting started
Using the GoDaddy example (since that’s where I’m hosted), the first time you launch your VPS – in other words when you ask them to do the basic setup for you – you’ll be asked for a hostnameusername andpassword.

  • Your hostname can be anything you want, really. For example, this site’s VPS could be called myvps.setupmyvps.com or helpme.setupmyvps.com or chickenlegs.setupmyvps.com – or anything else that takes our fancy. Obviously it’s best to choose something that sounds cool.

  • Your username and password will be used to access the hosting company’s stats and server info. The username isn’t normally used on the server itself but the password is.
Confusing? Yes. Learning how to set up a VPS is very confusing!
Once you’ve chosen a hostname, username and password, your hosting company will do the basics to setup a VPS for you – this usually takes a while (like 12 hours or so), though in slack periods it can be ready a lot quicker. You’ll get email confirmations of everything, usually along with a little user guide.
Your empty VPS is ready
Once your VPS is ready, you’ll need to log in using WHM. To do this, you’ll use the username “root” and the password you defined above. You use “root” as the login because, when you’re setting up a VPS, you need to be logged in at the highest possible system level… and that’s always called “root” (at least on normal servers it is).
Your hosting company will have sent you info on where to find WHM. In most cases, it’s on ports 2086 and 2087. You’ll need the VPS IP address (which will be in your notification email): for example, if your server’s IP address is 188.77.66.55, you’d type this into your browser’s address bar:
http://188.77.66.55:2087
You’ll see a WHM login screen. Enter the username “root” and the password you chose when you set the hostname.
WHM Login
Since this is the first time you’ve logged in, WHM will run a wizard to help you set up. You’ll need to agree to the license agreement (yawn), then choose your contact details. Make sure you enter a reliable email address: this is where any warnings and notifications will go, so you need to make sure you get them!
You’ll also need to enter the Main Shared Virtual Host IP. Although it sounds scary, it’s just the same IP address you entered to get to the WHM login (188.77.66.55 in our example).
The hostname section needs a domain name. You don’t always have to change this (most companies set it to something unique) but, if you want to, set it to a domain you own, e.g. setupmyvps.com
The next bit is nameservers. You need two of these and the standard approach when setting up a VPS is to call them ns1 and ns2 (imaginative, huh?). So in the example, they’d be ns1.setupmyvps.com and ns2.setupmyvps.com. Don’t worry about how you register these so that the Internet knows where to find them – we’ll cover stuff like that in how to set up a VPS with a new domain name.
Next, you just hit “Save”, skip through the quota page (without waiting for it to finish), mark “Enable Nameserver” on the next page (on the right) and keep clicking through until you get to the MySQL root password bit. You’ll need to enter a password there before finishing.
Ready to roll!
And that’s it. Setting up a VPS – at least the basics – is not incredibly difficult as long as you don’t fret too much and use your head a bit. Make sure you write down all the usernames, passwords, server names and stuff for later reference and you’ll be fine. http://www.setupmyvps.com/

If you need any Help or informations about VPSs pm me or write here in the Thread! Smile
Are you sure?
Reply
#2
This isn't what's the first things to do when you got your vps.
First, Update packages.
Second, secure it.
Third, secure it.

Wait, did I already say secure it?
Reply
#3
(09-23-2016, 02:51 AM)Conan Wrote: This isn't what's the first things to do when you got your vps.
First, Update packages.
Second, secure it.
Third, secure it.

Wait, did I already say secure it?

Yes @Conan: and i like to learn about more and more security related tutorials. can you please share with us some basic and then advance security tutorial with us in Tutorial Thread.
Reply
#4
I do recommend configuring the firewall and closing unnecessary ports that you don't need. Another good thing to do is to use a private/public authorization to your vps. Good luck to everyone who's getting started with their free or paid vps. Smile
Reply
#5
I think that changing ssh port, updating virtual private server system and using key authentication is three first things that you must do with your new server. Regards, Alex.
Reply
#6
(10-01-2016, 01:33 PM)mad_alex74 Wrote: I think that changing ssh port, updating virtual private server system and using key authentication is three first things that you must do with your new server. Regards, Alex.

And disable root authorization to use the specific user with su/sudo priveleges instead.
Reply
#7
I believe that changing ssh port, upgrading virtual private server framework and utilizing key confirmation is three first things that you should do with your new server
Reply
#8
hey guy's can you explain how to change the port of the new vps and upgrade the framework and utilizing key....
Reply
#9
1. Change the parameter PORT in /etc/ssh/sshd_config from standard 22 to any (upper). Then "service ssh restart". Note, in different systems it could have slightly different names/path: "/etc/openssh/sshd_config" and "service sshd restart" for example.
2. Keys: just generate with command "ssh-keygen". It's an interactive command. The pub string have to be copied to the file /home/<username>/.ssh/authorized_keys , the secret key have to be moved and kept on the local PC and used with Putty or any other ssh client.
Reply
#10
Now this is something worth a read.
Will definitely stick it up and check once I gain my points to unleash mine! Smile
~Do not hesitate to ask for Graphics Designing or Web Designing services!
Reply


Forum Jump:


Users browsing this thread:
1 Guest(s)