Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
The APS Catalog has been deprecated and removed from all Plesk Obsidian versions. Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.
My passenger.log file only contains those updating statistics logs and does not contain any logs from my node application.
Also in the log viewer in plesk, selecting node in the drop-down shows nothing for me and the other users with this problem from the link in my initial post above
Username:
TITLE
NodeJS Application logs are completely broken
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Plesk Obsidian 18.0.48, Ubuntu 22.04.1
PROBLEM DESCRIPTION
Application logs for nodejs do not work...
Logging for nodejs has been broken for a very long time. The above folks have this issue, I do and even other folks online report it:
https://support.plesk.com/hc/en-us/articles/360021105674-Where-are-the-Node-js-logs-located-
Alex can you please help us friend?
Hello friend, unfortunately none of the paths listed there for nodejs show any logs for me. In fact, none of these files exist or are all empty except for /var/log/nginx/error.log which just says:
2022/11/29 01:17:42 [notice] 197899#0: using inherited sockets from "9;10;11;12;13;14;"
Hi friend,
I also had this issue and solved it by wrapping the module file in a commonJS file, and using that as the entrypoint for my app.
For example lets say your main file is index.js, then create a file called index.cjs and do this:
and then in plesk in the nodejs extension for your app...
I have my nodejs app working perfectly with the nodejs that uses passthrough in plesk!
My only issue though is sadly I can't see the logs of my running app. Meaning, console.log/error or any stdout or stderr from node does not seem to get logged anywhere I can find.
In the log viewer I tried...