alectrocute / wg-api Goto Github PK

Hello,

Work fine.. But Do not remove users via http. Always return error 404 when you try to remove user vía HTTP but trougth wg.sh script the user is suscessfully removed.

Currently, you only have options for Cloudflare, Google DNS, and OpenDNS, but with a full tunnel, which is the default setup, and an external DNS, the VPN end-user is leaking traffic every time a DNS request/lookup comes from a client device.

I propose to add a fourth option to install/configure unbound and iptables so that the wireguard server will act as the VPN DNS.

This guide has an excellent example of a similar setup.

Hello!

I have found a small bug. I am able to create a peer, but I can't remove them afterwards. This is what I get;

root@server:~# curl http://x.x.x.x:3000/peer/create/removetest
{
  "code": 200,
  "profile": {
    "Interface": {
      "Address": "10.9.0.5/24",
      "PrivateKey": "<hidden>",
      "DNS": "1.1.1.1, 1.0.0.1"
    },
    "Peer": {
      "PublicKey": "07G4gg98uYm0LNO+Xwon01zVnzWwFRFGTjxMJgP88AI=",
      "AllowedIPs": "0.0.0.0/0, ::/0",
      "Endpoint": "x.x.x.x:2000",
      "PersistentKeepalive": "25"
    },
    "qr": "/peer/qr/removetest"
  }
}root@server:~#
root@server:~# curl http://x.x.x.x:3000/peer/remove/removetest
{"message":"Route GET:/peer/remove/removetest not found","error":"Not Found","statusCode":404}root@server:~#

Further, very enthousiastic about this API, comes in useful!

Hi
Is this script WireGuad Interface/Peer Configuration persistan on service restart ?
and another question is if i have thousand users and i make config for each of them on the fly may this cause interruption of other users ? (since creating and inserting each peer should restart the service to make user be able to connect successfully with that newly created config)

The QR code given in the first installation works just fine. But, let's use (create or remove) functions as get after making the necessary config settings. When we reboot after use, none of them work anymore. Because after reboot "/etc/wireguard/wg0.conf" file gets corrupted. More precisely, it gets corrupted after create and remove, but is noticed after reboot. "/wg-api/scripts/data/wg.def" does not get the necessary information from here and update itself, PublicKey and AllowedIPs remain empty. In addition, when we use the remove process, the user can still continue to use it even though they delete it from the profiles folder. "wg set $interface peer $key remove" instantly destroys this command when we run it manually in the terminal. When we use a command with "wg.sh" it breaks. It also crashes after reboot when we do create and remove with GET or use "wg.sh -a xxxx & wg.sh -d xxxx" directly. Corrupts the "wg.conf" file. Can you tell me where exactly is the problem?

Hello! First of all thanks for this software!

But i have a small problem.
When i generate new user:

:3000/peer/create/newclient

the response is empty public key and qr code not correct reading by phone device without public key.

{
  "code": 200,
  "profile": {
    "Interface": {
      "Address": "10.9.0.2/24",
      "PrivateKey": "somekey",
      "DNS": "1.1.1.1, 1.0.0.1"
    },
    "Peer": {
      "PublicKey": "",
      "AllowedIPs": "0.0.0.0/0, ::/0",
      "Endpoint": "myip:2000",
      "PersistentKeepalive": "25"
    },
    "qr": "/peer/qr/newclient"
  }
}

as you can see, the PublicKey is empty.

wg.sh do not create the saved.tmp file

Exist any way to get peer names using api given data?

"oAe6pZFvW5qyn3zL1ANyj+px4jzCoudydJSR2lsJ+mw=": {
"endpoint": "152.206.192.229:7192",
"latestHandshake": "Oct 1, 2021 16:18:52 UTC",
"transferRx": "4.82 MB",
"transferTx": "24.626 MB",
"allowedIps": [
"10.9.0.5/32"
]
},
That is an example, how can I know the client name that is using this

im getting this error on CentOS 7. please help me out. thanks.

create peer add as endpoint last user's login ip instead of server ip , this makes the config unusable as i'd have to correct endpoint manually, otherwise it' ok