Using Proxy, cannot connect (even with 443 on)

Hi Wally,

it would help to report the information shown by selecting "Report a Bug" from the "Help" menu (which includes platform, OS, etc).

Also, I understand you're trying to use a @sameplace.cc account, right?

Yes, im talking about the @sameplace.cc account

(bug report)
System information:

 SamePlace: 0.9.1.2008021910
 xmpp4moz: 0.6.1.2008021112
 OS: WINNT
 Application: Mozilla Firefox 2.0.0.12 (2008020121)

Latest relevant errors from console:

 [JavaScript Error: "[Exception... "JavaScript component threw a JavaScript object" nsresult: "0x8057001c (NS_ERROR_XPC_JS_THREW_JS_OBJECT)" location: "JS frame :: chrome://xmpp4moz/content/service/connector-xmpp_tcp.js :: write :: line 313" data: no]" {file: "chrome://xmpp4moz/content/service/connector-xmpp_tcp.js" line: 313}]

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

(Re-setting to open since this is a valid question, we just haven't found the culprit yet.)

I am open to run a debug version of it if you need. I am really interested in solving this problem since i want to be able to use sameplace from my workplace.

Thanks Wally :-) I'l add some more debug output to the XMPP connector
(it was rewritten in the development branch) before bothering you,
since right now it doesn't show the conversation between the client
and the proxy, only its outcome.

Err...this might not be a good act since ive put up my question on the mailing list too! apologies for kinda spamming the mailing list..
i got a problem with the proxy connection. At my institution, we have a proxy server in between that is used to connect to the internet. We dont have direct lines there.
e.g.: to gain access, we need to set up the proxies as 172.16.176.1:8080 where 8080 is the port on which the proxy server listens

now if i have my browser settings nicely configured and im able to open all the webpages, then probably my tiny firefox add-on shudnt have a problem in connection with wit the talk.google.com server! but here we got a problem....the connection procedure lasts indefinitely and ultimately u wont get it connected!
Is there a solution for this?
maybe some modifications need to be made either in the xmpp4moz sources or at the proxy server thats listening on port 8080!

Thanks
Nikhil

Hi Nikhil,

reasons why proxy connection could go wrong:

- it doesn't supprot SSL CONNECT;
- it supports SSL CONNECT but only to specific hosts;
- it requires authentication.

There may be more I'm not aware of but checking those would be a good start.

Hi Bard
Thanks for the quick reply!
well, as i said, v guys can access our gmail accounts through gtalk and equivalent clients!
even the browser works just fine.....regarding authentication, there's none...in our case, v r using the IP series that is unauthenticated....
what can be a possible solution for this?
I'l be checking upon the proxy server if it allows SSL connects or not!can u tell me if there can be a provision to listen through port 443 on the server?
or even that xmpp4moz can connect to the server from the same port which it listens on...i.e. port 8080, i guess 8080 and 443 can be equivalently used for secure connections..
wts ur say on this?

> what can be a possible solution for this?

No idea, I'd have to connect through your proxy to learn more about this. :-)

> I'l be checking upon the proxy server if it allows SSL connects or not!can u tell me if there can be a provision to listen through port 443 on the server?

Ehm?

> or even that xmpp4moz can connect to the server from the same port which it listens on...i.e. port 8080, i guess 8080 and 443 can be equivalently used for secure connections..

Proxy port and destination server port are different and unrelated things.

I suggest you enable chrome errors in the console (set
javascript.options.showInConsole -> true in about:config) and check
for any errors.

regarding the javascript options, i have already enabled the debugging preferences!(i'm using Extension Developer)

I might sound like a newbie...which I am to a certain extent.....can u please explain what exactly happens when we append talk.google.com with the port number 443?

as in case of the proxy port...all i cud understand that by specifying the socket 172.16.176.16:8080 , we intend to connect to a server with IP address 172.16.176.1 and to a port with number 8080 on that server! If the proxy server, which happens to be a machine in one of our labs, is not allowing me to connect via SSL, then probably there has to be a way in which it shall allow the same! there have been quite some people complaining about not able to connect Sameplace from their workplace just coz of the proxy thing...cudnt find any of em who gave a positive feedback about being able to connect thru a proxy... maybe their solution lies in my problem?

Erm... any news about this problem? i still have the same behaviour, and still open for debugging the client-server chat if you want.

Regards!

> Erm... any news about this problem? i still have the same behaviour, and
> still open for debugging the client-server chat if you want.

Actually, yes, now the development version logs the proxy response
too, and you can save the log. (Sorry, I committed this days ago, but
I was in the middle of relocating and forgot to update this question.)
 It's still possible that the point of failure is not in proxy
negotiation, but at least this should give us a hint.

You can find the development version on http://sameplace.cc/download.
After trying to log in, go to the help menu and select "Save XMPP
log", then send it to me at hyperstruct [at] gmail.com.

Thank you for staying in the loop!