Getting error in package.json while uploading to Openshift server - node.js

I am getting following error when i am trying to push my application to Openshift server. I have updated only package.json and trying to upload it on server then it showing this error.
So i have written couple of command to find out this error. So i found the following error but i am not getting what should i do now to fix this error.
My package.json is following below. If you think that there is some error in this package.json, please inform me. It is running fine on localhost but i do not know it is not able to find out package.json.

it's possible that the existing running application is not getting stopped correctly. Try using the rhc app stop command to completely stop your application, and then ssh to your gear (rhc ssh) and use the "ps -ef" command to make sure nothing else is running that would be taking up that port.

Related

Django, unable to start on local:host

I am using dj4e in pythonanywhere.com, I am trying to start the project but it gives an error saying that port 8000 is already in use. I tried to run from another port but nothing.
In dj4e's document, it says I can't use "runserver" command in
virtualenv.
Could somebody help me running the local server, please?
You need to deploy your web app to run it on PythonAnywhere. runserver would not work there. You may follow https://help.pythonanywhere.com/pages/DeployExistingDjangoProject/

I have hosted my Nodejs Application on Amazon AWS. Now it shows 502 bad gateway after some time

I started the server using Command prompt by the command "sudo node server.js"
Then I closed the command prompt.
Now after some time, the website automatically shows 502 bad gateway error.
I had also used the command "sudo node server.js &" but it still not works.
Can you help me find out what could be the possible problem.
Thanks in advance!
The problem is that you app is not running, here is why.
When start the application in the command line, the application is handled by that bash instance. When you close that instance, so does the application.
The solution to this is to use a package like pm2 which will make sure that your application is always running.

Logs eventsource failed

I create a nodejs app.
heroku local web works perfect.
However when I pushed it to heroku and open the application, error message pops up
ui error message
When I tried heroku logs --tail, another error shows up on the console
console error.
Please help me fix this, thank you!
I am the author of this post and I figured out where the problem is by executing
heroku run bash and manually restarting the program and soon observed the error in the output.
It was because I omitted installing one dependency, which caused the nodejs program fail to start.
However, the output of heroku logs --tail still needs improving. It does not return anything useful other than a 400 error.

Node.js app showing favicon.ico path error

I have deployed a Node.js app to heroku but as I run it for first time, it works good but then some error logs come up which say npm error and favicon.ico error and then the server closes the connection. I am not getting any sort of help from their documentation. Please help me run it!!

Node.js app gives 504 on Plesk-Onyx

I have Node.js/Postgres app (tested and worked on different servers without an issue). When I try to run this app via Plesk's Node.js extension, the domain becomes inaccessible and I get 504 Gateway Time-out error.
Additionally, when I run the "start" script, Plesk panel output freezes and the only way to get an output is to run "killall node" command on SSH. After killing the node, I get the expected output without any errors.
All the dependencies are installed without any issue. Any idea what causes the problem and what is the solution?

Resources