Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RedirAddr behaves quite odd when BindAddr is changed to "non-default" ports ... #235

Open
Cebeerre opened this issue Oct 18, 2023 · 0 comments

Comments

@Cebeerre
Copy link

Hi !

First of all let me thank @cbeuw and the rest of contributors for this nice piece of sofware ... really awesome !

I'm happily running a setup where traffic goes through Caddy2 running on Docker to be proxied to a Cloak instance running on top of an OpenWRT router where my Wireguard instances live. This setup is working fine without isues using the CDN Transport.

The thing is that ck-server is running on port 1081 on the OpenWRT and even though the plugable thing works perfectly, if I try to connect with a browser to the caddy2 vhost that proxies to the 1081 cloack instance, ck-server actually tries to redirect to the RedirAddr but forcing/using the 1081 port as per the logs:

Wed Oct 18 15:37:36 2023 daemon.err ck-server[13685]: time="2023-10-18T13:37:36Z" level=error msg="Making connection to redirection server: dial tcp 142.250.200.99:1081: connect: connection timed out"

Is this something really expected ?

My server.json looks like this:

{
    "ProxyBook": {
        "wireguard": [
            "udp",
            "127.0.0.1:3478"
        ]
    },
    "BindAddr": [
    	":1081"
    ],
    "BypassUID": [
        "xxxxxxx"
    ],
    "RedirAddr": "google.es",
    "PrivateKey": "xxxxxxx"
}

Many thanks !!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant