• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Recent content by proton23

  1. P

    Resolved Cannot make nodejs application listen on different port

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

    Resolved Cannot make nodejs application listen on different port

    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 =...
  3. P

    Resolved How can I get help if the forum is not able to?

    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...
  4. P

    Resolved Cannot make nodejs application listen on different port

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

    Resolved Cannot make nodejs application listen on different port

    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
  6. P

    Resolved Cannot make nodejs application listen on different port

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

    Resolved "502 Bad Gateway" with nginx reverse proxy for openhab cloud

    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...
  8. P

    Resolved "502 Bad Gateway" with nginx reverse proxy for openhab cloud

    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...
  9. P

    Resolved "502 Bad Gateway" with nginx reverse proxy for openhab cloud

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

    Resolved "502 Bad Gateway" with nginx reverse proxy for openhab cloud

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

    Resolved "502 Bad Gateway" with nginx reverse proxy for openhab cloud

    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.
  12. P

    Resolved "502 Bad Gateway" with nginx reverse proxy for openhab cloud

    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...
  13. P

    Resolved phusion passenger application is supposed to run on Plesk and throws an error

    I did it all over again and I don't know what I did different this time, it works now. :)
  14. P

    Resolved phusion passenger application is supposed to run on Plesk and throws an error

    I have no other nodejs app running so I can not say. I've seen this post but since the message there is: and the message on my site is: I thought this was a different issue. I switched to zsh in the meantime but the error remains (with zsh instead of bash). So I don't think removing .bashrc...
Back
Top