αž€αžΆαžšαžŠαŸ†αž‘αžΎαž„αžœαž·αž‰αŸ’αž‰αžΆαž”αž“αž”αžαŸ’αžš SSL αžŠαŸ„αž™αž”αŸ’αžšαžΎ DirectAdmin

αž€αžΆαžšαžŠαŸ†αž‘αžΎαž„αžœαž·αž‰αŸ’αž‰αžΆαž”αž“αž”αžαŸ’αžš SSL αžŠαŸ„αž™αž”αŸ’αžšαžΎ DirectAdmin

After the Certificate Authority issues your SSL certificate, you must install it on your website’s hosting server. Here’s how to install the certificate in DirectAdmin:

SSL installation on DirectAdmin

1) Navigate to your server’s main menu by clicking the button at the top-left corner of the screen, as shown in the screenshot below. Choose αž€αžΆαžšαž–αž·αž—αžΆαž€αŸ’αžŸαžΆβ€‹αžšαž”αžŸαŸ‹β€‹αž’αŸ’αž“αž€αž”αŸ’αžšαžΎαž”αŸ’αžšαžΆαžŸαŸ‹:

2) αž“αŸ…αž€αŸ’αž“αž»αž„ αž’αŸ’αž“αž€αž‚αŸ’αžšαž”αŸ‹αž‚αŸ’αžšαž„β€‹αž‚αžŽαž“αžΈ αž•αŸ’αž“αŸ‚αž€, αž…αž»αž… αžœαž·αž‰αŸ’αž‰αžΆαž”αž“αž”αžαŸ’αžš SSL:

3) αž‡αŸ’αžšαžΎαžŸαžšαžΎαžŸ αž”αž·αž‘αž—αŸ’αž‡αžΆαž”αŸ‹αžœαž·αž‰αŸ’αž‰αžΆαž”αž“αž”αžαŸ’αžš αž“αž·αž„αžŸαŸ„αžŠαŸ‚αž›αž”αžΆαž“αž”αž„αŸ’αž€αžΎαžαž‡αžΆαž˜αž»αž“ αž‡αž˜αŸ’αžšαžΎαžŸ:

4) Then, paste the Private key for your SSL into the αž‚αž“αŸ’αž›αžΉαŸ‡ αžœαžΆαž›αŸ”

αž…αŸ†αžŽαžΆαŸ† (Note): The Private key is generated at the same time as the CSR code. The Private key is enclosed with the following header and footer: —–BEGIN PRIVATE KEY—– and —–END PRIVATE KEY—–. If you generate the CSR code in DirectAdmin, you need to save the Private key manually as DirectAdmin does not save it automatically.

Paste the certificate code that you received from the Certificate Authority, including —–BEGIN CERTIFICATE—– and —–END CERTIFICATE—– to the αžœαž·β€‹αž‰αŸ’αž‰αžΆβ€‹αž”αž“β€‹αž”αŸαžαŸ’αžš field. The same code is also contained in the yourdomain.crt file located in your 1Byte account. You can open this file with a plain text editor like Notepad (for Windows) or TextEdit (for macOS).

Once you’ve pasted the key, tick the option Force SSL with https redirect. This enables HTTPS redirect for your website so that your visitors are automatically redirected to the secure version of the website. Then, click αžšαž€αŸ’αžŸαžΆαž‘αž»αž€β€‹ (Save).

To complete the installation, upload the CA Bundle file (.ca-bundle) to DirectAdmin.
This file is in the certificate ZIP archive you received from the Certificate Authority via email. You can also download all SSL files from your 1Byte account. The CA Bundle file should have the name: yourdomain.ca-bundle.
You can open it via Notepad (Windows) or TextEdit (mac OS) to copy its content in the TXT format required for the DirectAdmin panel.

αž‡αŸ’αžšαžΎαžŸαžšαžΎαžŸβ€œαž”αž·αž‘αž—αŸ’αž‡αžΆαž”αŸ‹αžœαž·αž‰αŸ’αž‰αžΆαž”αž“αž”αžαŸ’αžš αž“αž·αž„αžŸαŸ„αžŠαŸ‚αž›αž”αžΆαž“αž”αž„αŸ’αž€αžΎαžαž‡αžΆαž˜αž»αž“"αž‡αž˜αŸ’αžšαžΎαžŸαž αžΎαž™αž…αž»αž…αž›αžΎ SSL CA Certificate.

Next, copy and paste the entire content of the .ca-bundle file to the box and tick Use a CA cert αž‡αž˜αŸ’αžšαžΎαžŸαŸ” αž”αž“αŸ’αž‘αžΆαž”αŸ‹αž–αžΈαž“αŸ„αŸ‡αž…αž»αž… αžšαž€αŸ’αžŸαžΆαž‘αž»αž€β€‹ (Save).

You will see the notification β€œSuccess CA certificate is ok. Your site should be secure within a few minutesβ€œ. This means that the SSL was installed successfully. To check the certificate installation, you can use this online tool: https://decoder.link

Troubleshooting the β€œCould not Execute your request” error

From time to time, you may encounter the following error message when opening the αžœαž·αž‰αŸ’αž‰αžΆαž”αž“αž”αžαŸ’αžš SSL section in your Account Manager: β€œCould not Execute your request. SSL is not enabled for this αžˆαŸ’αž˜αŸ„αŸ‡αžŠαŸ‚αž“αŸ” αž“αŸαŸ‡αž˜αžΆαž“αž“αŸαž™αžαžΆ αž”αž·αž‘ SSL option was turned on in the αžœαž·αž‰αŸ’αž‰αžΆαž”αž“αž”αžαŸ’αžš SSL section of your DirectAdmin. This option doesn’t allow SSL installation. It also prevents the user from opening the αžœαž·αž‰αŸ’αž‰αžΆαž”αž“αž”αžαŸ’αžš SSL section. As a result, when that option is enabled, you won’t be able to install your certificate or turn the option off via the user management area.

It is only possible to disable that option via SSH. For this, you’ll need to have root access via SSH to the server where your DirectAdmin is installed. Once logged in as a root user, run this command to open the configuration file for the domain:

sudo nano /usr/local/directadmin/data/users/αž’αŸ’αž“αž€β€‹αž”αŸ’αžšαžΎ/domains/DOMAIN.TLD.conf

  • nano is the command to open the .txt file.
  • αž€αžΆαžšαž–αž·αž—αžΆαž€αŸ’αžŸαžΆβ€‹αžšαž”αžŸαŸ‹β€‹αž’αŸ’αž“αž€αž”αŸ’αžšαžΎαž”αŸ’αžšαžΆαžŸαŸ‹ is the name of the account where you will apply the changes.
  • DOMAIN.TLD is your domain name.

In the configuration file, locate the field ssl=OFF αž αžΎαž™αž•αŸ’αž›αžΆαžŸαŸ‹αž”αŸ’αžαžΌαžšαžœαžΆαž‘αŸ… ssl=ON. αž”αž“αŸ’αž‘αžΆαž”αŸ‹αž–αžΈαž“αŸ„αŸ‡αž…αž»αž… CTRL + O αžŠαžΎαž˜αŸ’αž”αžΈαžšαž€αŸ’αžŸαžΆαž‘αž»αž€αž€αžΆαžšαž•αŸ’αž›αžΆαžŸαŸ‹αž”αŸ’αžαžΌαžš αž“αž·αž„ CTRL + X to exit the file. This should fix the error.

αž”αŸ’αžšαžŸαž·αž“αž”αžΎαž€αžΆαžš αžœαž·αž‰αŸ’αž‰αžΆαž”αž“αž”αžαŸ’αžš SSL section error persists, contact your hosting provider for further assistance.