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

JSM stopped working After the telegram servers were in trouble (Windows) #27

Open
mehti1367 opened this issue Jul 29, 2018 · 3 comments

Comments

@mehti1367
Copy link

mehti1367 commented Jul 29, 2018

cant start JSM On Windows, proof:

https://uptostream.com/8edfmucvojfr

@mehti1367 mehti1367 changed the title JSM stopped working After the telegram servers were in trouble JSM stopped working After the telegram servers were in trouble (Windows) Jul 29, 2018
@PayamSoft
Copy link

I have same problem. log show as below.

0|mtproxy | Error: bind EADDRINUSE null:5478
0|mtproxy | at Object._errnoException (util.js:992:11)
0|mtproxy | at _exceptionWithHostPort (util.js:1014:20)
0|mtproxy | at listenOnMasterHandle (net.js:1415:16)
0|mtproxy | at shared (internal/cluster/child.js:115:3)
0|mtproxy | at Worker.send (internal/cluster/child.js:86:7)
0|mtproxy | at process.onInternalMessage (internal/cluster/utils.js:42:8)
0|mtproxy | at emitTwo (events.js:131:20)
0|mtproxy | at process.emit (events.js:214:7)
0|mtproxy | at emit (internal/child_process.js:772:12)
0|mtproxy | at _combinedTickCallback (internal/process/next_tick.js:141:11)

@mehti1367
Copy link
Author

I found the problem , we have to change port and secret.

@VahidN
Copy link

VahidN commented Aug 1, 2018

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

3 participants