1

I've run node.js http-server, described in my web dyno: http-server .build -p 80 Well, I've tried to stop process, kill, scale web to 0, restart... Even if web.1 disappear from heroku ps list, server still working on 80 port. And it can't be restarted with new arguments because port is already in use and I have no way to stop it. What am I doing wrong? I also tried to open heroku bash in admin panel and check ps aux or netstat, but no luck.

1 Answer 1

1

Ah! Sorry, I should not to specify port, because heroku uses random port, so my final dyno looks like this: http-server .build -p $PORT

Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.