• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue pki-validation nginx and sectigo issue

psupena

New Pleskian
Hello! Hopefully someone can give me some insights into this.

So basically before, we could use file based domain control verification by just uploading txt files from SSL providers to the httpdocs/.well-known/pki-validation/ folder of sites.

However recently, (possibly after an update), ALL files under httpdocs/.well-known/pki-validation/ of ANY domain either gets redirected or 404s.

After some investigation we think it might be the vhost configuration added by the Sectigo extension



Code:
location ^~ /.well-known/pki-validation/ {
            root /var/www/vhosts/default/htdocs;             

            types { }
            default_type text/plain;

            satisfy any;
            auth_basic off;
            allow all;

            location ~ ^/\.well-known/pki-validation.*/\. {
                    deny all;
            }
    }
    #extension sectigo end **


The trouble is, not everyone can really upload to /var/www/vhosts/default/htdocs via the normal plesk GUI. You need some command line experience.

So my question is.. Is it possible to override this under the additional nginx directives? I get a "duplicate location" error if I try to alter some of these rules, or they just don't work really.

Or does this mean we are stuck getting ssls only from the plesk interface, or via CNAME verification (which we don't have access in some cases).


Our goal basically is to be able to once again upload those DCV files on httpdocs/.well-known/pki-validation/ without having to resort to using the command line to get them to /var/www/vhosts/default/htdocs .

Any help would be greatly appreciated! Thanks!
 
I faced to same problem here.

We need upload authenticate file from third party SSL issuer, and use the /.well-known/pki-validation/ path as authentication. But this path has been hijacked by Sectigo extension...

Hope some one can point us a solution.
 
Back
Top