skoret / wireguard-telegram-bot Goto Github PK

ubuntu 22.04
after /newkey:
/root/wireguard-telegram-bot/internal/telegram/telegram.go:83 +0xe5
exit status 2

there are three way to send client config to user in our system:

• .conf file
• plain text
• qr code

there are two way to create new client config in our system:

• with new generated key pair by ourselves
• with placeholder for user's private key

Client file format:
[Interface]
Address =
PrivateKey =
DNS =

[Peer]
PublicKey =
AllowedIPs = 0.0.0.0/0 ?? todo: investigate
Endpoint =

tg-bot should update server's config on each new client
investigate: should we restart wg-server on every such updates?

Use wgctrl
Examples: wg-gen-web

commands should be registered on bot startup
mvp commands:

• new client configuration [for 'public' wg vpn]
  • generate new key pair for me | result: user receives new conf file with new client's private key
  • for provided public key | result: user receives new conf file with placeholder for user's private key
  • see #7 and #8

next evolution steps of project:

• setup and run new personal wg-instance
  • for some donations?
• teardown personal wg-instance
• list personal instances
• new client configuration [for specified personal instance]
  • generate new key pair
  • for provided public key
• list client configurations
• remove registered client configuration
• inline queries support (?)