-
Notifications
You must be signed in to change notification settings - Fork 102
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
could not connect service from the host #34
Comments
You must have made a mistake. |
Thanks for the reply |
Can you run I recommend setting Also, it seems that you commented with some additional information (I can see it in my email) but somehow it disappear on GitHub. |
sudo docker inspect -f '{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}' warp
172.26.0.37 It seems the ip is got the correct ip addr. and now the docker-compose is as below: warp:
image: caomingjun/warp:latest
container_name: warp
# restart: always
ports:
- "8338:8338"
environment:
- WARP_SLEEP=2
- GOST_ARGS=-L=ss+ohttp://aes-256-gcm:passwd@:8338
- BETA_FIX_HOST_CONNECTIVITY=1
cap_add:
- NET_ADMIN
sysctls:
- net.ipv6.conf.all.disable_ipv6=0
- net.ipv4.conf.all.src_valid_mark=1
- net.ipv4.ip_forward=1
volumes:
- /srv/docker/data/warp/:/var/lib/cloudflare-warp
networks:
ss-backend:
ipv4_address: 172.26.0.37 not got lucy, |
For the other gone replies. after that I drawback to the original gost service, and cannot connect again. I thought the only once 'successful connection' is caused the warp service not established on the time. if the warp not connected from time to time, the shadowsocks protocol could connect right. |
Can you try to see if the default SOCKS5 proxy also has this issue? It’s best to run |
Yes, the socks5 works fine. with the socks service works fine on host: fii@tc:~$ curl --socks5-hostname 127.0.0.1:1080 https://cloudflare.com/cdn-cgi/trace
fl=466f140
h=cloudflare.com
ip=104.28.217.42
ts=1727782106.888
visit_scheme=https
uag=curl/7.88.1
colo=SJC
sliver=none
http=http/2
loc=US
tls=TLSv1.3
sni=plaintext
warp=on
gateway=off
rbi=off
kex=X25519 while the shadowsocks not work |
I also tried proxy mode before warp-cli set-proxy-port 40000
# Set the mode to proxy
warp-cli --accept-tos mode proxy and |
This is very strange, I cannot understand. The SOCKS5 works indicates that the container can be accessed from the host machine, and the forwarding of SOCKS5 through shadowsocks suggests that there is no issue with GOST's shadowsocks functionality or your configuration. I can't think of what the problem could be. |
yes, that's very strange, I tried two days and try to get help here. any ideas appreciate. |
I've notice the issue #23 is closed.
However I still could not connect the gost exposed service from the host even with
BETA_FIX_HOST_CONNECTIVITY=1
the container ip is 172.35.0.37
and the output of the dump is
I think
172.35.0.37
is in the range of172.16.0.0/12
.and I try to expose a shadowsocks service by gost:
ss+ohttp://aes-256-gcm:password@172.35.0.37:9876
any idea? thanks
The text was updated successfully, but these errors were encountered: