blocks|key|4469798|text|在这里找到适合我的解决方案：Heroku+%2B+node.js+error+(Web+process+failed+to+bind+to+$PORT+within+60+seconds+of+launch)|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4469799|4469800|app.listen(process.env.PORT+%7C%7C+3000,+function(){
++console.log("Express+server+listening+on+port+%25d+in+%25s+mode",+this.address().port,+app.settings.env);
});|code-block|syntax|javascript|4469801|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/15693192/heroku-node-js-error-web-process-failed-to-bind-to-port-within-60-seconds-of^0|E|2G|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|-4|5|6|7|V|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|W|8|@]|9|@]|C|$H|I]]|$1|J|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]]]

Found solution for me here: <a href="https://stackoverflow.com/questions/15693192/heroku-node-js-error-web-process-failed-to-bind-to-port-within-60-seconds-of">Heroku + node.js error (Web process failed to bind to $PORT within 60 seconds of launch)</a>

In my case my app crashed because I was hard setting the PORT, instead of using the port that heroku dinamicaly sets, which can be accessed with <code>process.env.PORT</code>

<pre><code>app.listen(process.env.PORT || 3000, function(){
 console.log("Express server listening on port %d in %s mode", this.address().port, app.settings.env);
});
</code></pre>

blocks|key|4953189|text|我忘记从localhost更改数据库连接，一旦我的应用程序被推送到heroku，它就会崩溃。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4953190|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Also check your database connection. I forgot to change my database connection from localhost and this crashed my app once it was pushed to heroku.

blocks|key|4953222|text|我刚刚在我的应用程序上遇到了类似的问题，我在迁移数据库后遇到了这个问题，在尝试了许多选项后，一个对我有帮助的是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4953223|heroku+restart|code-block|syntax|javascript|4953224|(使用用于mac的Heroku工具带)|4953225|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I just had a similar issue with my app, I got the issue after a migration of the DB, after trying many options, the one that helped me was this:

<pre><code>heroku restart
</code></pre>

(Using Heroku toolbelt for mac)

blocks|key|1120259|text|在我的例子中，我发现了同样的错误，因为在我的本地机器上存在node和npm的版本差异，并在package.json版本中定义。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1120260|"engines":+{
++"node":+"0.8",
++"npm":+"1.2.x"
}|code-block|syntax|javascript|1120261|当我使用|1120262|node+--version+:+v0.10.41
npm+--version+:+1.4.29|1120263|当我将package.json更新为|1120264|+"engines":+{
++"node":+"0.10.41",
++"npm":+"1.4.29"
}|1120265|它运行良好:)|1120266|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

In my case, i found same error because there is version difference of node and npm on my local machine and defined in package.json version.

<pre><code>"engines": {
 "node": "0.8",
 "npm": "1.2.x"
}
</code></pre>

when i check using

<pre><code>node --version : v0.10.41
npm --version : 1.4.29
</code></pre>

when i update my package.json to 

<pre><code> "engines": {
 "node": "0.10.41",
 "npm": "1.4.29"
}
</code></pre>

It works fine :)

blocks|key|4470034|text|在我的示例中，将process.env.PORT+%7C%7C+3000添加到我的http服务器脚本的问题已解决。我的heroku日志报告'H20‘错误和503Http状态。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4470035|entityMap^0|8|O|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

in my case adding <code>process.env.PORT || 3000</code> to my http server script, resolved.
My heroku log reported 'H20' error and 503 http status.

blocks|key|4470089|text|我得到了与“应用程序崩溃”和H10错误相同的上面的错误，heroku应用程序日志没有显示太多与错误消息原因相关的信息。然后我在heroku中重新启动了dynos，然后它显示错误，说在我的设置中的一个index.js文件中有额外的大括号。这个问题在被移除并在heroku上重新部署应用程序后得到了修复。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4470090|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I got the same above error as "app crashed" and H10 error and the heroku app logs is not showing much info related to the error msg reasons. Then I restarted the dynos in heroku and then it showed the error saying additional curly brace in one of the index.js files in my setup. The issue got fixed once it is removed and redeployed the app on heroku.

blocks|key|1120396|text|在我自己的例子中，我得到了这个错误，因为我拒绝将Procfile添加到我的节点js应用程序中，并且我的"+main+"："app.js“最初指向另一个js文件作为main。所以做这些改变可以帮我把它修好|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1120397|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my own case, i got this error because i refuse to add a Procfile to my node js app and my "main": "app.js" was initially pointing to another js file as main. so doing these chnages get it fixed for me

