Articles in this section

See more

Unable to install a Symantec SSL certificate: Something went wrong with your order. Please double check configuration parameters. File not found

Avatar
Francisco Garcia
Updated
Follow

Applicable to:

  • Plesk Onyx for Linux
  • Plesk Onyx for Windows

Symptoms

  • When installing a Symantec SSL certificate at Domains > example.com > Symantec SSL, the process fails with one of the following error messages:

    PLESK_ERROR: SecureSiteStarterWildcard secure-site-starter-wildcard failed Incorrect file content.

    OR

    PLESK_ERROR: Something went wrong with your order. Please double check configuration parameters.File not found.

    OR

    PLESK_ERROR: Something went wrong with your order. Please double check configuration parameters.File Authentication Failed Due To Incorrect Content

  • The following error appears in:

    • /var/log/plesk/panel.log on Linux servers, or %plesk_dir%admin\logs\php_error.log on Windows servers

      CONFIG_TEXT: PHP Catchable Fatal Error: Argument 1 passed to Symantec\EncryptionEverywhere\ErrorException::__construct() must be an instance of Symantec\EncryptionEverywhere\Model\Error, instance of stdClass given

    • Or in same log files, but specific for symantec extension (with debug mode enabled):

      CONFIG_TEXT: ERR [extension/symantec] Common\Http\Models\RestRequest Object
      . . .
      [{"contactType":"TECHNICAL_PRIMARY","firstName":"joe","lastName":"doe","company":"companyname","email":"jdoe@example.com","phone":"0123456789"}],"domain":{"cn":"example.com"},"authType":"FILE","validityPeriodDays":365,"certFormatList":["x509"]}
      )

      ERR [extension/symantec] Common\Http\Models\RestResponse Object
      (
          [headers:Common\Http\Models\RestResponse:private] => Array
              (
                  ...
              )

          [body] => {"partnerOrderId":"ID_NUMBER_HERE","status":[{"name":"failed_file_auth","errors":[{"reason":"Incorrect file content.","key":"FILE_INCORRECT_CONTENT","field":"example.com"}]}]}
          [code] => 422
          [contentType] => application/json

  • The option Permanent SEO-safe 301 redirect from HTTP to HTTPS is enabled at Domains > example.com > Hosting Settings.

  • Domain's access log at Domains > example.com > Logs does not contain any requests to get the file /.well-known/pki-validation/fileauth.txt.

Cause

Permanent SEO-safe 301 redirect from HTTP to HTTPS prevents a Symantec SSL certificate from being installed. This is extension bug with ID #EXTCERT-1271 which will be fixed in future product updates.

Resolution

  1. Log in to Plesk

  2. Go to Domains > example.com > Hosting Settings

  3. Disable the option Permanent SEO-safe 301 redirect from HTTP to HTTPS

  4. Switch to Symantec SSL and install a required SSL certificate.

    This way domain's access log file in Domains > example.com > Logs will contain an entry like below that confirms successful connection from Symantec to install SSL:

    CONFIG_TEXT: "GET /.well-known/pki-validation/fileauth.txt HTTP/1.0" 200 338 "-" "DigiCert DCV Bot/1.1"

If an installation of Symantec SSL certificate continues to fail, contact Symantec Technical Support for further assistance.

Comments

2 comments

Sort by Date Votes

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles