Skip to main content
Version: v25.07.31

Socks proxy Troubleshooting

This document describes SocksProxy troubleshooting steps, focusing on configuration verification and checking the connection status from the CE and PE sides. In this case, users cannot connect to the SocksProxy. The causes could include a slow connection in terms of speed, failure to access given resources, or complete failure of connectivity. The whole troubleshooting process involves checking the Shadowsocks configuration both at the CE and PE, as well as checking for the status of network connections and also searching for error logs.

Troubleshooting Steps​

Cloud Configuration Verification​

This section details how to check the configurations made in the cloud. The commands below can be used to verify the cloud configuration.

Verify CE Configuration​

Log into the CE and inspect the Shadowsocks configuration file. The location may be different but common locations include /etc/config/shadowsocks-libev. Run the following command.

sudo cat /etc/config/shadowsocks-libev
Example Response​
 config server 'vtun56_3_server'
    option disabled '0'
    option server '103.78.41.23'
    option server_port '30021'
    option password 'IEUGVQl5a8wiGiBYujkDvtun56_3'
    option method 'chacha20'

This command shows the configuration file contents. Carefully check the settings, especially the server address, port, and password.

Verify PE Configuration​

In the PE, log in and check the Shadowsocks configuration file. A common phrase for this is /etc/shadowsocks-libev/vtun56_3.json. The command to run the configuration in a pretty print format is:

cat /etc/shadowsocks-libev/vtun56_3.json | json_pp
Example Response​
{
   "password" : "IEUGVQl5a8wiGiBYujkDvtun56_3",
   "reuse_port" : true,
   "method" : "chacha20",
   "local_port" : "40021",
   "server_port" : "30021",
   "timeout" : 60,
   "fast_open" : true,
   "server" : "0.0.0.0"
}

json_pp formats the JSON output for better readability. Check also that the port and password are set correctly in the settings.

Check for Configuration Errors​

Review both configuration files for syntax errors, typos, or wrong characters. Even a tiny error can keep shadowsocks from working correctly. For the PE's JSON configuration, validate the file with a JSON validator, either online or command line tools. Invalid JSON will prevent Shadowsocks from starting.

Q:1 What is a common example of a configuration file found in CE?

Q:2 How do I verify Shadowsocks configuration on PE (Provider Edge)?