-
Notifications
You must be signed in to change notification settings - Fork 337
Client cant connect to server #67
Comments
The default server port is 6060. Did you change that in client.js? |
i repulled the repo at setup and i got this Started server on 0.0.0.0:6060 events.js:85 |
You must have another program claiming port 6060. (Hence the EADDRINUSE). |
do i just change the port on both server and client and do i run the server and client on the same machine |
Whatever port you chose, the WebSocket address in client.js has to match the port of the server. You could run the server and client on the same or different machines, your choice. |
okay my server is running on 127.0.0.1:8080 and its loaded with no errors and my client is running on http://0.0.0.0:8080 but when i load the client url it loads and when i click a room it loads it and then just does nothing this is the log from the client Starting up http-server, serving ./ on: http://0.0.0.0:8080 |
you also need to start the |
i have i changed the port and now when i click a channel it says not implemented yet |
i got it working it was just the order i started them in thank this program is great |
one more thing how do i log in as admin |
Let your nickname be I should really put that info into the README. |
one more thing how do i change the ip of the http server |
I don't understand your question. Your IP is determined by the machine you are hosting the server from. |
when i start the http server for the client the default ip os 0.0.0.0 and the servers ip is 0.0.0.0 how do i change the client and server ip and do they have to be the same |
Those are binding IPs. If the servers are hosted from the same machine, they have the same IP address. |
i am trying to set this up locally i have the server on 0.0.0.0:6000 and the client on 0.0.0.0:8080 but when i open a channel on the client it loads and just stays there without showing the nickname window
The text was updated successfully, but these errors were encountered: