To change the port for the SSH server, follow these steps:
Log in to the server as root using SSH.
Open the /etc/ssh/sshd_config file in your preferred text editor (nano, vi, etc.).
Locate the following line:
Remember that for security reasons, A2 Hosting uses port 7822 for SSH connections instead of the default port 22.
Change 7822 to the new port number that you want to use.
Save the changes to the /etc/ssh/sshd_config file, and then exit the text editor.
Restart the SSH service using the appropriate command for your Linux distribution:
For CentOS and Fedora, type:
service sshd restart
For Debian and Ubuntu, type:
service ssh restart
While still logged in as root, in a new terminal window try to log in using the new SSH port number. If the login fails, check your settings. Do not exit your open root session until you are able to log in using the new configuration.
1. Login to WHM with your login details.
2. Go to restart servicees.
3. Restart SSH server. Once service get restart you will get below information –
Waiting for “sshd” to restart ………waiting for “sshd” to initialize ………finished.
sshd (/usr/sbin/sshd) running as root with PID 904715 (process table check method)
Starting sshd: [ OK ]
Apr 6 05:48:40 server sshd: Server listening on :: port 8872.
Apr 6 05:48:40 server sshd: Server listening on 0.0.0.0 port 8872.
Apr 6 05:48:39 server sshd: Received signal 15; terminating.
sshd restarted successfully.
In the above output, you can see 8872 is the SSH port.
In this article, we are going to see how we can migrate SSL certificates from one server to another. Before we transfer, you should be aware of the components involved with SSL certificates and how it is stored. Let’s have a detailed look on it.
There will be a certificate file. It will have the extension (.crt). Also, there will be a key and it will have the extension (.key). There will also be a CA bundle. We need to copy the files to new server in order to migrate the SSL certificate.
Steps to transfer SSL certificate
1) Login to your WHM.
You could access the WHM with https://server.hostname.tld:2087. This will lead you to the home page of WHM interface.
Now locate the ‘SSL/TLS’ section in WHM and go to ‘SSL Storage Manager’ as shown in the figure.
You will be lead to the next page. There you could find the certificates and keys with the username. Please locate the certificate you wish to transfer.
2) Copy the key
Please refer to the attached screen shot for any clarification.
Now you need to copy the key and paste it on a text file. To view the full content, please click on the lens icon near the key. The key will be starting with —–BEGIN RSA PRIVATE KEY—– and will end up with —–END RSA PRIVATE KEY—–.
3) Copy the Certificate
Now you need to copy the certificate. This also can be done from the previous window. Please click on the lens icon next to the certificate so that you would be able to view and copy the certificate.
Please copy and paste the certificate on a text file. The certificate will be starting with —–BEGIN CERTIFICATE—– and ending with —–END CERTIFICATE—–.
Now you need to install the certificate on the new server. You could install it from the WHM interface and the cPanel interface.
4) Install the certificate on new server
To install the certificate from the WHM, please locate “Install an SSL Certificate on a Domain” under the “SSL/TLS”. Please refer to the screenshot below in case of any doubts.
You need to use the certificate and key copied and saved on the text files earlier. You also could install it from the cPanel interface. To see how to install SSL certificate from the cPanel interface, please follow the guide in the link below.
The Let’s Encrypt allows you to install AutoSSL for the hostname. In this tutorial, I will show you how to install Let’s Encrypt SSL to the hostname. Here are the steps to install the same on hostname.
Install Let’s Encrypt Auto SSL Provider.
Run the following command to install Let’s Encrypt provider.
Once you have installed Let’s Encrypt provider, change auto SSL provider to Let’s Encrypt from Comodo.
Login to WHM >> Manage AutoSSL.
Install Self-Signed Certificate to Hostname.
1) Login to WHM as a root user.
2) Go to “Service Configuration”.
3) Then select the following services and click on “Browse Certificate”.
Calendar, cPanel, WebDisk, Webmail, and WHM Services
Dovecot Mail Server
Exim (SMTP) Server
4) Select hostname and click on “Use Certificates”.
5) Then click on “Install”.
Replace Self Signed Certificates with Valid Let’s Encrypt Certificates.
Once you have installed the self-signed certificate, run the following command to check SSL certificates
The Self signed SSL certificates will be replaced with a valid Let’s Encrypt certificate while running above command.
Once it is completed, you can access WHM with the hostname https://hostname:2087
After you upgrade MySQL, there is no supported way to downgrade to the previous version. There will be downtime of the MySQL service during the upgrade process. You should take a backup of the existing database system before you proceed.
In order to upgrade MySQL version from WHM panel, you have to login as root in your WHM and type in the search bar: MySQL.
You will see MySQL Upgrade in the Software section.
After you click on this tab you will be able to review the current version of the MySQL and select the next version, which is available to upgrade. In the screenshot below for example, you can see that the current database version – 5.5 – can be upgraded to 5.6. The screen lists all the important features in the latest version giving you an overview that should help you decide if upgrading the database is worthwhile or not. You should click “Next”
At the next screen the system warns you that you should take a backup of the existing database system. Second, it instructs you that there is no way to downgrade a MySQL database framework from a higher version two a lower one. If this is acceptable for you, you have to tick off two checkboxes indicating that you fully understand the risks of upgrading your database and click continue as shown below:
The next step is information about the upgrade of apache and PHP. Not all MySQL upgrades require them to be rebuilt. In this test example, the system recommends a partial upgrade without an Apache/PHP rebuild – If you upgrade from MySQL 5.5 or 5.6, you do not need to rebuild Apache because the client libraries are compatible.
Once you have choose the proper option for you, you should click on continue and the process will begin. This can take quite a while. All the while, you can check the output in the box below to see the progress.
When the upgrade is done you will see a screen like the image below: