SamePlace

Can't change port # for gmail/google talk

Asked by Mike

Like the subject line says - I simply can't change the port #. The default 443 is blocked by our network, and I thought I'd change it to 5222. It's as though the port box isn't actually a text field. I can put the cursor in it, but nether the regular numbers, nor the number pad work... Any thoughts?

Oh - I'm using Firefox 2.0.0.12

Question information

Language:
English Edit question
Status:
Solved
For:
SamePlace Edit question
Assignee:
No assignee Edit question
Solved by:
Mike
Solved:
Last query:
Last reply:

This question was reopened

  • by Mike
Revision history for this message
Massimiliano Mirra (bard-hyperstruct) said : 		#1

Hi Mike,

please see https://bugs.launchpad.net/sameplace/+bug/193261, this is fixed in devel branch and will be in 0.9.2.

Revision history for this message
Mike (ubergruvn) said : 		#2

Thanks Bard!

PS - I did a search for the problem, but the bug report didn't turn up.

Revision history for this message
Mike (ubergruvn) said : 		#3

Hey Bard, Thought you'd want to know -

I downloaded the development version, and i was then able to change the port number. However, I could still not connect. It just hangs there on port 5222 (tried with and without SSL). I compared the SamePlace settings with a functioning KoolIM installation which works (on the same machine), and as far as I can tell, they're setup identical (eg host name - talk.google.com, port 5222, and same user account) , but sameplace doesn't connect. I also tried port 5223.

I know this is a development install, so maybe that's the problem?

Thanks!

Revision history for this message
Massimiliano Mirra (bard-hyperstruct) said : 		#4

KoolIM probably uses StartTLS over 5222 (which SamePlace is going to support only from 0.10).

For Google Talk, you should be able to connect using 5223+SSL and 443+SSL. (I am connected right now using 443+SSL, but I can see the 5223 port being open.) You might want to try the 5223+SSL combination with another client, too--just to check that it's not blocked by a firewall like the 443.

Revision history for this message
Mike (ubergruvn) said : 		#5

Alas, no combination I can find is working. Too bad - sameplace looks like an infinitely better interface.

Thanks anyways.

Revision history for this message
Massimiliano Mirra (bard-hyperstruct) said : 		#6

I take that means that even port 5223 is blocked. Pity! Maybe give it another try when 0.10 is out--StartTLS+5222 will work on that.