ssh + tinyproxy: poor performance

Posted by Paul on Server Fault See other posts from Server Fault or by Paul
Published on 2011-09-06T14:56:44Z Indexed on 2012/06/02 22:43 UTC
Read the original article Hit count: 2113

Filed under:
|
|
|

I am currently in China and I would like to still visit some blocked websites (facebook, youtube). I have VPS in the USA and I have installed tinyproxy on it. I log in on my VPS with SSH port-forwarding and I have configured my browser appropriately. Everything works more or less: I can surf to those websites but everything is inusually slow and sometimes data transfer stops abruptly. This probably has to do with the fact that I see some errors in my shell on the VPS like :

channel 6: open failed: connect failed:

Also in the log-file of tinyproxy I see some bad things:

ERROR     Sep 06 14:52:14 [28150]: getpeer_information: getpeername() error: Transport endpoint is not connected
ERROR     Sep 06 14:52:15 [28153]: writebuff: write() error "Connection reset by peer" on file descriptor 7
ERROR     Sep 06 14:52:15 [28168]: readbuff: recv() error "Connection reset by peer" on file descriptor 7
ERROR     Sep 06 14:52:15 [28151]: readbuff: recv() error "Connection reset by peer" on file descriptor 7
ERROR     Sep 06 14:52:15 [28143]: readbuff: recv() error "Connection reset by peer" on file descriptor 7
ERROR     Sep 06 14:52:17 [28147]: writebuff: write() error "Connection reset by peer" on file descriptor 7
ERROR     Sep 06 14:52:23 [28137]: writebuff: write() error "Connection reset by peer" on file descriptor 7
ERROR     Sep 06 14:52:26 [28168]: getpeer_information: getpeername() error: Transport endpoint is not connected
ERROR     Sep 06 14:52:27 [28186]: read_request_line: Client (file descriptor: 7) closed socket before read.
ERROR     Sep 06 14:52:31 [28160]: getpeer_information: getpeername() error: Transport endpoint is not connected

© Server Fault or respective owner

Related posts about ssh

Related posts about proxy