Connection problem

[jts]

The other day I was fooling around with ways to configure my internet connection and accidentally set the whole system (Ubuntu) to go through Privoxy for a few seconds. I reverted it a moment later, and everything was fine... except for Cgoban, which gives the following error from Java when I try to connect:

Security Exception
Name: CGOban 3

java.net.MalformedURLException : unknown protocol : socket

--------Details:

java.net.MalformedURLException: unknown protocol: socket
at java.net.URL.<init>(URL.java:574)
at java.net.URL.<init>(URL.java:464)
at java.net.URL.<init>(URL.java:413)
at java.net.URI.toURL(URI.java:1081)
at com.sun.deploy.net.proxy.DeployProxySelector.connectFailed(DeployProxySelector.java:208)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:384)
at java.net.Socket.connect(Socket.java:529)
at java.net.Socket.connect(Socket.java:478)
at java.net.Socket.<init>(Socket.java:375)
at java.net.Socket.<init>(Socket.java:189)
at cZ.a(cgoban:72)
at cP.a(cgoban:66)
at cQ.run(cgoban:215)
at java.lang.Thread.run(Thread.java:662)

--------Leading to this error from CGoban:
Error "Can't connect to SOCKS proxy:Connection refused" while connection to machine "goserver.gokgs.com"

Now, I can't figure out where the heck this is being stored. I reinstalled both Sun Java and the shared Java components. I also downloaded a fresh jnlp, although I don't think that could possibly matter. Any other thoughts on what I should try?

[Kirby]

Is the port correct? Does the applet work?

On a side note, this type of connection problem is so much more boring than connection problems on the go board.

[oren]

On a side note, this type of connection problem is so much more boring than connection problems on the go board.

I don't know, I've had some very interesting connection problems of this nature for work before.

[jts]

The port is 2379... I'm not able to find documentation for what it's supposed to be,

[jts]

and as for applets, I was never able to get the applet to work on my ubuntu laptop.

[Kirby]

2379 is the correct port. Maybe you're blocking that port.

I can try to see what you can do when I get home, but in the meantime, you might try using nmap. I think that would work to see if something is being blocked.

Try something like:

Code: Select all

nmap -p 2379 goserver.gokgs.com

Though, again, I haven't tested if this is the precise syntax, so I don't know if this will work even if you're not blocking the port. I can try to get you more information when I get home today.

[Kirby]

And by the way, if it does turn out that that port is being blocked, I know that http tunneling works to get you connected. I've done this before at a library where the port was blocked on the wifi... Though, I wonder if there's still a remnant problem from Privoxy.

When you say you "reverted it", what do you mean by this?

[Kirby]

Another thing to try:

Code: Select all

semanage port -a -t tor_port_t -P tcp 2379

This is just something I found online. I have never used "semanage" before, so again, I'm not sure if this will work.

[Kirby]

This discussion is getting me into the mood to start using linux, again.

[wms]

No clue. Something broke, but what?

[jts]

I wanted Chrome to use privoxy, so I went to preferences>under the hood> change proxy settings. Originally it was set to "direct network connection"; I set it to "manual proxy", gave it the port for privoxy, and clicked "apply". When the success dialogue came up to tell me that I had changed the settings for my entire system, I changed it back to "direct network connection."

(I realize now that the "change proxy setting" button in chrome calls up the system proxy settings interface. Which is pretty misleading.)

[Kirby]

Maybe try checking your network proxy settings by a different means...?

Does this work: http://www.techmetica.com/howto/setup-a ... in-ubuntu/?

[jts]

So what I was saying is: you can't change Chrome's proxy setting's specifically, Chrome just redirects you the system-wide settings.

I don't think it's Java's fault. I selected Vuze just to check, and Vuze didn't seem to have any trouble connecting to the internet.

[Kirby]

So what I was saying is: you can't change Chrome's proxy setting's specifically, Chrome just redirects you the system-wide settings.

I don't think it's Java's fault. I selected Vuze just to check, and Vuze didn't seem to have any trouble connecting to the internet.

Interesting. The thing that strikes me is that, if you could connect to kgs via cgoban prior to changing proxy settings, and now you cannot connect to kgs, it appears that your computer is in a different state than it was before making the change to the settings. That's kind of why it seems natural to try to find a means to ensure that you have undone whatever you did before.

[jts]

I agree! I just can't think what those means would be.