On October 19, 2021, we have enabled single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
If you had already registered your account at Plesk 360 (formerly known as My Plesk) please use one for login. Otherwise please re-register it using the same email address as your existing Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account.

Articles in this section

See more

Unable to access SSL/TLS Certificates for a domain: Argument 3 passed to BaseComponentChecker::getCertificateStatus() must be an instance of PleskExt\SslIt\Certificate

Avatar
Dinara Aspembitova
Updated
Follow
Plesk for Linux kb: bug ext: sslit ABT: Group B

Applicable to:

  • Plesk for Linux

Symptoms

Unable to access SSL/TLS Certificates page at Plesk > Domains > example.com. The following error is shown:

PLESK_ERROR: Server Error
500 TypeError
Argument 3 passed to PleskExt\SslIt\Entity\Domain\Component\Checker\BaseComponentChecker::getCertificateStatus() must be an instance of PleskExt\SslIt\Certificate, null given, called in /usr/local/psa/admin/plib/modules/sslit/library/Entity/Domain/Component/Checker/WwwComponentChecker.php on line 74
File BaseComponentChecker.php
Line 81

Cause

This is the bug with ID  EXTSSLIT-1183. It is going to be fixed in future SSL It! extension releases.

Resolution

Follow the article to be notified when the bug is fixed - the article will be updated.
Meanwhile, apply the  workaround below:
  1. Log into Plesk.
  2. Open Subscriptions > example.com > Account(Customize) > Additional Services.
  3. Select "none" for SSL-It.

 

Comments

3 comments

Sort by Date Votes
  • Avatar
    TomBob

    hit the issue. uninstalled and reinstalled. not a cool solution at all. got to enable hsts, "keep websites secured", and OCSP stapling for 85 domains. Not cool.

    Might help Plesk nailing down the cause (didn't check if a bug report is already filed): the way we hit the issue:

    create new client and domain for client logged in as server admin. Secure domain. Client made mistake, wants to rename domain. Set SSL cert for original domain name setup to none. Rename the hosting to new domain name. Enter SSL It to create a new cert > above error shows. For all other domains / subscriptions SSL IT still works.

    0
    Comment actions Permalink
  • Avatar
    TomBob

    now that I'm going through the domains to enable again hsts, "keep websites secured", and OCSP stapling, each of those domains (1 per subscription) has the service plan locked afterwards, no matter which plan, or which permissions and settings are enabled. Need to do a re-synch to plan on top of above.

    0
    Comment actions Permalink
  • Avatar
    Anton Maslov

    Hello Tom,

    We always stick to find a root cause, though we were not yet able to do it for this issue. Nevertheless we believe sharing workaround is still better for customers.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles