• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

How to add ssl let's encrypt to https://server:8443 plesk ?

Hi @WSNHosting

I believe if you set up a hosting account in Plesk with the same domain as the server hostname, when creating a Let's Encrypt certificate for that account it will ask if you would like to secure Plesk with it.
 
NOT WORKING;

Code:
Error: Let's Encrypt SSL certificate installation failed: Failed letsencrypt execution: Failed authorization procedure. www.ZZZZZ.kraftysprouts.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: NXDOMAIN looking up A for www.zzzzzzz.kraftysprouts.com
IMPORTANT NOTES:
- If you lose your account credentials, you can recover through
e-mails sent to hello @ kraftysprouts.com.
- The following errors were reported by the server:

Domain: www.ZZZZZZ.kraftysprouts.com
Type: connection
Detail: DNS problem: NXDOMAIN looking up A for
www.zzzzzzzzz.kraftysprouts.com

To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you're using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.
- Your account credentials have been saved in your Let's Encrypt
configuration directory at /opt/psa/var/modules/letsencrypt/etc.
You should make a secure backup of this folder now. This
configuration directory will also contain certificates and private
keys obtained by Let's Encrypt so making regular backups of this
folder is ideal.
 
Hi Kingsley,

please make sure, that you have a corresponding A - DNS entry for the subdomain, before you proceed/test another Let's encrypt SSL certificate installation. As you can see in the error message:

Domain: www.ZZZZZZ.kraftysprouts.com
Type: connection
Detail: DNS problem: NXDOMAIN looking up A for
www.zzzzzzzzz.kraftysprouts.com

... there is no DNS - entry for "www.zzzzzzzzz.kraftysprouts.com".

The actual DNS - entries for the domain "kraftysprouts.com" are:
Code:
Name    TTL    Class    Type    Priority    Data
kraftysprouts.com.    1800    IN    SOA         ns1.digitalocean.com. hostmaster.kraftysprouts.com. 1459117648 10800 3600 604800 1800
kraftysprouts.com.    1800    IN    NS         ns3.digitalocean.com.
kraftysprouts.com.    1800    IN    NS         ns1.digitalocean.com.
kraftysprouts.com.    1800    IN    NS         ns2.digitalocean.com.
kraftysprouts.com.    1800    IN    A         104.219.248.26
kraftysprouts.com.    1800    IN    MX    10    mx.zoho.com.
kraftysprouts.com.    1800    IN    MX    20    mx2.zoho.com.

Please keep in mind, that with your actual configuration, the primary DNS - server is not your rented server, but the DNS - server from DigitalOcean. You always have to set up DNS - entries over your domain provider, the additional possible entries over Plesk are optional.
 
Hi Kingsley,

please make sure, that you have a corresponding A - DNS entry for the subdomain, before you proceed/test another Let's encrypt SSL certificate installation. As you can see in the error message:



... there is no DNS - entry for "www.zzzzzzzzz.kraftysprouts.com".

The actual DNS - entries for the domain "kraftysprouts.com" are:
Code:
Name    TTL    Class    Type    Priority    Data
kraftysprouts.com.    1800    IN    SOA         ns1.digitalocean.com. hostmaster.kraftysprouts.com. 1459117648 10800 3600 604800 1800
kraftysprouts.com.    1800    IN    NS         ns3.digitalocean.com.
kraftysprouts.com.    1800    IN    NS         ns1.digitalocean.com.
kraftysprouts.com.    1800    IN    NS         ns2.digitalocean.com.
kraftysprouts.com.    1800    IN    A         104.219.248.26
kraftysprouts.com.    1800    IN    MX    10    mx.zoho.com.
kraftysprouts.com.    1800    IN    MX    20    mx2.zoho.com.

Please keep in mind, that with your actual configuration, the primary DNS - server is not your rented server, but the DNS - server from DigitalOcean. You always have to set up DNS - entries over your domain provider, the additional possible entries over Plesk are optional.

i have added www.zzzzz.kraftysprouts.com A IP to DO DNS manager still did not work.... i use external DNS as i feel more comfortable with it (might change my mind)
 
Hi Kingsley,

i have added www.zzzzz.kraftysprouts.com A IP to DO DNS manager still did not work.... i use external DNS as i feel more comfortable with it (might change my mind)

DNS - changes ( or new entries ) may take up to 48-72 hours, untill they are synchronized, please keep that in mind, if you "test and play" with your settings.
Apart from that, you are actually using cPanel for your configuration on your server, so please consider to ask the cPanel - support to help you with their software.
 
Hi Kingsley,



DNS - changes ( or new entries ) may take up to 48-72 hours, untill they are synchronized, please keep that in mind, if you "test and play" with your settings.
Apart from that, you are actually using cPanel for your configuration on your server, so please consider to ask the cPanel - support to help you with their software.