blocks|key|4953341|text|在我的例子中，我的Procfile指向了错误的文件(我之前使用的bot.js)，所以一旦我更新了它，错误就消失了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4953342|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case, my Procfile was pointing to the wrong file (bot.js which I previously used) so once I updated it, the error was gone.

blocks|key|1120454|text|我遇到了同样的问题，上面的答案都没有帮助到我。我所做的是运行：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1120455|node+--version|code-block|syntax|javascript|1120456|在package.json中，使用您的节点版本添加engines部分：|1120457|{
++"name":+"myapp",
++"description":+"a+really+cool+app",
++"version":+"1.0.0",
++"engines":+{
++++"node":+"6.11.1"
++}
}|1120458|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I faced this same problem and none of the answers above helped me.
What i did was run:

<pre><code>node --version
</code></pre>

and in the package.json add the engines section with your node version:

<pre><code>{
 "name": "myapp",
 "description": "a really cool app",
 "version": "1.0.0",
 "engines": {
 "node": "6.11.1"
 }
}
</code></pre>

blocks|key|1120498|text|密码包含%25为我打破了它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1120499|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Password contained a % broke it for me.

blocks|key|4953389|text|我有一个打字错误|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4953390|const+PORT+=+process.env.PORT%7C%7C'8080';|offset|length|style|CODE|4953391|曾经是|4953392|const+PORT+=+process.env.port%7C%7C'8080';|4953393|entityMap^0|0|0|12|0|0|0|12|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|M|$]]

I had a typo 

<code>const PORT = process.env.PORT||'8080';</code>

used to be 

<code>const PORT = process.env.port||'8080';</code>

blocks|key|1120525|text|在我的例子中，我忘记了为部署设置数据库环境。您可以通过以下命令设置环境(我对MongoDB服务器使用mLab+)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1120526|heroku配置:set+MONGO_URI='mongodb://address‘|1120527|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

