• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Forwarded to devs Error 500 when opening "Let's Encrypt" Icon after fresh install

Bitpalast

Plesk addicted!
Plesk Guru
TITLE:
Error 500 when opening "Let's Encrypt" Icon after fresh install
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Plesk 17.8
CentOS 7.6
Latest patches
PROBLEM DESCRIPTION:
After a Plesk fresh installation, when clicking on the "Let's Encrypt" icon of a new subscription, the panel shows an error 500.

When going through the "Extensions" page and opening Let's Encrypt overview there, clicking on the same domain, the certificate intallation dialog shows up. But not when opened from the subscription page.

Error is: "Call to a member function getMessage() on null" (see screenshot)letsencrypt_error.jpg
STEPS TO REPRODUCE:
Create a standard installation of Plesk 17.8 with Let's Encrypt extension. Create a subscription, wait until web server has restarted so that the subscription domain is accessible. Then click the "Let's Encrypt" icon on "websites and domains" tab of the subscription.​
ACTUAL RESULT:
See screenshot​
EXPECTED RESULT:
Certificate installation dialogue.​
ANY ADDITIONAL INFORMATION:
After running "plesk repair installation" on the console, the error is solved, however no errors were indicated during repair.
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug
 
From developers:

It looks like an inconsistency on the customer's server. Could you please provide access to the server? Also, an error message in panel.log (actually, exception stacktrace) would be useful to find the root cause.
 
The only entries regarding this error in panel.log (several attempts to open the page):

[2019-01-26 19:30:59.857] ERR [1] DB query failed:
[2019-01-26 19:31:00.287] ERR [panel] Call to a member function getMessage() on null:
[2019-01-26 19:31:00.290] ERR [1] Call to a member function getMessage() on null
[2019-01-26 19:31:12.410] ERR [1] DB query failed:
[2019-01-26 19:31:12.897] ERR [panel] Call to a member function getMessage() on null:
[2019-01-26 19:31:12.899] ERR [1] Call to a member function getMessage() on null
[2019-01-26 19:31:19.230] ERR [1] DB query failed:
[2019-01-26 19:31:19.685] ERR [panel] Call to a member function getMessage() on null:
[2019-01-26 19:31:19.687] ERR [1] Call to a member function getMessage() on null
[2019-01-26 19:31:30.433] ERR [1] DB query failed:
[2019-01-26 19:31:30.906] ERR [panel] Call to a member function getMessage() on null:
[2019-01-26 19:31:30.907] ERR [1] Call to a member function getMessage() on null
[2019-01-26 19:32:05.126] ERR [1] DB query failed:
[2019-01-26 19:32:05.574] ERR [panel] Call to a member function getMessage() on null:
[2019-01-26 19:32:05.576] ERR [1] Call to a member function getMessage() on null

No more data available.
 
Peter, according to developers this info is not enough to understand the reason.
Do you have any additional details?
 
I do not have any additional information, and on the latest new machine that I installed a few days ago, this issue did not show up. I think it could be due to the ECDSA certificate type, because last time on the installation of a test server where this happened, I had previously set that change in the panel.ini file before attempting to create the certificate. As this does not work for mail server protection I waived the procedure for other systems, so that could be a reason why it did not occur again.
 
Back
Top