aaPanel Deployment
This guide shows how to run the Epusdt service itself with aaPanel.
No manual .env is required for first boot. Start the binary, then finish setup in the browser wizard.
Basic flow
- Create a site in aaPanel for your payment domain
- Upload the Epusdt release package or binary
- Reverse proxy the site to
http://127.0.0.1:8000 - Fix program permissions before starting it with Supervisor
- Use aaPanel Supervisor with the correct working directory and command
- Open the bound domain to finish the install wizard
Recommended permissions before Supervisor
If aaPanel Supervisor runs the process as www, make sure the deployment directory is executable and owned correctly first:
bash
cd /www/wwwroot/epusdt
chmod +x epusdt
chown -R www:www /www/wwwroot/epusdtRecommended Supervisor settings
- Working directory:
/www/wwwroot/epusdt - Command:
./epusdt http start
Using only epusdt http start can fail when the working directory is wrong, because the config file path is resolved relative to the current directory.
Finish the install wizard
- Recommended: open the bound domain directly, such as
https://pay.example.com - Only if you are connecting to the program port directly, open
http://server-ip:8000
Verification
Use your deployed domain as the API base URL, for example:
text
https://pay.example.comRecommended order route:
text
POST /payments/gmpay/v1/order/create-transactionNotes
- Admin panel settings now own merchant credentials and EPay defaults
- Do not follow old docs that still mention
/payments/epusdt/v1/order/create-transaction