In my case, I forgot to set database env for deployment.
you can set env by this command
(I'm using mLab for MongoDB server)

heroku config:set MONGO_URI='mongodb://address'

blocks|key|1120565|text|对我来说，它是Package.json，它是空的，没有依赖项，尽管我认为我确实安装了它们。因此，我必须在最后使用--package.json选项重新安装它们，并验证它们是否已添加到保存中。然后再推一次，它就成功了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1120566|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

For me it was Package.json it was empty from dependencies even though i thought i did install them.. so I had to reinstall them with --save option in the end and verify they were added to the package.json.. and then push it again and it worked.

blocks|key|1120608|text|我的端口被设置为解析为80的config.httpPort。我通过这样做解决了这个问题：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1120609|const+PORT+=+process.env.PORT+%7C%7C+config.httpPort;

app.listen(PORT,+...)|code-block|syntax|javascript|1120610|非常感谢，昨晚浪费了我很多时间。|1120611|entityMap^0|B|2|E|F|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

My port was set to <code>config.httpPort</code> which resolves to <code>80</code>. I fixed it by doing this:

<pre><code>const PORT = process.env.PORT || config.httpPort;

app.listen(PORT, ...)
</code></pre>

Thanks a lot, it wasted me a lot of hours last night.

blocks|key|1120651|text|我有这个问题，唯一的问题是我的Procfile是这样的|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1120652|web+:+node+index.js|code-block|syntax|javascript|1120653|我改成了|1120654|web:node+index.js|1120655|唯一的问题是空格|1120656|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I had this issue, the only problem was my Procfile was like this
<pre><code>web : node index.js
</code></pre>
and I changed to
<pre><code>web:node index.js
</code></pre>
the only problem was spaces

blocks|key|324546|text|H10错误代码可能意味着许多不同的事情。在我的例子中，第一次是因为我不知道Heroku与Sqlite3不兼容，第二次是因为我不小心在开发和生产中使用Google+analytics进行了更新。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|324547|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The H10 error code could mean many different things. In my case, the first time was because I didn't know that Heroku isn't compatible with Sqlite3, the second time was because I accidentally pushed an update with Google analytics working in development as well as production.

blocks|key|4953638|text|更老的线程，但我没有在Heroku控制台中设置我的.env变量。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4953639|entityMap^0|P|4|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Older thread, but for me I didn't set my <code>.env</code> vars in the Heroku console.

blocks|key|1120760|text|我使用的是抛出异常的body-Parser|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1120761|const+bodyParser+=+require('body-Parser')++++
//Bodyparser+Middleware
app.use(bodyparser.json())|code-block|syntax|javascript|1120762|使用的完整性|1120763|++++//Bodyparser+Middleware
++++app.use(express.json())|1120764|这解决了我的问题|1120765|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

i was using body-Parser that throw exception

<pre><code>const bodyParser = require('body-Parser') 
//Bodyparser Middleware
app.use(bodyparser.json())
</code></pre>

intead of using 

<pre><code> //Bodyparser Middleware
 app.use(express.json())
</code></pre>

this resolved my issue

blocks|key|4953718|text|如果您像我一样通过nodemon在本地启动节点服务器，并且它在本地工作，那么可以尝试npm+start。Nodemon告诉我没有错误，但npm+start以一种可以理解的方式告诉了我很多错误，然后我可以通过关注这里的其他帖子来解决它们。我希望这对某些人有帮助。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4953719|entityMap^0|9|7|16|9|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

If you locally start node server by <code>nodemon</code>, like I did, and it locally works, try <code>npm start</code>. Nodemon was telling me no errors, but npm start told me a lot of them in a understandable way and then I could solve them by following another posts here. I hope it helps to someone.

blocks|key|4470604|text|我想在这里注册我对这个错误的解决方案是什么，这是一个没有更新到Github的简单文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4470605|我有一个完整的堆栈项目，我的文件是结构化的，包括后端的根目录和前端的客户端(我使用的是React.js)。这一切都归结于我错误地将客户端文件夹推送到了Github，并且我所有有错误的更改(在我的index.js中的对象实例中缺少逗号)都没有在后端更新。因为这个Heroku从Github+Repository获取所有更新，所以我无法访问我的服务器，错误仍然存在。然后，我所要做的就是提交并推送到根目录，并更新项目的所有更改，然后一切都会恢复正常。|4470606|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I want to register here what was my solution for this error which was a simple file not updated to Github.

I have a full stack project, and my files are structured both root directory for backend and client for the frontend (I am using React.js). All came down to the fact that I was mistakenly pushing the client folder only to Github and all my changes which had an error (missing a comma in a object's instance in my index.js) was not updated in the backend side. Since this Heroku fetches all updates from Github Repository, I couldn't access my server and the error persisted. Then all I had to do was to commit and push to the root directory and update all the changes of the project and everything came back to work again.

blocks|key|1120927|text|在我的例子中，package.json文件的脚本部分没有启动命令。当我使用npm+init创建package.json文件时，我没有创建启动脚本命令。因此，我转到package.json文件，在脚本下添加了一个新条目：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1120928|+"scripts":+{
++++"start":+"node+index.js"
++},|code-block|syntax|javascript|1120929|将其保存并上传到Heroku，它就起作用了|1120930|entityMap^0|7|C|11|8|1B|C|29|C|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|N|$]]

In my case there was no start command in the script section of <code>package.json</code> file.
When I created the <code>package.json</code> file with <code>npm init</code> I did not create a start script command.
So I went to the <code>package.json</code> file, under scripts I added a new entry:

<pre><code> "scripts": {
 "start": "node index.js"
 },
</code></pre>

Saved it and uploaded to Heroku and it worked

blocks|key|1120942|text|在使用hapi18时，我发现去掉“主机”字段并将端口设置为：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1120943|port:+process.env.PORT+%7C%7C+5000做到了这一点。|offset|length|style|CODE|1120944|entityMap^0|0|0|U|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

upon using hapi18, I find taking out the "host" field and setting the port to:

<code>port: process.env.PORT || 5000</code> did the trick.

blocks|key|1120976|text|在我的例子中，我有code=H10和status=503，因为我的配置文件：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1120977|web:+node+build/server.js|code-block|syntax|javascript|1120978|我将/build包含在.gitignore中|1120979|entityMap^0|9|8|I|A|0|0|2|6|B|A|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|N|$]]

In my case I had code=H10 and status=503 because my 
Procfile:

<pre><code>web: node build/server.js
</code></pre>

and I included /build in .gitignore

blocks|key|4470767|text|我在同一个错误中挣扎了几个小时，但我能够解决它。我错误地将multer和aws-sdk安装为devDependencies，而不仅仅是依赖项。所以，任何有同样错误的人，只要仔细检查你的package.json文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4470768|另外，还有一个关于package.json中引擎属性的小技巧。|4470769|enter+code+here
//The+greater+or+equal+operators+will+make+sure+that+you+use+the+right+node+
//version+
//even+if+your+current+node+is+greater+version+than+npm+node

"engines":+{
"node":+">=+0.8.14"
},


