Skip to content

Better error messages and debugging information.... #11

Open
@Elite

Description

@Elite

I successfully used TrevorProxy on one of my servers, but on the second server with same provider having the same networking setup but using Ubuntu instead of Debian I am not able to connect and get this error:

trevorproxy subnet -s XXX:YYY::/64 -i enp129s0f0
[DEBUG] ip route add local XXX:YYY::/64 dev enp129s0f0
[INFO] Listening on socks5://127.0.0.1:1080

But:

curl -v --proxy socks5://127.0.0.1:1080 -6 api64.ipify.org
* Closing connection 0
curl: (7) Couldn't connect to server

From this it looks like the proxy server is not running as no connection request is logged by the server, I have checked that firewall and it seems the proxy is listening correctly.

lsof -i :1080
COMMAND      PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
trevorpro 159845 root    4u  IPv4 296659      0t0  TCP localhost:socks (LISTEN)

So, the question is how to get more information where is this failing?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions