Open regdog opened 11 years ago
I just saw this for someone else. In their case it was because their config.ru included a first line to default to port 4000. Removing this line should likely fix the issue (as heroku tries to provide a port to bind to the process and then checks for a process there).
Hi everyone,
Has anyone encountered this issue when deployed the serve app to heroku? How to solve this issue?
thanks and regards, regdog