- BTCPay Server integration - TeleBot Telegram bot - Review system - Admin area - Docker deployment configuration 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
1.5 KiB
1.5 KiB
Nginx Proxy Manager Configuration
Access Information
- Admin Panel: http://thebankofdebbie.giize.com:81
- Default Credentials:
- Email: admin@example.com
- Password: changeme
- CHANGE THESE IMMEDIATELY!
Create Proxy Host for BTCPay
- Login to NPM admin panel
- Go to "Proxy Hosts" → "Add Proxy Host"
- Configure as follows:
Details Tab:
- Domain Names: thebankofdebbie.giize.com
- Scheme: http
- Forward Hostname / IP: 172.20.0.4 (or use container name: generated_btcpayserver_1)
- Forward Port: 49392
- Cache Assets: OFF (for BTCPay)
- Block Common Exploits: ON
- Websockets Support: ON (important for BTCPay)
SSL Tab:
- SSL Certificate: Request a new SSL Certificate
- Force SSL: ON
- HTTP/2 Support: ON
- HSTS Enabled: ON
- Email: admin@thebankofdebbie.giize.com
- Agree to Terms: Check
Advanced Tab (optional):
# Add if needed for BTCPay
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
Current Services Status:
- BTCPay: Running on port 8080 (internal: 49392)
- NPM: Running on ports 80, 443, 81
- Portainer: Running on port 9443
Troubleshooting:
If BTCPay doesn't respond through NPM:
- Check Docker network connectivity
- Verify BTCPay is accessible locally:
curl http://localhost:8080 - Check NPM logs:
docker logs nginx-proxy-manager - Ensure websockets are enabled in proxy host