Recent content by proton23

I tried plesk repair fs and all domains had errors which were fixed but nothing changed in UI. I tried plesk repair all and this shows up all the time and repair will not finish. 2024 May 24 14:55:32 server A path to a valid license key file was not specified. 2024 May 24 14:55:32 server...

Hi, my root server with Ubuntu 20.04. crashed this weekend and I had to move to another server where I installed Debian 12. Luckily I have a backup ... so I thought. I tried for many hours now but I can't make it work. First of all: How do I get my User on the linux system? I always logged in...

Sorry, but I can not see how the thread can be set to "resolved"

So the support fixed my problem but in a different way. Not the port of the node.js application was changed but the port of the Plesk Antivirus Service. Since it can break every time through an update they told me how to fix it. grep -R 2999 /etc/drweb/ /etc/drweb/drweb_handler.conf:Address =...

Hi, my problem is this. I got an answer probably with a solution but I can't make it work and every few weeks I get a message that my virus definitions are outdated and/or my node.js application stops working. As it seems there is no one able to help me make it work. What else can I do? Is...

In the articel it is suggested to use I'm sorry but I don't know how to do this. Can somebody please explain?

Thanks for the reply! I'm not quite sure how this is supposed to work. Isn't app.set('port', process.env.PORT || 3000); nearly what was suggested in the article? And where will the port be set? Best regards

Hello, I was finally able to make openhab cloud work. The application is listening on port 3000 and I would like to change this since Dr.Web is using this port. The code of app.js contains this line. app.set('port', process.env.PORT || 3000); I tried to set env variable PORT to 3001, without any...

How can I mark this as resolved?

I was able to solve the problem. After activating node.js I was able to access the page but there was no process listening on port 3000. Under run nodejs commands I had to execute "run start" to make node listen on port 3000. Now all configuration works as expected. Thanks to everyone trying to...

I changed app.set('port', process.env.PORT || 3000); to app.set('port', 3000); to make sure the app is using port 3000, but after restart there is still so service listening on port 3000. The application is available when I access oh.mydomain. What am I missing here? Should I open a new thread...

So, I guess the answer is yes? How can I make the the application start on port 3000 in Plesk?

I'm not sure what you mean with toolkit. I started it with node.js dashboard from Plesk.

Actually I'm not sure. In app.js on line 117 there is app.set('port', process.env.PORT || 3000); and the application is running but if I run sudo netstat -tulpn | grep LISTEN no service is listening on port 3000.

Hi, I'm trying to make openhab cloud (GitHub - openhab/openhab-cloud: Cloud companion for openHAB instances) work on Plesk but it seems impossible for me. To explain briefly how it should work: - Local openhab instance connects with UUID and secret to openhab cloud instancen. They are connected...