Resolved Node.JS panel suddenly blank for domains with a subdomain

[tacriela]

Server operating system version

Debian 9.13.0

Plesk version and microupdate number

18.0.44

When I logged in to my Plesk today to upgrade a Node.JS site, I noticed the page wouldn't load and I noticed a lot of errors appearing in my debug console. After some debugging, I found out that Node works perfectly fine on a singular site, until I add a subdomain to that site. Once I add a subdomain to a site, I get a blank screen and the errors appear in the console. I suspect this is due to the Node.JS Toolkit version 2.3.5 update, but I'm not sure. I never had this problem before, and Plesk auto-updated the package a few days ago. Refer to the screenshots below to see how it's expected to work, what it actually does, and what errors appear in the console.


Expected



Actual



Console

PS: I already tried reinstalling the Node.JS Toolkit, but unfortunately with no success.

 

[Peter Debik]

Duplicate to Issue - NodeJS extension broken after latest update

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-

 

[ShayLash]

Duplicate to Issue - NodeJS extension broken after latest update

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-

Hi,
Any news on this. This is very impacting for us as we rely on node on several instance of Plesk and multiple servers. And if no fix is found how can I revert to the previous version of the Node.js Toolkit.

Thanks

 

[Peter Debik]

It is under investigation as ID PPS-14684.

 

[basano]

Dear Peter, I've got the same problem. How do I find updates on the ticket that you mentioned? Is there any workaround for us?

 

[basano]

Hi @Peter Debik , I really hope this issue gets solved quickly. I also have subdomains on my server, same as the OP. This is my console output client side when opening the Node.js page in Plesk 18.0.48:

Probably, I should change my business to some other software?

 

[Peter Debik]

@basano You are using a very old Plesk version (18.0.48). Please first update to the latest version (18.0.54), then check again if this issue persists.

 

[basano]

Hi @Peter Debik , I updated to 18.0.52 through the internal plesk updater and now it seems to work again. Great!
BTW: I also found out, that auto updates were not activated:

Now it is activated.

 

[ShayLash]

Hi @Peter Debik ,
What if we can't update right now due to the debian version (We are migrating but need this to work right now). My version of Plesk is 18.0.44. How can I downgrade the NodeJs extension to the previous version that was working fine (auto update was on and as you can see is not always a good solution). Please keep me posted as it is blocking us at the moment.
Thanks for you time and have a good day

 

[Peter Debik]

@ShayLash Plesk does not support such downgrades. One reasons is that Linux is a complex system with many dependencies. It is not actually the extension you'd need to downgrade, but also NodeJS and other files. These again may not work properly with newer version of other files etc.