• 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.

Issue All domains unavailable after enabling Node.js

Q

qf53

New Pleskian
I enabled Node.js and it's dependency Phusion Passenger server in the Plek Installer, the installation was successful.
After enabling these packages however, every single one of my domains became unavailable. Trying to visit any of them in Chrone resulted in an ERR_CONNECTION_REFUSED error. The domain's logs dod not even report any requests.


After going back to the Plesk Installer and removing Node.js and Phusion Passenger server, all of my domains became available again immediately.

Is this a common issue? I'm running Plesk Obsidian 18.0.38 on CentOS 7.9.2009
 
Is anyone familiar with this?

I simply installed Node.js and Phusion Passenger Server and all of my websites, aliases and forwards immediately stopped working.
 
You must log in or register to reply here.

Similar threads

H
Resolved Unable to Disable Node.js Application in Plesk – App Remains Accessible
Replies
1
Views
967
HawkSky
H
A
Issue Facing issues with Node.js Application Visibility Issues on Plesk Panel for Multiple Domains
Replies
0
Views
778
anjandc
A
T
Question DNS error for all domains after adding an IP
Replies
2
Views
407
teds
T
Azurel
Question Isolating Applications in Plesk – Separation of Owner Privileges and Subdomain Management Across Subscriptions?
Replies
2
Views
396
Azurel
Azurel
J
Question Plesk Firewall is blocking requests even with configured rules
Replies
2
Views
1K
Johnny9977
J
Back
Top