Neomanbeta

It seems to be working right now. TBH I have no idea how.....Here is the test log. It took me days to setup my debian server with ipv6 and create...

I don't know where does it go wrong. It can pass the test inside the docker terminal; / # curl -f https://ip.sb/cdn-cgi/trace fl=466f115 h=ip.sb ip=104.28.213.199 ts=1719821100.357 visit_scheme=https uag=curl/8.5.0 colo=SJC sliver=none...

I think I've located the problem. Since I can only replace endpoint with an ipv6 address & port, I've created a docker bridge network with ipv6 support. By default this...

Yes, I go straight to the folder where wgcf-profile.conf is located, then modify the endpoint ip & port and restart the docker. Reason why I do not use ipv4 endpoint...

I'm not sure what you mean, but if you mean even with the current issue at hand, can I use terminal to login the docker and execute curl? Then the...

No, the problem is still there. I think I've made you confused, so I will clarify the problem. After modifying the wgcf-profile.conf, the docker can connect to the WARP service....

1: ipv6, I cannot use ipv4 endpoint ips, they are all blocked. 2: OK, good to know 3: with modified ipv6 endpoint ip&port

Say the ipv6 ip&port I want to change to is 2606:4700:d0::3ed0:74ce:7f61:70be:3476 the command would be: sed -i 's|engage.cloudflareclient.com:2408|2606:4700:d0::3ed0:74ce:7f61:70be:3476|' /opt/wgcf-profile.conf I'm not sure this is 100% correct, it seems alright. But...

I hope i'm getting this right. Yes, the test curl -x "socks5h://127.0.0.1:9091" -fsSL "https://www.cloudflare.com/cdn-cgi/trace" is working fine. Normally, I can access this socks from other devices by using host machine's...

OK, i see, thanks for the help.