• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Resolved NodeJS extension broken after latest update

darkobgd

New Pleskian
Server operating system version
CentOS Linux 8.5.2111
Plesk version and microupdate number
Plesk Obsidian v18.0.41_build1800220207.23 os_CentOS 8
VersionPlesk Obsidian v18.0.41_build1800220207.23 os_CentOS 8
OSCentOS Linux 8.5.2111

After NodeJS Toolkit extension update(i guess, i didn't log in at all from 3rd July, everything was ok), NodeJS section under Websites&Domains is empty.

Plesk Log Browser says this:

2023-07-10 02:20:16ERRpanel.ui [90515:64ab4ec051031]attribute name is invalid: application
2023-07-10 02:20:16ERRpanel [90515:64ab4ec051031]
pm_Exception: attribute name is invalid: application
file: /usr/local/psa/admin/plib/pm/Domain.php
line: 225
code: 0
trace: #0 /usr/local/psa/admin/plib/modules/nodejs/controllers/ApiController.php(495): pm_Domain->getProperty(string 'application')
#1 /usr/local/psa/admin/plib/modules/nodejs/controllers/ApiController.php(163): ApiController->getUsedApplicationPaths(array)
#2 /usr/local/psa/admin/plib/vendor/plesk/zf1/library/Zend/Controller/Action.php(516): ApiController->applicationAction()
#3 /usr/local/psa/admin/plib/vendor/plesk/zf1/library/Zend/Controller/Dispatcher/Standard.php(308): Zend_Controller_Action->dispatch(string 'applicationAction')
#4 /usr/local/psa/admin/plib/vendor/plesk/zf1/library/Zend/Controller/Front.php(954): Zend_Controller_Dispatcher_Standard->dispatch(object of type Zend_Controller_Request_Http, object of type Zend_Controller_Response_Http)
#5 /usr/local/psa/admin/plib/pm/Application.php(91): Zend_Controller_Front->dispatch()
#6 /usr/local/psa/admin/htdocs/modules/nodejs/index.php(5): pm_Application->run()

Only change, beside logins from 03.07 until now is this:

127.0.0.1 admin [2023-07-08 03:30:38] 'Upgrade extension' ('Extension Id': 'nodejs' => 'nodejs', 'Extension Name': 'Node.js Toolkit' => 'Node.js Toolkit', 'Extension Release': '297' => '312', 'Extension Version': '2.3.4' => '2.3.5')

Any help? Thanks in advance.
 

Attachments

  • Screenshot 2023-07-10 022042.png
    Screenshot 2023-07-10 022042.png
    76.7 KB · Views: 10
I believe that this issue has not been seen yet. Please open a ticket with Plesk support.

To sign-in to support please go to https://support.plesk.com

If you experience login issues, please see this KB article:
https://support.plesk.com/hc/en-us/...rt-plesk-com-and-password-reset-does-not-work

If you bought your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative:
https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk-
 
@royce, yes, PPS-14684 has been resolved, however it turned out in this case that an individual issue existed on the server that had no standard solution but needed an individual intervention. The cause was not something that the Plesk software could have fixed. For privacy reasons I cannot give you more details.

Instead, I suggest you open a new thread with an error description and steps-to-reproduce your own case.
 
Back
Top