qdm12 / gluetun

VPN client in a thin Docker container for multiple VPN providers, written in Go, and using OpenVPN or Wireguard, DNS over TLS, with a few proxy servers built-in.
https://hub.docker.com/r/qmcgaw/gluetun
MIT License
7.42k stars 350 forks source link

Feature request: cloudflare warp #1738

Open arjung24 opened 1 year ago

arjung24 commented 1 year ago

What's the feature 🧐

It would be great if cloudflare's warp is included in gluetun vpn list.

Extra information and references

https://developers.cloudflare.com/cloudflare-one/connections/connect-devices/warp/deployment/vpn/#:~:text=The%20Cloudflare%20WARP%20client%20is,to%20Gateway%20for%20policy%20enforcement.

afa5088 commented 1 year ago

请问我安装 WARP 的时候老是显示 “您尝试使用的功能位于不可用的网络资源上” 这个怎么解决呢,笔记本电脑,之前安装过一次,卸载过一次,再次安装就出现这个问题,很苦恼... 官网下载安装的时候老是弹出这个

qdm12 commented 1 year ago

@arjung24 I am not certain I understand, is Warp its own VPN protocol? Or does it support Wireguard or Openvpn clients?

From the looks of it, it's its own protocol, with a closed source client (prove me wrong maybe?), and that's a no-go unfortunately, since the end goal is to have gluetun cross platform and as a single binary (and we don't want to manage closed source applications, already openvpn is a pain to manage 😄)

Regarding @afa5088 comment:

From Google Translate:

I will install WARP when it shows “The function you are trying to use is located on a network resource that is not available"

No idea how this is remotely relevant here, I'll hide the comment

leo15dev commented 1 year ago

In fact, Warp uses the WireGuard protocol, which can be found more information at https://github.com/ViRb3/wgcf

I've been running Warp WireGuard through gluetun for about half a year or so, and it's pretty stable, except for when Cloudflare maintains the Server, the endpoints are not available due to reroute.

arjung24 commented 1 year ago

In fact, Warp uses the WireGuard protocol, which can be found more information at https://github.com/ViRb3/wgcf

I've been running Warp WireGuard through gluetun for about half a year or so, and it's pretty stable, except for when Cloudflare maintains the Server, the endpoints are not available due to reroute.

@qdm12 brother please check this out. And if possible make a guideline for warp to work through gluetun 🤗🤗

ridgewell commented 1 year ago

If you're looking for this functionality, this has already been implemented by: https://github.com/Mon-ius/Docker-Warp-Socks

Sn00zEZA commented 8 months ago

In fact, Warp uses the WireGuard protocol, which can be found more information at https://github.com/ViRb3/wgcf

I've been running Warp WireGuard through gluetun for about half a year or so, and it's pretty stable, except for when Cloudflare maintains the Server, the endpoints are not available due to reroute.

Mind sharing your docker config or a short description on how to get this working?

chientrm commented 7 months ago

In fact, Warp uses the WireGuard protocol, which can be found more information at https://github.com/ViRb3/wgcf

I've been running Warp WireGuard through gluetun for about half a year or so, and it's pretty stable, except for when Cloudflare maintains the Server, the endpoints are not available due to reroute.

Ohm, can you share it? 🥹🥹🥹

leo15dev commented 7 months ago

@Sn00zEZA @chientrm Follow this instruction to get the wgcf-profile.conf

and in gluetun docker-compose.yaml add the follow information

environment:
  - VPN_SERVICE_PROVIDER=custom
  - VPN_TYPE=wireguard
  - VPN_ENDPOINT_IP=
  - VPN_ENDPOINT_PORT=
  - WIREGUARD_PUBLIC_KEY=
  - WIREGUARD_PRIVATE_KEY=
  - WIREGUARD_ADDRESSES=

which VPN_ENDPOINT_IP, VPN_ENDPOINT_PORT, WIREGUARD_PUBLIC_KEY, WIREGUARD_PRIVATE_KEY, WIREGUARD_ADDRESSES was obtained in the wgcf-profile.conf.

Sn00zEZA commented 7 months ago

@Sn00zEZA @chientrm Follow this instruction to get the wgcf-profile.conf

and in gluetun docker-compose.yaml add the follow information

environment:
  - VPN_SERVICE_PROVIDER=custom
  - VPN_TYPE=wireguard
  - VPN_ENDPOINT_IP=
  - VPN_ENDPOINT_PORT=
  - WIREGUARD_PUBLIC_KEY=
  - WIREGUARD_PRIVATE_KEY=
  - WIREGUARD_ADDRESSES=

which VPN_ENDPOINT_IP, VPN_ENDPOINT_PORT, WIREGUARD_PUBLIC_KEY, WIREGUARD_PRIVATE_KEY, WIREGUARD_ADDRESSES was obtained in the wgcf-profile.conf.

Thanks for the info, i have tried this many times over and lots of other variables also and didn't get it to work at the time i requested your config. Kept getting "write: operation not permitted". I gave up.. Decided to test it right now and its working!!.. Gotta be kidding me! Same yml i saved then now just works. Oh well, thanks anyway.

tubbadu commented 7 months ago

@Sn00zEZA @chientrm Follow this instruction to get the wgcf-profile.conf and in gluetun docker-compose.yaml add the follow information

environment:
  - VPN_SERVICE_PROVIDER=custom
  - VPN_TYPE=wireguard
  - VPN_ENDPOINT_IP=
  - VPN_ENDPOINT_PORT=
  - WIREGUARD_PUBLIC_KEY=
  - WIREGUARD_PRIVATE_KEY=
  - WIREGUARD_ADDRESSES=

which VPN_ENDPOINT_IP, VPN_ENDPOINT_PORT, WIREGUARD_PUBLIC_KEY, WIREGUARD_PRIVATE_KEY, WIREGUARD_ADDRESSES was obtained in the wgcf-profile.conf.

Thanks for the info, i have tried this many times over and lots of other variables also and didn't get it to work at the time i requested your config. Kept getting "write: operation not permitted". I gave up.. Decided to test it right now and its working!!.. Gotta be kidding me! Same yml i saved then now just works. Oh well, thanks anyway.

This is really strange, I keep getting the same write: operation not permitted error as yesterday