//insted+of
"engines":+{
++"node":+"0.8.14"
}|code-block|syntax|javascript|4470770|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I struggle with the same error for hours, but I was able to solve it. I installed multer and aws-sdk as a devDependencies by mistake, instead of just dependencies. 
So, anyone who has the same error, just double-check your package.json file.

Also, a small tip for the property of the engine in package.json.

<pre><code>enter code here
//The greater or equal operators will make sure that you use the right node 
//version 
//even if your current node is greater version than npm node

"engines": {
"node": "&gt;= 0.8.14"
},


//insted of
"engines": {
 "node": "0.8.14"
}
</code></pre>

blocks|key|4470798|text|旧线程，但我通过将端口常量设置为process.env.PORT+%7C%7C来修复此问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4470799|出于某种奇怪的原因，它想先搜索Env。|4470800|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Old Thread, but I fix this issue by setting PORT constant to process.env.PORT || 

For some weird reason, it wanted to search Env first.

blocks|key|4470809|text|我在部署python+Django框架时遇到了这个错误，因为我忘了把我的应用程序名web:+gunicorn+plaindjango.wsgi:application+--log-file+-而不是plaindjango|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4470810|entityMap^0|15|1J|2R|B|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

I was deploying python Django framework when I got this error because I forget to put my app name <code>web: gunicorn plaindjango.wsgi:application --log-file -</code> instead of <code>plaindjango</code>

blocks|key|4954016|text|对我来说，我把东西不必要地拆分到不同的文件夹中。我正在运行plotly，我将我的Procfile、Pipfile+(和锁)放在一起，但与我的应用程序的其他功能(run.py和app.py，实际使用的页面内容在一个子文件夹中)是分开的。因此，将这些结合在一起就修复了我的H10错误|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4954017|entityMap^0|14|8|1D|7|28|6|2F|6|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|G|$]]

For me, I had things unnecessarily split into separate folders. I'm running plotly dash and I had my <code>Procfile</code>, and <code>Pipfile</code> (and lock) together, but separate from the other features of my app (<code>run.py</code> and <code>app.py</code>, the actual content of the pages being used was in a subfolder). So joining much of that together repaired my H10 error

blocks|key|4954087|text|我的start命令有env-cmd+-f+./config/prod.env+node+index.js。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4954088|在更改为：node+index.js后，它得到了修复。|4954089|entityMap^0|2|5|A|16|0|5|D|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|I|$]]

My <code>start</code> command had <code>env-cmd -f ./config/prod.env node index.js</code>.
after changing to: <code>node index.js</code> it got fixed.

blocks|key|1121239|text|我也遇到了同样的问题，问题是我的个人资料是这样的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1121240|web:+gunicorn__init__:app|offset|length|style|CODE|1121241|请注意，在上面的代码中，gunicorn和__+init+__之间没有空格|BOLD|1121242|代替web:+gunicorn+__init__:app|1121243|entityMap^0|0|0|P|0|C|8|L|A|0|2|Q|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|S|8|@$D|T|E|U|F|J]|$D|V|E|W|F|J]]|9|@]|A|$]]|$1|K|3|L|5|6|7|X|8|@$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|N|$]]

I got the same issue, the problem was my Profile was like this:
<code>web: gunicorn__init__:app</code>
Notice with the above there was no space between gunicorn and __ init __
instead of
<code>web: gunicorn __init__:app</code>

I deployed my app to Heroku. It's a node.js + express + socket.io app and this is the <code>package.json</code> file

<pre><code>{
 "name": "game_test",
 "author": "Ilya",
 "description": "A test app for our board game",
 "version": "0.0.1",
 "private": true,
 "scripts": {
 "start": "node app"
 },
 "dependencies": {
 "express": "3.0.6",
 "jade": "*",
 "socket.io" : "*"
 },
 "engines": {
 "node": "0.8.14"
 }
}
</code></pre>

This is the log I get:

<pre><code>heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=game-test-1.herokuapp.com fwd=37.26.146.185 dyno= queue= wait= connect= service= status=503 bytes=
heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=game-test-1.herokuapp.com fwd=37.26.146.185 dyno= queue= wait= connect= service= status=503 bytes=
</code></pre>

What does it mean?

First Heroku deploy failed `error code=H10`

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我将我的应用程序部署到Heroku。这是一个node.js + express + socket.io应用程序，这是package.json文件{  "name": "game_test",  "author": "Ilya",  "description": "A test app for our board gam...

问第一次Heroku部署失败` `error code=H10`
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问第一次Heroku部署失败` `error code=H10`EN