Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


VPN/socks proxy timeouts, how to find cause?
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

VPN/socks proxy timeouts, how to find cause?

postcdpostcd Member
edited January 2017 in Help

Hello,

i bought a VPS with Linux CentOS 6 and installed shadowsocks proxy server and OpenVPN server so the VPS serve as a proxy for my Windows computer. Now it seems that my web browser or other apps have quite frequent problems (timeouts)

When i switch to proxy/vpn on other VPS (other GEO location), connection works. The bad VPS is not offline, the proxified pages loads, sometime timeout and slow load.

I tried running "mtr 8.8.8.8" at the bad VPS, but no loss

On "bad" VPS is no firewall or blocking SW to my knowledge, only default iptables:
http://pastebin.com/5qDCJf9j

cat /etc/openvpn/server.con*

http://pastebin.com/M9s4RUmM

shadow*socks server config file:

http://pastebin.com/j4emiVac

OpenVPN client based log file in current verbosity does not show anything useful and in settings i do not see ability to change verbosity.

Please can you advice which commands to run and what to do to discover cause of these problems?

My client computer is running Windows 10. Thank you

Comments

  • CiefdxCiefdx Member
    edited January 2017

    If you are the big brother of China, you can add my QQ 97981616. The answer is a hash symbol (#).
    I can not understand what you mean, in general, has nothing to do with the firewall, only with your computer on the configuration.

  • On shadowsocks config, your timeout value is too low. Change to something around 200.

  • postcdpostcd Member
    edited January 2017

    @miau said:
    On shadowsocks config, your timeout value is too low. Change to something around 200.

    done, but this is not cause of the problem, there was not connection issues before. issue started recently.

Sign In or Register to comment.