There are many reasons to have Secure Socket Layer (SSL) certificates configured for your domains.  An SSL certificate will help safe guard login credentials for sites that require users to login by encrypting the information as it is transmitted. Aside from authentication, SSL certificates are essential for any site where private information is being submitted (financial, medical, etc). Failure to use an SSL certificate will result in all traffic to and from a given site being transmitted across the Internet in plain text which can possibly be intercepted without knowledge by third parties.

There are three steps to issue and install a certificate:

1. Generate a Certificate Signing Request (CSR) from WHM
2. Provide the CSR to your SSL provider and retrieve the certificate they create from it
3. Access the Web Host Manager and install your new certificate

If you already have a certificate issued from an SSL provider you can skip to the third step. If you are just getting started with the process of configuring an SSL certificate for a domain you will need to use the Generate an SSL certificate tool first with the steps below.

Generate a Certificate Signing Request

To begin you will visit your IP address followed by /whm which should redirect you to your IP address on port 2087.

Example WHM URL: https://123.123.123.123:2087/ Replace the 123.123.123.123 IP with the IP from your welcome email for your server. You will need to login as the root user to access WHM. The login password for the root user will also be found in your welcome email unless it has been changed.

After logging in you will see a menu on the left with a SSL/TLS section. Beneath that section you will see Generate an SSL certificate and Signing Request and Install an SSL Certificate on a Domain.

Complete the form to generate a certificate signing request (CSR). This CSR is what you will provide to the SSL provider and they will use it to issue a certificate for your server / domain configuration.

CSR Form Items:

When complete, email me the certificate, key, and CSR. Check if you want a copy via email
Email Address: If the box above is checked a valid email will be needed for delivery
Key Size: Default of 2048 is sufficient unless the SSL provider requires 4096
Domains: Provide the domains to be covered. This will typically be the domain and the domain with a www. prefix.
City: Enter your city
State: Enter your state but do not abbreviate as it can cause errors
Country: Select from the drop down list
Company Name: Your Company Name, Domain name if not a company
Company Division: Optional, often set to the same as the Company Name
Email: Needs to be valid although use is contingent upon SSL provider
Passphrase:  Blank unless specifically directed to use by SSL provider

Provide the CSR to your SSL provider and retrieve the certificate they create from it.

After completing the form hit Create. The next page will display the CSR, Certificate, and a Key.

“The system has successfully generated the CSR and private key for “yourssldomain.com www.yourssldomain.com”. The system also generated a self-signed certificate that you can temporarily use until you receive a signed certificate from your SSL certificate vendor.”

Do not disclose the key to anyone as it will compromise the security of the certificate. You will want to copy the entire block of text in the Signing Request box and provide this to your SSL provider. They will use the CSR to issue your certificate. You must provide the entire CSR which includes everything between and including the following lines:

-----BEGIN CERTIFICATE REQUEST-----

-----END CERTIFICATE REQUEST-----

After submitting your CSR you should receive the official certificate in the form of an email or as a downloaded zip file. If the contents are compressed you will need to extract them to your desktop or another working area so the certificate can be installed.

Access the Web Host Manager and install your new certificate.

When you have your certificate you will need to return back to the Web Host Manager. Instead of using the Generate an SSL Certificate and Signing Request you will use the Install an SSL Certificate on a Domain link.

You will want to copy the certificate from your provider with everything including the BEGIN and END CERTIFICATE lines:

-----BEGIN CERTIFICATE-----

-----END CERTIFICATE-----

Paste this certificate in the Certificate box and hit “Autofill by certificate”. This should populate the domain name, IP address, and the private key. If your certificate provider included a Certificate Authority (CA) Bundle you can copy that in the third field. If they did not provide this do not worry as the server will attempt to populate it automatically.

When the Domain, IP Address, Certificate, Private Key, and CA Bundle (if applicable) are filled in you can use the Install button at the bottom of the page. If the certificate and other values are valid you should see a success message:


 

When the success message is shown you should be able to then visit your site that the certificate is valid for using https:// and the browser will then encrypt and validate the domain with the new certificate to securely transmit data.

Overview

This guide will show you how to change the default page that Plesk uses for any new sites that have created accounts on the server before content is placed in the website folders as well as the default page used for any sites that are pointed to your server that do not have an account created in Plesk.

This is what the Plesk default page typically looks like. This page is displayed when you navigate to a domain that is pointed to your server's IP address and created on the Plesk server without placing any web content and also when navigating to the IP address of the sever when no domain is set as the default domain on that IP address.

