2017-05-15 61 views
0

我想在heroku服務器上使用algolia搜索。 它在當地正常工作。然而,當它被裝載到Heroku的崩潰給這個結果:Algolia搜索導致heroku應用程序崩潰

/app/dist/algolia/algolia-manager.js:28 
2017-05-15T17:40:19.948991+00:00 app[web.1]:     throw err; 
2017-05-15T17:40:19.948991+00:00 app[web.1]:    ^
2017-05-15T17:40:19.948996+00:00 app[web.1]: AlgoliaSearchNetworkError: getaddrinfo ENOTFOUND bzkq9hqh2-1.algolianet.com bzkq9hqh2-1.algolianet.com:443 
2017-05-15T17:40:19.948998+00:00 app[web.1]:  at ClientRequest.error (/app/node_modules/algoliasearch/src/server/builds/node.js:227:14) 
2017-05-15T17:40:19.948998+00:00 app[web.1]:  at ClientRequest.g (events.js:292:16) 
2017-05-15T17:40:19.948998+00:00 app[web.1]:  at emitOne (events.js:96:13) 
2017-05-15T17:40:19.948999+00:00 app[web.1]:  at ClientRequest.emit (events.js:188:7) 
2017-05-15T17:40:19.949000+00:00 app[web.1]:  at TLSSocket.socketErrorListener (_http_client.js:309:9) 
2017-05-15T17:40:19.949000+00:00 app[web.1]:  at emitOne (events.js:96:13) 
2017-05-15T17:40:19.949001+00:00 app[web.1]:  at TLSSocket.emit (events.js:188:7) 
2017-05-15T17:40:19.949001+00:00 app[web.1]:  at connectErrorNT (net.js:1021:8) 
2017-05-15T17:40:19.949002+00:00 app[web.1]:  at _combinedTickCallback (internal/process/next_tick.js:80:11) 
2017-05-15T17:40:19.949002+00:00 app[web.1]:  at process._tickCallback (internal/process/next_tick.js:104:9) 

出現這種情況與簡單的例子託管here。 有人知道如何處理這個?

回答

2

您的APPID缺少一個字符,這就是爲什麼你看到這個錯誤。

+0

感謝問題是在heroku環境變量中的APPID不正確。一旦我修好它,它就起作用了 – xerotolerant