search

flackr / circ

An IRC packaged chrome app
BSD 3-Clause "New" or "Revised" License
387 stars 79 forks source link

join-server command does not work under ChromeOS #223

Open vendion opened 11 years ago

vendion commented 11 years ago

On my Chromebook running ChromeOS: 30.0.1599.101 circ is unable to connect to my Linux desktop, also running Chrome 30 and Circ in server mode. I have no problems getting Circ on my Macbook Pro to connect to the Linux box, in fact circ connected to the remote server without me having to run the join-server command.

I don't know if the problem lays with Google now allowing outbound connections on port 1329, or what but because my Mac had no problems it either points to Circ or ChromeOS.

flackr commented 10 years ago

This is still working regularly for me, can you verify that you can connect directly to your linux desktop from your chromebook when this is failing? Perhaps by opening crosh (Ctrl+Alt+T) and pinging your desktop ip address.

vendion commented 10 years ago

Well the odd thing is it works fine on my HP Chromebook 11, but does not work on my Samsung Series 5 550 chromebook. From my samsung chromebook I can ping my Linux box running CIRC in server mode, but I can not connect to it from CIRC on it, I get "Unable to connect to the server device 192.168.1.21 on port 1329". This is my only box that has a problem with this.

On Thu, Nov 21, 2013 at 11:01 AM, Robert Flack notifications@github.comwrote:

This is still working regularly for me, can you verify that you can connect directly to your linux desktop from your chromebook when this is failing? Perhaps by opening crosh (Ctrl+Alt+T) and pinging your desktop ip address.

— Reply to this email directly or view it on GitHubhttps://github.com/flackr/circ/issues/223#issuecomment-28996494 .

flackr commented 10 years ago

Actually it sounds like you're having a problem with sync. The server generates a random password that the client must hash a challenge with in order to not allow just anyone to connect to your server instance. This is sent to the clients (as well as the server's ip) using chrome sync storage. If you run /get-pw on your server instance and your samsung chromebook, I'd bet they have different passwords. You can use /set-pw to fix it but the underlying problem sounds like they're not using the same chrome profile or chrome sync is not working or turned off.

vendion commented 10 years ago

According to my samsung chromebook, it is syncing everything with my Google account, and chrome://sync-internals shows it is working. Running /get-pw on both machines returns the same password, but yet /join-server fails. If I wait long enough I get a "Socket Error: Invalid write on socket, code: -101." error as well as the "Unable to connect" error.

On Fri, Nov 22, 2013 at 9:12 AM, Robert Flack notifications@github.comwrote:

Actually it sounds like you're having a problem with sync. The server generates a random password that the client must hash a challenge with in order to not allow just anyone to connect to your server instance. This is sent to the clients (as well as the server's ip) using chrome sync storage. If you run /get-pw on your server instance and your samsung chromebook, I'd bet they have different passwords. You can use /set-pw to fix it but the underlying problem sounds like they're not using the same chrome profile or chrome sync is not working or turned off.

— Reply to this email directly or view it on GitHubhttps://github.com/flackr/circ/issues/223#issuecomment-29074814 .

vendion commented 10 years ago

This seems related to Issue #240