* start of refactoring * Wireguard Init * Update * Config * Ssh * ShadowSockets * Update Dockerfile * Pull Request Actions * Removed Dropbear And ssh Update * Push * Push * Add * to lower case files * Rename Dirs * Push * vs code Dev Conatiner * Update devcontainer
Server API
The server's backend is all controlled by a RESTful API, and not directly accessed by the shell, only if it is necessary to do some operation by terminal. Here is a summary of the API routes.
Wireguard
We support Wireguard as a VPN protocol, but it requires Docker to run in --privileged mode, as it will create a network interface to Wireguard.
Routes to Wireguard
-
Add Peer:
/Wireguard/Add?Token={Token}&User={Unique Peer Name}GET -
Remove Peer:
/Wireguard/Remove?Token={Token}&User={Unique Peer Name}GET -
Get Configs:
/Wireguard/Config?Token={Token}GET -
Get Client Config:
/Wireguard/UserConfig?Token={Token}GET- Get Client in another file type:
/Wireguard/UserConfig/:{File Type}?Token={Token}GET- Files Avaibles:
default,wireguard,json,qrcodeandyaml
- Files Avaibles:
- Get Client in another file type:
Dropbear and OpenSSH
This image also has an OpenSSH Server and a Dropbear Server, and just for tunneling over SSH.
Routes to SSH
-
Get services Status:
/sshGET -
Add user:
/ssh/Add?Token={Token}&Username={Unique User}&Password{Passworld}&Days{Days to remove user}&Connections={Number of connections allowed}GET -
Remove user:
/ssh/Remove?Token={Token}&Username={Unique User}GET -
List users:
/ssh/List?Token={Token}GET -
Ssh Monitor:
/ssh/Monitor?Token={Token}or/ssh/ssh_monitor?Token={Token}GET