What do you mean am using CPANEL? Why would i come to plesk forum and ask for cpanel support? Do i look stupid?

Credit Card Receipt: Plesk
Hello Kingsley Felix,

Your Invoice 03-2016-304398 in the amount of $4.00 has been processed and approved.

PAYMENT INFORMATION
Credit Card Type: MasterCard
Credit Card Number: 7778
Transaction Date/Time: 3/23/16 5:40 PM
Transaction ID: 8097078329
Auth Return: 1
Auth Code: 551592
AVS Code: P
Transaction Amount: $4.00
Notes: This transaction has been approved.
You will see a charge from Plesk for this transaction.

Thank you,
Plesk

Wednesday, March 23, 2016 5:40:35 PM Europe/Berlin

BILLING

To download your product licenses, view or pay your invoices, manage your subscriptions and billing details log in to our client billing system at:

https://shop.plesk.com/login
Username: iamkingsleyf

Need help with your password? Visit the URL above and click the Forgot your password? link to retrieve your password.

SUPPORT

For answers to licensing and purchase questions, seeKB126078.
For other Support inquiries, please visit Plesk Support Home.

CONTACT

Plesk
Vordergasse 59,
Schaffhausen, 8200
+41 31 528 12 23
 
Hi Kingsley,

my above statement is based on the fact, that opening the URL http://zzzzz.kraftysprouts.com ( 104.219.248.26 ) or http://s134.web-hosting.com ( 104.219.248.26 ) redirects to http://zzzzz.kraftysprouts.com/cgi-sys/defaultwebpage.cgi or http://s134.web-hosting.com/cgi-sys/defaultwebpage.cgi actually lead to a cPanel error page. There is no need to discuss this ( especially not in the public forum ) and there is no need at all, that you think, that you have to provide additional informations.
In addition, I'm very surprised that you feel insulted or offended, - I overread my posts and didn't find any possible reason, that you might feel insulted or offended by me, but feel free to discuss that in a private conversation with me, if you wish to.
 
Hi Kingsley,

my above statement is based on the fact, that opening the URL http://zzzzz.kraftysprouts.com ( 104.219.248.26 ) or http://s134.web-hosting.com ( 104.219.248.26 ) redirects to http://zzzzz.kraftysprouts.com/cgi-sys/defaultwebpage.cgi or http://s134.web-hosting.com/cgi-sys/defaultwebpage.cgi actually lead to a cPanel error page. There is no need to discuss this ( especially not in the public forum ) and there is no need at all, that you think, that you have to provide additional informations.
In addition, I'm very surprised that you feel insulted or offended, - I overread my posts and didn't find any possible reason, that you might feel insulted or offended by me, but feel free to discuss that in a private conversation with me, if you wish to.

Hello UFHH01

You statement made it look like am stupid that i don't know were cpanel support is, all you should done is ask why zzzz is redirecting to a cpanel error page then i will explain to you instead of assuming am using cpanel.

I once had a 4G server at vultr with plesk 12.5 installed all was well until on the 9th day all the domains went off and keep popping up 504 error across 10 domains. All solutions i tried didn't work because if i restart nginx/apache/php-fpm it will be back online and still go offline making me lose money and ranks.

Tried the same setup on centos 7, same issues so i decided to use HHVM my usual set up but moving 9 domains to hhvm is stressful so i decided to buy namecheap hosting for the niche and smaller sites why the big ones are still using plesk
 
Why zzzz is redirecting to cpanel error page is because kraftysprouts.com is hosted on namecheap why server1.kraftysprouts.com and analytics.kraftysprouts.com is on PLESK.


Thanks for help
 
For what is worth: make sure you create a domain in Plesk with the host that you use to access Plesk.

For example, I have a VPS on OVH, so my host is vps#######.ovh.net (####### being some numbers) and I had to create that domain in Plesk, while before only my main site's domain was configured. Now if I open vps#######.ovh.net in the browser on port 80 I get the default domain page, while if I use port 8443 then Plesk opens. Since vps#######.ovh.net is accessible via DNS, there are no problems for the Let's Encrypt tool to do its thing (it needs to be accessed from outside — that's why it doesn't work if the current domain for Plesk is not configured on the public DNS).

When using Let's Encrypt's module, the checkbox for using the certificate with Plesk appears only if the currently visited domain is the same as the one being configured.
 
Also, since opening port 80 in the now configured domain opens the default site page, I deleted index.html from httpdocs and added a 4-lines index.php file to simply redirect to Plesk

PHP:
<?php

if ($_SERVER['SERVER_PORT'] != 8443) {

    header('Location: https://vps#######.ovh.net:8443');
    exit;

}
 
Back
Top