Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run an error after the update #11

Open
zhq1 opened this issue Jul 23, 2018 · 2 comments
Open

Run an error after the update #11

zhq1 opened this issue Jul 23, 2018 · 2 comments

Comments

@zhq1
Copy link

zhq1 commented Jul 23, 2018

018-07-23 15:33:46 [Payments] [bitcoinpay] Payment processing setup with daemon ([email protected]:8379) and redis (127.0.0.1:6379)
events.js:183
throw er; // Unhandled 'error' event
^

Error: bind EADDRNOTAVAIL 47.75.77.92:80
at Object._errnoException (util.js:1022:11)
at _exceptionWithHostPort (util.js:1044:20)
at listenOnMasterHandle (net.js:1411:16)
at rr (internal/cluster/child.js:111:12)
at Worker.send (internal/cluster/child.js:78:7)
at process.onInternalMessage (internal/cluster/utils.js:42:8)
at emitTwo (events.js:131:20)
at process.emit (events.js:214:7)
at emit (internal/child_process.js:772:12)
at _combinedTickCallback (internal/process/next_tick.js:141:11)
2018-07-23 15:33:46 [Master] [Website] Website process died, spawning replacement...

@zhq1
Copy link
Author

zhq1 commented Jul 23, 2018

No error will be reported when using the previous version, but it is not sure whether it is out of the block.

@TheComputerGenie
Copy link

EADDRNOTAVAIL

Means that you're already using the port in the config (in this case, port 80) for something else. Change the port in config to an unused portand the error will go away.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants