{"action":"closed","issue":{"url":"https://api.github.com/repos/tajpure/hexo-editor/issues/4","repository_url":"https://api.github.com/repos/tajpure/hexo-editor","labels_url":"https://api.github.com/repos/tajpure/hexo-editor/issues/4/labels{/name}","comments_url":"https://api.github.com/repos/tajpure/hexo-editor/issues/4/comments","events_url":"https://api.github.com/repos/tajpure/hexo-editor/issues/4/events","html_url":"https://github.com/tajpure/hexo-editor/issues/4","id":168678653,"number":4,"title":"Error start script 'node server.js'","user":{"login":"JLKM","id":18215374,"avatar_url":"https://avatars.githubusercontent.com/u/18215374?v=3","gravatar_id":"","url":"https://api.github.com/users/JLKM","html_url":"https://github.com/JLKM","followers_url":"https://api.github.com/users/JLKM/followers","following_url":"https://api.github.com/users/JLKM/following{/other_user}","gists_url":"https://api.github.com/users/JLKM/gists{/gist_id}","starred_url":"https://api.github.com/users/JLKM/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JLKM/subscriptions","organizations_url":"https://api.github.com/users/JLKM/orgs","repos_url":"https://api.github.com/users/JLKM/repos","events_url":"https://api.github.com/users/JLKM/events{/privacy}","received_events_url":"https://api.github.com/users/JLKM/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-08-01T15:49:00Z","updated_at":"2016-08-02T13:40:23Z","closed_at":"2016-08-02T13:40:23Z","body":"Hexo-editor is just, what I've been waiting for. But waiting is not over yet, as it seems impossible for me to get hexo-editor running. Both on a local machine with Windows/Node 6.3.1 and on a server with Linux/Node 6.1.\r\n\r\nIt looks like, my windows-installation is closer. An upgrade to Node 6.3.1 plus a change in package.json from\r\n`jade@^1.11.0`\r\nto\r\n`pug@2.0.0-beta4`\r\nmade the road for an errorless\r\n>npm install --production\r\n\r\nBut\r\n>npm start\r\nwith Hexo running in another command-prompt still throws this error:\r\n\r\n```\r\nConnected to redis:127.0.0.1:6379\r\nHexo Editor is listening at port:2048.\r\nHexo init success.\r\nevents.js:160\r\n      throw er; // Unhandled 'error' event\r\n      ^\r\n\r\nError: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379\r\n    at Object.exports._errnoException (util.js:1012:11)\r\n    at exports._exceptionWithHostPort (util.js:1035:20)\r\n    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1080:14)\r\n\r\nnpm ERR! Windows_NT 10.0.10586\r\nnpm ERR! argv \"C:\\\\Program Files\\\\nodejs\\\\node.exe\" \"C:\\\\Users\\\\Jan\\\\AppData\\\\Roaming\\\\npm\\\\node_modules\\\\npm\\\\bin\\\\npm-cli.js\" \"start\"\r\nnpm ERR! node v6.3.1\r\nnpm ERR! npm  v3.8.1\r\nnpm ERR! code ELIFECYCLE\r\nnpm ERR! hexo-editor@1.0.0 start: `node server.js`\r\nnpm ERR! Exit status 1\r\nnpm ERR!\r\nnpm ERR! Failed at the hexo-editor@1.0.0 start script 'node server.js'.\r\nnpm ERR! Make sure you have the latest version of node.js and npm installed.\r\nnpm ERR! If you do, this is most likely a problem with the hexo-editor package,\r\nnpm ERR! not with npm itself.\r\nnpm ERR! Tell the author that this fails on your system:\r\nnpm ERR!     node server.js\r\nnpm ERR! You can get information on how to open an issue for this project with:\r\nnpm ERR!     npm bugs hexo-editor\r\nnpm ERR! Or if that isn't available, you can get their info via:\r\nnpm ERR!     npm owner ls hexo-editor\r\nnpm ERR! There is likely additional logging output above.\r\n\r\nnpm ERR! Please include the following file with any support request:\r\nnpm ERR!     D:\\vscode\\hexo\\hexo-editor\\npm-debug.log\r\n```\r\n\r\nI'm not even able to find `events.js` anywhere in the hexo-editor- or hexo-folders.\r\n\r\nAny suggestions, how I can get hexo-editor up and running?\r\n"}}
{"actor":{"display_login":"JLKM"}}