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

on server side error starting collaboration server port already in use?? #9

Open
careyjames opened this issue Jul 24, 2019 · 3 comments

Comments

@careyjames
Copy link

careyjames commented Jul 24, 2019

on server side I'm getting an error when I launch the server with:
./empire --server --shared_password password --port 1337
"error starting collaboration server port already in use"??

I did already set a listener to that port...

also on the client GUI side, I'm getting refused to connect messages:

socket.io.min.js:1 GET https://xxx.xx.xxx.xxx/socket.io/?EIO=3&transport=polling&t=1564004359993-38 net::ERR_CONNECTION_REFUSED
i.create @ socket.io.min.js:1
i @ socket.io.min.js:1
o.request @ socket.io.min.js:1
o.doPoll @ socket.io.min.js:1
n.poll @ socket.io.min.js:2
n.doOpen @ socket.io.min.js:2
n.open @ socket.io.min.js:1
r.open @ socket.io.min.js:1
r @ socket.io.min.js:1
r @ socket.io.min.js:1
n.open.n.connect @ socket.io.min.js:1
(anonymous) @ socket.io.min.js:1
@careyjames
Copy link
Author

I also had trouble when I was setting up the listener to that port also, so should I set up the listener first without using: ./empire --server --shared_password password --port 1337 to login?

@careyjames
Copy link
Author

and another thing is, do we "set Port" or put the port in our address like xxx.xx.xxx.xx:1337

@careyjames
Copy link
Author

error no 98

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

1 participant