Resolution

To change this page to your own page, you need to navigate on the server with SSH or SFTP to the following directories.

Location of default page for sites that are pointed to your server that do not have an account created in Plesk. You can also view this page by navigating to the IP address of your server in your web browser so long as there's not a default domain set to the IP address under Tools and Settings -> IP Addresses.

• /var/www/vhosts/default/htdocs (non-SSL)
• /var/www/vhosts/default/httpsdocs (SSL)

Location of default page that Plesk serves before any files are copied to a newly added domain's folders.

• /var/www/vhosts/.skel/0/httpdocs/.
• /var/www/vhosts/.skel/0/httpsdocs/.

In this example I replaced the index.html file with my own file named the same thing in the /var/www/vhosts/default/htdocs directory. You can simply edit the index.html file or replace it with the site files of your choosing. 

                This is in reference to 2008 server edition not being able to process its updates, and is not progressing through the checking updates phase of the windows updates.

1. Connect to the server using RDP.
2. Open up the command prompt you can do this by using programs.
3. Launch the command prompt as administrator. (this is required to provide sufficient access needed to stop the windows processes)
4. Run the following command in Command Prompt net stop wuauserv and wait for it to completely stop.
5. Open up the C drive.
6.  Go to the windows folder.
7. Rename the software distribution folder to softwaredistrubition_test.
8. Return to the command prompt and run net start wuauserv
9. Then reboot the computer.
10. When the computer reboots you can run and update the security updates.

Microsoft released a security pack that fixed this on 2008, ensuring that you have this update once the updates are completed, will prevent the error from happening in the future. This security update is called  947821. 

  In this article, we will walk through how to log into your linux server over ssh as the root user from your Windows PC or Mac Computer. Accessing the server with the "root" account will allow you the most freedom to modify the server. However, this can be dangerous as the "root" account is the most powerful account on the server. ( Always make a backup of any files you plan to change before changing them. This way you can always go back to a working configuration if the change doesn't go according to plan. )

1.) The first thing you will want to do is download the PuTTY client for Windows from their site.

 http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

 2.) Once you've downloaded and installed PuTTY, you will want to click on the PuTTY executable to open the application.

 3.) In the "Host Name (or IP address)" field, put the IP address that has been provided with your server and click "Open".

4.) You will be prompted to generate a key upon your first login attempt. Click "Yes".

5.) Type "root" as the user and press "enter", Then type in the password provided with your server and press "enter"(when typing in the password, no text will be displayed).

You are now logged in under the root account and ready to begin setting up your server.

If you are using a Mac, you can simply open the Mac Terminal and connect to SSH from here.

 1.) Select "Search" in the upper right hand corner of the desktop.

2.) Type in the Search box "Terminal" and click on the top result.

 


3). Once you've opened your Terminal Window, just type the following:

ssh root@IP.add.re.ss

**replace "IP.add.re.ss" with the IP address you have been provided with your server.

4.) You will be prompted to create a key upon your first login attempt to the server. Type "yes".

5.) Type the password provided with your server and you are now logged in as "root"! (when typing in the password, no text will be displayed)

 This article has been provided by Codero Hosting, the leading provider of reliable dedicated, managed and cloud hosting services. Need more information on this topic or to learn more about Codero’s hosting services please visit www.codero.com, chat with us online or give us a call at 866-2-CODERO.

In order to create a new instance, you must log into your control panel at serverportal.com, and click on the “cloud” option under the services. If you have not done so, please make sure to agree to the Cloud TOS before proceeding.

1.  Log into your Cloud Portal.  https://portal.codero.com/
2. Click on Create Cloud Server
   
   
    
3. Create Cloud Server Hostname
   
4. Choose Region – Phoenix (West) or Dallas (Central)
   
   
   
   
5. Operating System – CentOS, Fedora, Ubuntu, Debian, Docker, Oracle or Windows
6. Mixin – **This is optional** Currently for Mixin's we offer the Plesk Web Admin control panel.
   
   
   
   
7. Server size – Choose Ram, CPU and HD sizes
   
   
   
   
8. Next to the size it will show the bandwidth included with that size and below the sizes offered it will show what bandwidth is included for free (Public Incoming and Private Outgoing/Incoming) along with the cost if you go over the included amount that comes with the size chosen.
9. Summary -  Choose Hourly or Monthly Billing **This cannot be changed after the instance is spun up**
   
   
   
   
10. Click Create Server
11. Your Server will then begin to be configured according to your specs.  Below are the three stages of the Deployment.

Creating
 

Online



Assigning IP 

• 12. Here you have for Cloud Server when it is finished.

Your new instance will now be created and you will see a pop-up at the top of the page with you new root (or Administrator if its a Windows server) password.

IMPORTANT: Please be sure to record your root password and change it as soon as you first log into your instance. You can only view the temporary password once.

Your new cloud is ready!

This article has been provided by Codero Hosting, the leading provider of reliable dedicated, managed and cloud hosting services. Need more information on this topic or to learn more about Codero’s hosting services please visit www.codero.com, chat with us online or give us a call at 866-2-CODERO.

All new customers to Codero will be charged $1 to the credit card or ACH payment method prior to allowing a VM to be created.  Upon successful charge, a $1 account credit will be placed on the account.

The $1 is a validation of the credit card or ACH, and cannot be refunded but will be applied as an account credit.

This article has been provided by Codero Hosting, the leading provider of reliable dedicated, managed and cloud hosting services. Need more information on this topic or to learn more about Codero’s hosting services please visit www.codero.com, chat with us online or give us a call at 866-2-CODERO. 

Codero only accepts payments via credit card (Visa, Mastercard, Discover and American Express) Codero Cloud.  We do not accept Paypal, wire transfers, ACH or checks for Codero Cloud payments.


This article has been provided by Codero Hosting, the leading provider of reliable dedicated, managed and cloud hosting services. Need more information on this topic or to learn more about Codero’s hosting services please visit www.codero.com, chat with us online or give us a call at 866-2-CODERO. 

No, when you create a VM on the Codero Cloud, you choose either monthly or hourly billing.  You can not switch that VM from one payment type to another.

If you wish to change the payment from hourly to monthly or monthly to hourly, you will need to destroy the VM and create a new one.  Before doing such, please make sure you create a snapshot of the VM you are destroying, and then you can load that snapshot into your new VM you create on the other billing method.

This article has been provided by Codero Hosting, the leading provider of reliable dedicated, managed and cloud hosting services. Need more information on this topic or to learn more about Codero’s hosting services please visit www.codero.com, chat with us online or give us a call at 866-2-CODERO. 

We have attempted to make this as easy as possible being able to manage not only your cloud server but also your billing and payment methods from within the same control panel. Once you log in to your Portal.Codero.Com you will need to add a payment method to be able to create a cloud server. 

            This is done by clicking the “Payment Methods” options on the left side menu. From this menu you will need to setup a credit card for automatic payments under the option “Add Credit Card”section on the right hand side of the page. For this simply fill out all of the card details and then click  “Add Credit Card” at the bottom of the page. Once the card is added you are now free to create a cloud server. If this is your first time creating a cloud server then you may need to have your account verified. For this, be on the lookout for an email from Codero to verify your account. After it has been verified you should be able to spin up cloud servers. If you have any issues or questions please use the “Support” section for assistance at the bottom of the left hand menu.

This article has been provided by Codero Hosting, the leading provider of reliable dedicated, managed and cloud hosting services. Need more information on this topic or to learn more about Codero’s hosting services please visit www.codero.com, chat with us online or give us a call at 866-2-CODERO. 

In the article below you will be creating a user and giving them full permissions to a specific database. This should only be done for users that you trust as they would have full access to the content of that database. Typically the ability of creating users and granting privileges can only be done by the root/admin user and is done via SSH or Remote Desktop. 

Keep in mind any underlined words may need to be changed to match your specific requirements as shown below in the full example. All other items are necessary.

CREATE USER 'user'@'localhost' IDENTIFIED BY 'password';

GRANT ALL PRIVILEGES ON database.table TO 'user'@'localhost';

Now with a full example below.

In this example my user is george and my password is abcd1234

Georges public IP that he connects from is 192.168.100.15

I’m granting him access to the jungle database and all it's tables.

CREATE USER 'george'@'192.168.100.15' IDENTIFIED BY 'abcd1234';

GRANT ALL PRIVILEGES ON jungle.* TO 'george'@'192.168.100.15';

You can also grant a user permissions to all databases by putting a *.* where "jungle.*" would be, or give them access to a specific table within a database by specifying it like so: jungle.specificDB

If you wish for him to only connect to this from within you may put this instead:

GRANT ALL PRIVILEGES ON jungle.* TO 'george'@'localhost';

If you wanted to only give the george user read only access to all of the tables within the jungle database, this would be done as shown below:

GRANT SELECT ON jungle.* TO 'george'@'192.168.100.15' IDENTIFIED BY 'abcd1234';

Further information on granting privileges and what certain privileges can do can be found at MySQL's Documentation page.

.htaccess redirects can be done via several different methods, which all essentially work the same way. In this article we will cover a few different basic methods of .htaccess redirects, explaining what they do, how they work, and when you would want to use one over another.

There are two forms of redirects which are called 301 and 302 redirects. 301 Redirects are permanent redirects, which essentially tell Bots and Spiders (such as Google's Website Indexing Bot) that the redirect is a permanent displacement of the Website or Webpage, so that Google can index the new page or website accordingly. The 302 redirect is a Temporary Redirection, meaning that the redirect should be removed sometime in the future and that the normal website content should return and would be used when you do not want Google to update their indexing for your website.

With that bit out of the way, let's get to the actual redirect coding! 


The easiest redirect is simply redirecting one domain or webpage to another domain or webpage. This can be done by adding a single line of coding to your .htaccess file;

Redirect 301 / http://NewDomain.com/

Now let's break this down a bit!
The Redirect at the beginning tells Apache that you're going to be doing a redirect if the URL matches the clause.
The 301 (as we covered earlier) means that this redirect is going to be a permanent relocation.
The first / means that the redirect for "http://YourDomain.com/".
The last bit, http://NewDomain.com/, tells Apache to redirect requests to http://NewDomain.com/
All in all, this redirect would redirect any hits to "http://YourDomain.com/" to " http://NewDomain.com/"

We can make this redirect work only for certain URLs by appending the URL after the first /, as so;
Redirect 301 /RedirectMe http://NewDomain.com/Redirected
This redirect would redirect any hits to "http://YourDomain.com/RedirectMe" to " http://NewDomain.com/Redirected"

You would only want to use these types of redirect when redirecting an entire Domain or a specific Web Page or URL to another location (For Example "http://Domain.com/" to "http://NewDomain.com/" or "http://Domain.com/Page1" to "http://Domain.com/Page2").

You would not want to use this redirect to redirect a Domain to a Sub Folder of the same domain, as it will cause a redirect loop (For Example "http://Domain.com/" to "http://Domain.com/Sub-Folder/").
The next type of redirect is a bit more complicated, but is a much more powerful tool due to how heavily it can be customized.  These types of redirects are most commonly used when redirecting "Domain.com" to "www.Domain.com" or "http://Domain.com/" to "https://Domain.com/" for use with SSLs.


To redirect a domain to use the www. subdomain, you would want to use the following bit of coding in your .htaccess file;

RewriteEngine On

RewriteBase /

RewriteCond %{HTTP_HOST} ^domain.com$

RewriteRule ^(.*)$ http://www.domain.com/$1 [R=301,L]

- The first line of coding turns the RewriteEngine used by Apache on. This should be on by default and should not be needed in most circumstances.
- The second line of coding is a little complicated. It essentially tells the Rewrite Rule what directory you're working from, as the rewrite rule is relative to the RewriteBase. In this case, and in most cases, the RewriteBase is the document root.
- The third line of coding is where the redirect really begins to take place. This line states the Rewrite Condition, which is essentially that the HTTP Host sent by the headers matches "domain.com". The $ at the end is a capture, taking anything after the / and storing it until the RewriteRule is executed.
- The final line of coding is a bit more complicated. This bit of coding essentially states that, when the Rewrite Conditions are met, that the page redirects to "http://www.domain.com/". The $1 at the very end is the capture from the RewriteCond and would automatically put in the URI from the initial URL onto the end of the new URL with the www sub-domain.

In practice this bit of coding would redirect the following;
http://domain.com to http://www.domain.com/

http://domain.com/ to http://www.domain.com/

http://domain.com/Redirected/ to http://www.domain.com/Redirected/

To do the opposite and redirect http://www.domain.com/ to http://domain.com/ you would want to use the following bit code;

RewriteEngine On

RewriteBase /

RewriteCond %{HTTP_HOST} ^www.domain.com$

RewriteRule ^(.*)$ http://domain.com/$1 [R=301,L]

This coding is almost identical to the coding above, however we placed the 'www' sub-domain prefix on the RewriteCond line and removed it from the RewriteRule line, telling Apache to redirect http://www.domain.com/ to http://domain.com/.


Another very sought after redirect is an HTTPS redirect. This redirect is used when forcing HTTPS (SSL) on a Domain or Webpage. The code to do so would be the following;

RewriteEngine On

RewriteCond %{HTTPS} off

RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

- The first line of coding turns the RewriteEngine used by Apache on. This should be on by default and should not be needed in most circumstances.
- The second line of coding is the Rewrite Condition, checking to make sure that 'HTTPS' is set to 'off' in the request headers. This is needed so that we do not redirect HTTPS URLs back to HTTPs again, creating a Redirect Loop.
- The third line of coding is again the effect of the redirect. If the RewriteCond was true (that HTTPS was off), then it rewrites the URL to "https://Domain.com/$URI"

In practice this bit of coding would redirect the following;
http://domain.com/ to https://domain.com/
http://domain.com/login/ to https://domain.com/login/
http://www.domain.com/ to https://domain.com/
http://www.domain.com/sub-folder/ to https://domain.com/sub-folder/



The final commonly used redirect is used to redirect your Domain to a Sub Folder under the Domain. This is typically done when people want their landing page to be a Sub Folder, such as "http://domain.com/store". The bit of coding would be;

RewriteEngine On
RewriteCond %{HTTP_HOST} ^(www.)?Domain.com$
RewriteRule ^(/)?$ subfolder [L]

- The first line of coding turns on the Rewrite Engine for Apache.

- The second line of coding matches the HTTP Host sent in the headers to "Domain.com" or "www.Domain.com".
- The third line of coding is the sub folder that you'd like to redirect to. In this case it would redirect to /subfolder.

In practice this bit of coding would redirect the following;
http://domain.com/ to http://domain.com/subfolder/
http://www.domain.com/ to http://www.domain.com/subfolder/



Easy apache is a stream lined method of installing modules for all users of the WHM.  This is useful if you do not want to set up individual php.inis.

To Enable Apache or PHP Modules Using EasyApache

1. Log in to WHM as the 'root' user.
2. In the Find box type easy.
3. Click EasyApache (Apache Update).
4. Leave default, and then click the gear icon (Customize Profile).
5. Leave default, and then click Next Step.
6. Click Exhaustive Options List.
7. Click the name of the Apache or PHP module, and then click Save and build.

Once you hit save and build, it can take some time, let the update run, and once completed all cpanels on the WHM account will be updated.

By following this guide you will be able to set a PTR record for any Cloud server you have with Codero.

            1. Log into your portal.codero.com account.

            2. Locate the Cloud server from the list in which you plan on adding the PTR record.

            3. Click on the Reverse DNS button which will open up a pop-up screen to add the record.

            4. Once the record is added click Update to finish.

            5. Please allow 12-24 hours for the record to propagate worldwide.

*If you do not see the Reverse DNS button please make sure the server is in the “Running” state.

*Please note you do not need to stop or reboot the server once the record has been added.

This article has been provided by Codero Hosting, the leading provider of reliable dedicated, managed and cloud hosting services. Need more information on this topic or to learn more about Codero’s hosting services please visit www.codero.com, chat with us online or give us a call at 866-2-CODERO. 

1. Log in to Remote Desktop as the Administrator user and then open the start menu.
2. From the start menu simply type “Control Panel” and the control panel option should be quickly indexed, click on it.
3. In Control Panel, click Network and Internet then click on the Network and Sharing Center. 
4. You would then select Change Adapter Settings, right-click the network adapter that connects to the public network or internet, and then click Properties.                                      
5. On the Networking tab, click Internet Protocol (TCP/IPv4), and then click Properties.
6. On the General tab, click Advanced.
   
7. On the Advanced TCP/IP Settings dialog box, click Add under the "IP Addresses" section on the "IP Settings" tab.
8. On the TCP/IP Address dialog box, enter the IP address and the Subnet mask, and then click Add.
9. Click OK twice, and then click Close.

Wordpress is php based, and due to this there is times where the php index page cannot load after an upgrade due to incompatible plugins. You can disable this without logging into the site in case the wp-admin page is unavailable.

1. Log into phpmyadmin
2. In the list of databases find the database contained in the wp-configuration file under database_name
3. Go to wp-options table
4. Find Active plugins table
5. The table will hold a line of code that looks like this A : 1 : {#} change this value to A : 0 : {}
6. Then save this will disable them without logging in.

Copy the previous code back into the cell to reactivate them at once. 

You are able to receive discounts if you choose to renew on a semi annual or annual term.

Semi annual renewals receive a 5% discount and Annual renewals receive 10%.

These discounts are valid for the life of the server, as long as the billing term remains the same.

If you wish to change your billing to one of these terms, please submit a ticket to the Billing Department, via www.serverportal.com , with the request.

This guide will help you get phpMyAdmin installed on a Debain 8. 

Before we begin, please make sure everything is fully up to date by running these commands.

                apt-get update && apt-get upgrade -y

Next make sure you have the PHP module mcrypt installed.

                apt-get install mcrypt

Restart apache

                /etc/init.d/apache2 restart


 

Next install phpMyAdmin

                apt-get install phpmyadmin

Select apache2 on the next screen by pressing spacebar.

Select yes on the next screen.

Next cd into your website directory and create a symbolic link.

                cd /var/www/html/

                ln -s /usr/share/phpmyadmin


 

You may want to secure phpMyAdmin now by creating an .htaccess file.

                cd /var/www/html/phpmyadmin

                nano .htaccess

Add these lines and replace the IP with your own IP.

                order allow,deny

                allow from 12.34.56.78

You may now access phpMyAdmin by going to ‘yourdomain.com/phpmyadmin’.

Overview

This guide will show you how to change the default page that Plesk uses for any new sites that have created accounts on the server before content is placed in the website folders as well as the default page used for any sites that are pointed to your server that do not have an account created in Plesk.

This is what the Plesk default page typically looks like. This page is displayed when you navigate to a domain that is pointed to your server's IP address and created on the Plesk server without placing any web content and also when navigating to the IP address of the sever when no domain is set as the default domain on that IP address.

Resolution

To change this page to your own page, you need to navigate on the server with SSH or SFTP to the following directories.

Location of default page for sites that are pointed to your server that do not have an account created in Plesk. You can also view this page by navigating to the IP address of your server in your web browser so long as there's not a default domain set to the IP address under Tools and Settings -> IP Addresses.

• /var/www/vhosts/default/htdocs (non-SSL)
• /var/www/vhosts/default/httpsdocs (SSL)

Location of default page that Plesk serves before any files are copied to a newly added domain's folders.

• /var/www/vhosts/.skel/0/httpdocs/.
• /var/www/vhosts/.skel/0/httpsdocs/.

In this example I replaced the index.html file with my own file named the same thing in the /var/www/vhosts/default/htdocs directory. You can simply edit the index.html file or replace it with the site files of your choosing.

1. Log in to Remote Desktop as the Administrator user and then open the start menu.
2. From the start menu simply type “Control Panel” and the control panel option should be quickly indexed, click on it.
   
   
   
   
3. In Control Panel, click Network and Internet then click on the Network and Sharing Center. 
   
   
   
   
   
4. You would then select Change Adapter Settings, right-click the network adapter that connects to the public network or internet, and then click Properties.
   
   
   
   
   
   
5. On the Networking tab, click Internet Protocol (TCP/IPv4), and then click Properties.
   
   
   
   
6. On the General tab, click Advanced.
   
   
   
   
7. On the Advanced TCP/IP Settings dialog box, click Add under the "IP Addresses" section on the "IP Settings" tab.
   
   
   
   
8. On the TCP/IP Address dialog box, enter the IP address and the Subnet mask, and then click Add.
9. Click OK twice, and then click Close.

MySQL organizes information into databases; each table holds specific data. Below we will explain how to list, create and delete databases in MySQL. To do this you will need access to run mysql queries either via SSH, or through phpMyAdmin.

You can easily view available databases by typing the command:

 SHOW DATABASES;

 When running the command make sure you remember to put the ; (semicolon) character at the end of it. When running the command it should like the following:

 mysql> SHOW DATABASES;

+--------------------+

| Database |

+--------------------+

| information_schema |

| mysql |

| performance_schema |

| test |

+--------------------+

4 rows in set (0.01 sec)

Creating a database:

 CREATE DATABASE databasename;

 For the sake of this guide, the data based will be called "testone". 

 mysql> CREATE DATABASE testone;

 mysql> SHOW DATABASES;

+--------------------+

| Database |

+--------------------+

| information_schema |

| testone |

| mysql |

| performance_schema |

| test |

+--------------------+

5 rows in set (0.00 sec)

You would delete a MySQL database with this command:

Be very careful when you DROP A DATABASE IT IS GONE FOR GOOD! The best route would be to backup the database first using mysqldump command explained here and then use the DROP command below. This way you have a backup to restore should you need it.

 DROP DATABASE databasename;