SilverLABS/littleshop
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial commit of LittleShop project (excluding large archives)

Browse Source 
- 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>
This commit is contained in:
SysAdmin
2025-09-17 15:07:38 +01:00
parent bcca00ab39
commit e1b377a042
140 changed files with 32166 additions and 21089 deletions
Download Patch File Download Diff File Expand all files Collapse all files

132
Hostinger/BITCOIN_RESTORED_STATUS.md Normal file
View File

@@ -0,0 +1,132 @@
# Bitcoin Successfully Restored! ✅
**Date**: September 16, 2025
## Current Status
### ✅ Bitcoin Core is Running
- **Container**: btcpayserver_bitcoind
- **Status**: Active and syncing
- **Current Block**: ~253,371 (as of 18:32 UTC)
- **Target Height**: ~862,000 (mainnet current)
- **Sync Progress**: ~29% (will continue in background)
### ✅ Pruning Active
```
Prune configured to target 10000 MiB on disk for block and undo files.
```
- Maximum disk usage: 10GB
- Automatic old block cleanup
- Sufficient for payment processing
### ✅ BTCPay Integration
- BTCPay Server connected to Bitcoin node
- NBXplorer indexing transactions
- Ready to accept Bitcoin payments once synced
## Service Architecture
```
NPM (80/443) → BTCPay (8080) → NBXplorer → Bitcoin Core
↓
PostgreSQL
```
## Container Status
| Service | Container | Status |
|---------|-----------|---------|
| Bitcoin | btcpayserver_bitcoind | ✅ Running |
| BTCPay | generated_btcpayserver_1 | ✅ Running |
| NBXplorer | generated_nbxplorer_1 | ✅ Running |
| Database | generated_postgres_1 | ✅ Running |
| Tor | tor | ✅ Running |
| Proxy | nginx-proxy-manager | ✅ Running |
## Monitoring Commands
### Check Sync Progress
```bash
ssh -p 2255 -i vps_hardening_key sysadmin@thebankofdebbie.giize.com
sudo docker logs btcpayserver_bitcoind | grep "Rolling forward" | tail -5
```
### Check Disk Usage
```bash
sudo docker exec btcpayserver_bitcoind du -sh /data
```
### View Bitcoin Logs
```bash
sudo docker logs btcpayserver_bitcoind --tail 50
```
## Configuration Files
### Docker Compose Override
Location: `/opt/btcpayserver-docker/docker-compose.override.yml`
```yaml
version: "3.6"
services:
bitcoind:
environment:
BITCOIN_EXTRA_ARGS: |
prune=10000
maxmempool=300
dbcache=1000
maxconnections=40
rpcthreads=6
```
### Environment
Location: `/opt/.env`
- BTCPAY_CRYPTOS=btc
- NBITCOIN_NETWORK=mainnet
- BTCPAYGEN_CRYPTO1=btc
- NOREVERSEPROXY_HTTP_PORT=8080
## Next Steps
1. **Wait for Bitcoin Sync**
- Will take 12-24 hours to fully sync
- BTCPay will show "Bitcoin node is syncing" until complete
- Can still configure stores while syncing
2. **Configure BTCPay Store**
- Access: https://thebankofdebbie.giize.com (via NPM)
- Create admin account if not done
- Add store and configure Bitcoin wallet
3. **Optional: Add Monero**
- Install Monero plugin in BTCPay
- Configure existing Monero wallet
- Address: 49TnBo2VHbncxvrMFbX5uMS9mtAGkiG1L4N6i7MMz4MhA9AXfyRqBdmf1XrFtGXq2v2G72TNtiVFo2kot5SHnBBz3gwoMj9
## Troubleshooting
### If Bitcoin stops syncing:
```bash
sudo docker restart btcpayserver_bitcoind
```
### If disk space issues:
```bash
# Check actual usage
df -h /
sudo docker system df
# Clean if needed
sudo docker system prune -a
```
### If BTCPay can't connect to Bitcoin:
```bash
sudo docker restart generated_nbxplorer_1
sudo docker restart generated_btcpayserver_1
```
## Success Metrics
- ✅ Bitcoin container running
- ✅ Pruning enabled (10GB limit)
- ✅ Connected to BTCPay
- ✅ Blockchain syncing
- ✅ Accessible via web interface
**Bitcoin is successfully restored and operational!**

99
Hostinger/BTCPAY_BACKUP_README.md Normal file
View File

@@ -0,0 +1,99 @@
# BTCPay Server Complete Backup
**Created: September 16, 2025**
## Backup Contents
### File: `btcpay-backup-20250916.tar.gz` (615KB)
This archive contains:
1. **Configuration Files**
- `/opt/.env` - Environment variables
- `Generated/` - Docker compose generated files
- `docker-compose.override.yml` - Custom overrides
- BTCPay scripts (*.sh files)
2. **Monero Wallet Data**
- Wallet address: `49TnBo2VHbncxvrMFbX5uMS9mtAGkiG1L4N6i7MMz4MhA9AXfyRqBdmf1XrFtGXq2v2G72TNtiVFo2kot5SHnBBz3gwoMj9`
- Wallet files and keys
- Password: `password` (simple password for RPC)
3. **Database**
- Complete PostgreSQL dump of BTCPay database
- Includes stores, users, invoices, settings
4. **Tor Configuration**
- Onion addresses for BTCPay and Bitcoin
## Server Configuration
- **Host**: thebankofdebbie.giize.com (srv1002428.hstgr.cloud)
- **Network**: Mainnet
- **BTCPay Version**: 2.2.1
- **Cryptocurrencies**: BTC (with pruning), XMR
- **NO DOGECOIN**: Successfully removed
## How to Restore
### On a fresh Debian/Ubuntu server:
1. **Copy backup to server:**
```bash
scp btcpay-backup-20250916.tar.gz root@newserver:/root/
```
2. **Extract backup:**
```bash
cd /root
tar -xzf btcpay-backup-20250916.tar.gz
cd btcpay-backup-20250916-1614
```
3. **Restore configurations:**
```bash
# Copy environment file
cp env-file /opt/.env
# Install BTCPay
git clone https://github.com/btcpayserver/btcpayserver-docker /opt/btcpayserver-docker
cd /opt/btcpayserver-docker
# Copy configurations
cp -r ~/btcpay-backup-*/Generated ./
cp ~/btcpay-backup-*/docker-compose.override.yml ./
# Run setup
. ./btcpay-setup.sh -i
```
4. **Restore database:**
```bash
docker exec -i generated_postgres_1 psql -U postgres < ~/btcpay-backup-*/postgres-backup.sql
```
5. **Restore Monero wallet:**
```bash
docker cp ~/btcpay-backup-*/monero-wallet/. btcpayserver_monero_wallet:/wallet/
docker restart btcpayserver_monero_wallet
```
## Important Security Notes
⚠️ **KEEP THIS BACKUP SECURE!**
- Contains wallet private keys
- Contains database with transaction history
- Contains Tor private keys
## Current System Status
- ✅ Bitcoin: 99.7% synced, pruning active (25GB)
- ✅ Monero: Wallet configured and running
- ✅ SSL: Valid Let's Encrypt certificate
- ✅ Tor: Fully operational
- ✅ DOGE: Completely removed (0 traces)
## Access Information
- URL: https://thebankofdebbie.giize.com
- SSH: Port 2255 with key authentication
- Network: 10 containers running smoothly
---
**Backup created by BTCPay fix session - September 16, 2025**

294
Hostinger/BTCPay_Tor_Setup.txt Normal file
View File

@@ -0,0 +1,294 @@
================================================================================
BTCPAY SERVER WITH TOR INTEGRATION SETUP
================================================================================
Setup Completed: September 10, 2025
Status: FULLY OPERATIONAL WITH TOR HIDDEN SERVICES ✅
================================================================================
TOR ONION ADDRESSES
================================================================================
🧅 BTCPAY SERVER ONION ADDRESS:
njoc2ubkk7ymgqfg6plt3wcltvcvuv3j4eemixnovicegrlwhq2zwfad.onion
🔗 BITCOIN P2P ONION ADDRESS:
s7n55wptvooma4gqsbdo5vn6v6nphjffqsmlufoa3fzqhwkqgeasslad.onion
⚠️ IMPORTANT: Keep these addresses private and secure!
================================================================================
ACCESS METHODS
================================================================================
🌐 CLEARNET ACCESS (Standard Web):
https://srv1002428.hstgr.cloud
- Full BTCPay functionality
- SSL/TLS encrypted
- Public internet accessible
🧅 TOR ONION ACCESS (Maximum Privacy):
http://njoc2ubkk7ymgqfg6plt3wcltvcvuv3j4eemixnovicegrlwhq2zwfad.onion
- Requires Tor Browser
- Complete anonymity for customers
- No exit node exposure
🔐 SSH TUNNEL ACCESS (Admin Security):
ssh -i vps_hardening_key -p 2255 -L 8080:localhost:80 ubuntu@srv1002428.hstgr.cloud
Then browse to: http://localhost:8080
================================================================================
BITCOIN NODE CONFIGURATION
================================================================================
⚙️ BITCOIN CORE SETTINGS:
Mode: PRUNED (50GB blockchain storage)
Network: Tor-Only (onlynet=onion)
Connections: Up to 16 onion peers
Proxy: tor:9050 (internal Docker network)
P2P Service: s7n55wptvooma4gqsbdo5vn6v6nphjffqsmlufoa3fzqhwkqgeasslad.onion
📊 SYNC STATUS:
Initial sync: In progress (headers downloading over Tor)
Expected time: 12-24 hours for full sync
Storage usage: ~50GB maximum (pruned)
🔒 PRIVACY FEATURES:
✅ All Bitcoin P2P traffic via Tor
✅ No clearnet Bitcoin connections
✅ Automatic onion peer discovery
✅ Hidden service for incoming connections
================================================================================
DOCKER SERVICES RUNNING
================================================================================
🐳 BTCPAY CORE SERVICES:
✅ btcpayserver_bitcoind - Bitcoin Core (pruned + Tor)
✅ generated_btcpayserver_1 - BTCPay Server application
✅ generated_nbxplorer_1 - Blockchain explorer
✅ generated_postgres_1 - PostgreSQL database
✅ nginx - Reverse proxy with SSL
✅ tor - Tor daemon for onion services
✅ tor-gen - Tor configuration generator
🔐 TOR SERVICES:
✅ Hidden service for BTCPay web interface
✅ Hidden service for Bitcoin P2P network
✅ Automatic onion address generation
✅ Traffic routing through Tor network
================================================================================
LIGHTNING NETWORK
================================================================================
⚡ LIGHTNING STATUS:
Currently: NOT ENABLED (can be added later)
To enable Lightning Network with Tor:
1. Run: sudo /opt/btcpayserver-docker/btcpay-setup.sh
2. Set BTCPAYGEN_LIGHTNING=lnd (or clightning)
3. Lightning will automatically get Tor hidden service
⚡ LIGHTNING OVER TOR FEATURES:
- Hidden service for Lightning node
- Tor-only channel connections
- Invoice generation over onion network
- Complete payment privacy
================================================================================
SECURITY CONFIGURATION
================================================================================
🔒 NETWORK SECURITY:
✅ UFW Firewall active with BTCPay rules
✅ SSH on port 2255 (key authentication)
✅ Fail2Ban monitoring SSH and web access
✅ Dokploy admin panel blocked externally
✅ Tor traffic allowed for local connections
🛡️ TOR SECURITY:
✅ Bitcoin node: Tor-only (no clearnet connections)
✅ BTCPay Server: Accessible via both clearnet and onion
✅ Hidden services properly configured
✅ No DNS leaks (Bitcoin uses onlynet=onion)
⚠️ SECURITY NOTES:
- Tor provides privacy, not perfect anonymity
- BTCPay plugins may have clearnet dependencies
- Regular security updates still required
- Monitor logs for any clearnet leaks
================================================================================
STORAGE & PERFORMANCE
================================================================================
💾 CURRENT STORAGE USAGE:
Total Space: 387GB SSD
BTCPay Services: ~5GB
Bitcoin Blockchain: ~50GB (pruned, growing)
Docker Images: ~3GB
Available: ~329GB remaining
📈 PERFORMANCE EXPECTATIONS:
Bitcoin Sync: Slower over Tor (12-24 hours)
Transaction Processing: Normal speed
Web Interface: Slight Tor overhead for onion access
API Calls: Standard response times
🔄 MAINTENANCE:
Bitcoin pruning: Automatic (keeps last 50GB)
Log rotation: Configured in Docker daemon
Backup schedule: Manual (set up as needed)
================================================================================
BACKUP PROCEDURES
================================================================================
💾 CRITICAL DATA TO BACKUP:
1. BTCPay Database: /var/lib/docker/volumes/generated_postgres_*
2. Bitcoin Wallet: /var/lib/docker/volumes/generated_bitcoin_*
3. Tor Keys: /var/lib/docker/volumes/generated_tor_*
4. Configuration: /opt/.env and /opt/btcpayserver-docker/
🔄 BACKUP COMMANDS:
# Create backup archive
sudo tar -czf btcpay-backup-$(date +%Y%m%d).tar.gz \
/var/lib/docker/volumes/generated_* \
/opt/.env \
/opt/btcpayserver-docker/docker-compose.generated.yml
# Restore from backup
sudo systemctl stop btcpayserver
sudo tar -xzf btcpay-backup-YYYYMMDD.tar.gz -C /
sudo systemctl start btcpayserver
================================================================================
MONITORING COMMANDS
================================================================================
🔍 SYSTEM HEALTH:
# Bitcoin sync status
sudo docker exec btcpayserver_bitcoind bitcoin-cli getblockchaininfo
# BTCPay services status
sudo docker ps | grep -E "(btcpay|bitcoin|tor)"
# Tor connectivity
sudo docker exec tor ps aux | grep tor
# Storage usage
df -h /
🔧 MAINTENANCE COMMANDS:
# Restart all BTCPay services
sudo btcpay-restart.sh
# Check Bitcoin logs
sudo docker logs btcpayserver_bitcoind --tail 50
# Check BTCPay logs
sudo docker logs generated_btcpayserver_1 --tail 50
# Update BTCPay to latest version
sudo btcpay-update.sh
================================================================================
INTEGRATION WITH LITTLESHOP
================================================================================
🔗 API INTEGRATION:
Clearnet API: https://srv1002428.hstgr.cloud/api
Onion API: http://njoc2ubkk7ymgqfg6plt3wcltvcvuv3j4eemixnovicegrlwhq2zwfad.onion/api
For maximum privacy, use onion API endpoint in LittleShop configuration.
💳 PAYMENT PROCESSING:
✅ Bitcoin payments (on-chain)
✅ Invoice generation
✅ Webhook notifications
✅ Payment verification
⚡ Lightning payments (when enabled)
🔐 WEBHOOK CONFIGURATION:
For Tor privacy, configure webhooks to use onion address:
http://njoc2ubkk7ymgqfg6plt3wcltvcvuv3j4eemixnovicegrlwhq2zwfad.onion/webhook
================================================================================
TROUBLESHOOTING
================================================================================
🚨 COMMON ISSUES:
1. Bitcoin Sync Slow:
- Normal over Tor network
- Check: docker logs btcpayserver_bitcoind
- Solution: Wait 12-24 hours for initial sync
2. Onion Service Not Accessible:
- Check Tor container: docker ps | grep tor
- Restart if needed: docker restart tor
- Verify address: cat /var/lib/docker/volumes/generated_tor_servicesdir/_data/BTCPayServer/hostname
3. BTCPay Web Interface Not Loading:
- Check nginx: docker logs nginx
- Restart services: btcpay-restart.sh
- Check SSL certificate: curl -I https://srv1002428.hstgr.cloud
4. Storage Issues:
- Monitor with: df -h /
- Bitcoin pruning should keep usage ~50GB
- Clean old Docker images: btcpay-clean.sh
🔧 RECOVERY PROCEDURES:
If BTCPay becomes unresponsive:
1. sudo btcpay-restart.sh
2. Check logs for errors
3. If needed: sudo btcpay-down.sh && sudo btcpay-up.sh
4. Last resort: Restore from backup
================================================================================
NEXT STEPS
================================================================================
🎯 IMMEDIATE ACTIONS:
1. Wait for Bitcoin initial sync to complete (~24 hours)
2. Access BTCPay via Tor Browser using onion address
3. Create BTCPay admin account during setup wizard
4. Test payment processing with small amount
⚡ OPTIONAL ENHANCEMENTS:
1. Enable Lightning Network for instant payments
2. Set up automated backups
3. Configure email notifications
4. Add additional cryptocurrencies (Monero, Litecoin)
🔗 LITTLESHOP INTEGRATION:
1. Update LittleShop config to use BTCPay API
2. Test order creation and payment flow
3. Configure webhook endpoints
4. Enable Tor routing for maximum customer privacy
================================================================================
SUPPORT & RESOURCES
================================================================================
📚 DOCUMENTATION:
BTCPay Server Docs: https://docs.btcpayserver.org/
Tor Project: https://www.torproject.org/
Bitcoin Core: https://bitcoincore.org/
🛠️ USEFUL COMMANDS REFERENCE:
btcpay-setup.sh - Reconfigure BTCPay Server
btcpay-restart.sh - Restart all services
btcpay-update.sh - Update to latest version
btcpay-clean.sh - Remove old Docker images
bitcoin-cli.sh - Bitcoin Core CLI commands
🔐 SECURITY RESOURCES:
Check for updates: sudo apt list --upgradable
UFW status: sudo ufw status
Fail2Ban status: sudo fail2ban-client status
================================================================================
END OF BTCPAY TOR SETUP
================================================================================

270
Hostinger/CONFIG_BACKUP.txt Normal file
View File

@@ -0,0 +1,270 @@
================================================================================
CURRENT BTCPAY CONFIGURATION BACKUP
================================================================================
Backup Date: September 10, 2025
Source: Ubuntu 24.04 BTCPay Setup (to be replaced with Debian 13)
Status: WORKING - Bitcoin pruning active, Tor fully operational
================================================================================
TOR ONION ADDRESSES
================================================================================
🧅 CURRENT ONION ADDRESSES (will change with new installation):
BTCPay Server: njoc2ubkk7ymgqfg6plt3wcltvcvuv3j4eemixnovicegrlwhq2zwfad.onion
Bitcoin P2P: s7n55wptvooma4gqsbdo5vn6v6nphjffqsmlufoa3fzqhwkqgeasslad.onion
⚠️ NOTE: New Debian 13 installation will generate NEW onion addresses
These addresses will be lost and cannot be recovered.
================================================================================
BTCPAY ENVIRONMENT BACKUP
================================================================================
Working BTCPay Environment Variables (/opt/.env):
BTCPAY_PROTOCOL=https
BTCPAY_HOST=srv1002428.hstgr.cloud
BTCPAY_LIGHTNING_HOST=
BTCPAY_ADDITIONAL_HOSTS=
BTCPAY_ANNOUNCEABLE_HOST=srv1002428.hstgr.cloud
REVERSEPROXY_HTTP_PORT=80
REVERSEPROXY_HTTPS_PORT=443
REVERSEPROXY_DEFAULT_HOST=none
NOREVERSEPROXY_HTTP_PORT=
BTCPAY_IMAGE=
ACME_CA_URI=production
NBITCOIN_NETWORK=mainnet
LETSENCRYPT_EMAIL=
LIGHTNING_ALIAS=
BTCPAY_SSHTRUSTEDFINGERPRINTS=
BTCPAY_SSHKEYFILE=/datadir/host_id_ed25519
BTCPAY_SSHAUTHORIZEDKEYS=/datadir/host_authorized_keys
BTCPAY_HOST_SSHAUTHORIZEDKEYS=/home/ubuntu/.ssh/authorized_keys
LIBREPATRON_HOST=
TALLYCOIN_APIKEY=
TALLYCOIN_PASSWD=
TALLYCOIN_PASSWD_CLEARTEXT=
CLOUDFLARE_TUNNEL_TOKEN=
================================================================================
WORKING BITCOIN CONFIGURATION
================================================================================
CRITICAL: Working Bitcoin Configuration in Docker Compose:
BITCOIN_EXTRA_ARGS: |-
rpcport=43782
rpcbind=0.0.0.0:43782
rpcallowip=0.0.0.0/0
port=39388
whitelist=0.0.0.0/0
maxmempool=500
prune=10000 ⭐ CRITICAL: Pruning enabled (10GB max)
onion=tor:9050 ⭐ CRITICAL: Tor-only networking
rpcauth=btcrpc:a6a5d29a3f44f02e4cd8cabb5b10a234$ab6152915515f6a9cca806d2ab5f0e2794c346ba74f812c61e48241d523778b8
mempoolfullrbf=1
HIDDEN SERVICES:
HIDDENSERVICE_NAME: BTC-P2P,BTC-RPC
BTC-P2P_HIDDENSERVICE_VIRTUAL_PORT: 8333
BTC-P2P_HIDDENSERVICE_PORT: 39388
BTC-RPC_HIDDENSERVICE_VIRTUAL_PORT: 8332
================================================================================
SSH SECURITY BACKUP
================================================================================
Working SSH Configuration:
Port 2255 ⭐ CRITICAL: Custom port
PermitRootLogin no ⭐ CRITICAL: Root disabled
PubkeyAuthentication yes ⭐ CRITICAL: Key auth
PasswordAuthentication yes ⚠️ Enabled for safety (disable after key test)
AuthorizedKeysFile .ssh/authorized_keys
MaxAuthTries 3
LoginGraceTime 30
MaxStartups 3
ChallengeResponseAuthentication no
UsePAM yes
Protocol 2
Ciphers aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,aes256-ctr
MACs hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,umac-128-etm@openssh.com
X11Forwarding no
AllowTcpForwarding no
AllowAgentForwarding no
PermitTunnel no
AllowUsers ubuntu ⭐ CRITICAL: Only ubuntu user
Banner /etc/ssh/ssh-banner
SSH Public Key (for ubuntu user):
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIDoUnUn5wsJyelx5NAzP1lrcTBKAV93m8R1hlR0ZU07Z vps-hardening-20250910
================================================================================
FIREWALL CONFIGURATION
================================================================================
Working UFW Rules:
Status: active
To Action From
-- ------ ----
2255/tcp ALLOW Anywhere # SSH-Hardened
80/tcp ALLOW Anywhere # HTTP-BTCPay
443/tcp ALLOW Anywhere # HTTPS-BTCPay
3000/tcp DENY Anywhere # Block-Dokploy-External
9050/tcp ALLOW 127.0.0.0/8 # Tor-Local
================================================================================
FAIL2BAN CONFIGURATION
================================================================================
Working Jail Configuration (/etc/fail2ban/jail.local):
[DEFAULT]
bantime = 3600
findtime = 600
maxretry = 3
loglevel = INFO
[sshd]
enabled = true
port = 2255 ⭐ CRITICAL: Custom SSH port
filter = sshd
backend = systemd
bantime = 7200
maxretry = 3
[nginx-http-auth]
enabled = true
port = 80,443
filter = nginx-http-auth
logpath = /var/log/nginx/error.log
[nginx-noscript]
enabled = true
port = 80,443
filter = nginx-noscript
logpath = /var/log/nginx/access.log
[nginx-badbots]
enabled = true
port = 80,443
filter = nginx-badbots
logpath = /var/log/nginx/access.log
maxretry = 2
================================================================================
DOCKER SERVICES STATUS
================================================================================
Working Docker Containers (8 total):
✅ btcpayserver_bitcoind - Bitcoin Core (pruned + Tor)
✅ generated_btcpayserver_1 - BTCPay Server application
✅ generated_nbxplorer_1 - Blockchain explorer
✅ generated_postgres_1 - PostgreSQL database
✅ nginx - Reverse proxy + SSL
✅ tor - Tor daemon
✅ tor-gen - Tor config generator
✅ letsencrypt-nginx-proxy-companion - SSL certificate manager
All containers: UP and running
Bitcoin status: PRUNED mode confirmed in logs
Tor status: Hidden services active
================================================================================
DISK USAGE STATUS
================================================================================
Working Storage Allocation:
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 387G 11G 377G 3% /
Breakdown:
- System + Docker: ~5GB
- BTCPay Services: ~3GB
- Bitcoin (pruned): ~3GB (will grow to max 10GB)
- Available: 377GB
⭐ CRITICAL SUCCESS: Bitcoin pruning working - logs show:
"Config file arg: [main] prune="10000""
"Prune configured to target 10000 MiB on disk for block and undo files."
================================================================================
MONITORING COMMANDS
================================================================================
Working Commands for New Installation:
# Status monitoring
~/monitor-btcpay.sh # Overall status
docker ps | grep btcpay # Container status
df -h / # Disk usage
sudo fail2ban-client status # Security status
# Bitcoin specific
docker exec btcpayserver_bitcoind bitcoin-cli getblockchaininfo
docker logs btcpayserver_bitcoind | grep prune
# Tor addresses
sudo cat /var/lib/docker/volumes/generated_tor_servicesdir/_data/BTCPayServer/hostname
sudo cat /var/lib/docker/volumes/generated_tor_servicesdir/_data/BTC-P2P/hostname
# Maintenance
sudo btcpay-restart.sh # Restart services
sudo btcpay-update.sh # Update BTCPay
sudo btcpay-clean.sh # Clean Docker images
================================================================================
CRITICAL LESSONS
================================================================================
⭐ CRITICAL ISSUES RESOLVED:
1. BITCOIN PRUNING CONFIGURATION:
- Must add "prune=10000" to Docker Compose BITCOIN_EXTRA_ARGS
- BTCPay generator overwrites manual bitcoin.conf changes
- Required clearing blockchain data to activate pruning from scratch
- Logs must show: "Prune configured to target 10000 MiB"
2. TOR CONFIGURATION:
- opt-add-tor fragment works correctly
- Hidden services generate automatically within 5 minutes
- onion=tor:9050 in BITCOIN_EXTRA_ARGS enables Tor-only networking
3. SSH SECURITY:
- Port 2255 avoids common attacks on port 22
- Must disable systemd ssh.socket to use custom port
- Keep password auth enabled until SSH keys tested
- AllowUsers ubuntu prevents root access
4. FIREWALL SETUP:
- UFW must allow new SSH port before restarting SSH
- Tor port 9050 needs local access for Bitcoin
- Block unnecessary services (like Dokploy port 3000)
5. STORAGE MANAGEMENT:
- 387GB VPS is perfect with pruning (10GB Bitcoin max)
- Monitor disk usage during initial sync
- Clear blockchain data if pruning not working
================================================================================
BACKUP VERIFICATION
================================================================================
✅ Configuration backed up and verified working
✅ Automation scripts created and tested
✅ SSH keys preserved for new installation
✅ All critical settings documented
✅ Troubleshooting knowledge captured
✅ Ready for Debian 13 OS reinstallation
ESTIMATED RESTORATION TIME: 30 minutes + 24 hours Bitcoin sync
================================================================================
END OF BACKUP
================================================================================

300
Hostinger/DEBIAN13_SETUP_GUIDE.md Normal file
View File

@@ -0,0 +1,300 @@
# DEBIAN 13 VPS SETUP GUIDE
## Complete BTCPay Server + Tor Restoration
**Target:** Hostinger VPS thebankofdebbie.giize.com (31.97.57.205)
**Date:** September 10, 2025
**Status:** Ready for Debian 13 OS rebuild
---
## 🎯 **QUICK START (30 Minutes)**
### Step 1: Fresh Debian 13 Installation
1. Reinstall Debian 13 via Hostinger control panel
2. Use password: `Th3fa1r13sd1d1t.` (keep this initially)
3. Wait for OS installation to complete
### Step 2: Copy SSH Key and Scripts
```bash
# On your local machine
scp -P 22 vps_hardening_key* root@thebankofdebbie.giize.com:/tmp/
scp -P 22 debian13_vps_hardening.sh root@thebankofdebbie.giize.com:/tmp/
scp -P 22 btcpay_tor_installer.sh root@thebankofdebbie.giize.com:/tmp/
```
### Step 3: Run VPS Hardening (5 minutes)
```bash
# SSH to fresh Debian 13 server
ssh root@thebankofdebbie.giize.com
# Make scripts executable
chmod +x /tmp/*.sh
# Run hardening script
/tmp/debian13_vps_hardening.sh
# Add your SSH public key
cat /tmp/vps_hardening_key.pub > /home/ubuntu/.ssh/authorized_keys
chown ubuntu:ubuntu /home/ubuntu/.ssh/authorized_keys
chmod 600 /home/ubuntu/.ssh/authorized_keys
```
### Step 4: Test SSH Keys (CRITICAL)
```bash
# Test SSH key access on new port
ssh -i vps_hardening_key -p 2255 ubuntu@thebankofdebbie.giize.com
# If successful, disable password auth:
sudo sed -i 's/PasswordAuthentication yes/PasswordAuthentication no/' /etc/ssh/sshd_config
sudo systemctl restart ssh
```
### Step 5: Install BTCPay Server + Tor (15 minutes)
```bash
# Run as root
sudo su -
/tmp/btcpay_tor_installer.sh
```
### Step 6: Monitor Installation
```bash
# Check status
./monitor-btcpay.sh
# Watch Bitcoin sync progress
docker logs btcpayserver_bitcoind -f
```
---
## 🔧 **DETAILED CONFIGURATION**
### Previous Working Configuration
```
BTCPay Onion: njoc2ubkk7ymgqfg6plt3wcltvcvuv3j4eemixnovicegrlwhq2zwfad.onion
Bitcoin P2P Onion: s7n55wptvooma4gqsbdo5vn6v6nphjffqsmlufoa3fzqhwkqgeasslad.onion
Note: New installation will generate NEW onion addresses
```
### Bitcoin Configuration
```bash
# Verified working config in BITCOIN_EXTRA_ARGS:
prune=10000 # 10GB max blockchain storage
rpcport=43782
rpcbind=0.0.0.0:43782
rpcallowip=0.0.0.0/0
port=39388
whitelist=0.0.0.0/0
maxmempool=500
onion=tor:9050
```
### Security Configuration
```bash
# SSH
Port 2255
PermitRootLogin no
AllowUsers ubuntu
PubkeyAuthentication yes
# UFW Firewall
2255/tcp ALLOW SSH-Hardened
80/tcp ALLOW HTTP-BTCPay
443/tcp ALLOW HTTPS-BTCPay
9050 ALLOW Tor-Local (127.0.0.0/8)
# Fail2Ban
SSH: 3 attempts -> 2 hour ban
Web: monitoring nginx logs
```
---
## 🚨 **CRITICAL SUCCESS POINTS**
### ✅ **Must Work Before Proceeding:**
1. SSH key authentication on port 2255
2. UFW firewall active with correct rules
3. Fail2Ban monitoring logs
4. Docker running and ubuntu in docker group
### ✅ **BTCPay Installation Success Indicators:**
1. All Docker containers running (8 containers)
2. Bitcoin logs show: "Prune configured to target 10000 MiB"
3. Tor onion addresses generated in 5 minutes
4. Web interface accessible on both clearnet and onion
### ⚠️ **Common Issues & Solutions:**
**Issue:** Bitcoin not in pruned mode
```bash
# Solution: Clear blockchain and restart
sudo btcpay-down.sh
docker run --rm -v generated_bitcoin_datadir:/data alpine rm -rf /data/blocks /data/chainstate
sudo btcpay-up.sh
```
**Issue:** Port conflicts
```bash
# Solution: Stop conflicting services first
sudo docker stop $(sudo docker ps -aq) 2>/dev/null || true
sudo btcpay-up.sh
```
**Issue:** Onion services not generating
```bash
# Solution: Restart Tor container
sudo docker restart tor tor-gen
# Wait 5 minutes, then check:
sudo cat /var/lib/docker/volumes/generated_tor_servicesdir/_data/BTCPayServer/hostname
```
---
## 📊 **EXPECTED RESULTS**
### Disk Usage After Complete Setup:
```
System + Docker: ~5GB
BTCPay Services: ~3GB
Bitcoin (pruned): ~10GB (max)
Available: ~369GB
Total Used: ~18GB / 387GB (5%)
```
### Performance Expectations:
```
Initial Bitcoin Sync: 12-24 hours (over Tor)
Bitcoin Storage: 10GB maximum (pruned)
Web Response: Normal (slight Tor overhead for onion)
Payment Processing: Real-time
```
### Services Running (8 containers):
```
✅ btcpayserver_bitcoind - Bitcoin Core (pruned, Tor-only)
✅ generated_btcpayserver_1 - BTCPay Server application
✅ generated_nbxplorer_1 - Blockchain explorer
✅ generated_postgres_1 - PostgreSQL database
✅ nginx - Reverse proxy with SSL
✅ tor - Tor daemon + onion services
✅ tor-gen - Tor configuration generator
✅ letsencrypt-... - SSL certificate manager
```
---
## 🔐 **SECURITY FEATURES RESTORED**
### Network Security:
- ✅ SSH on port 2255 with key auth only
- ✅ UFW firewall with minimal allowed ports
- ✅ Fail2Ban monitoring SSH and web attacks
- ✅ Bitcoin P2P traffic only via Tor network
- ✅ BTCPay accessible via both clearnet and Tor
### Privacy Features:
- ✅ Bitcoin node uses onlynet=onion (no clearnet P2P)
- ✅ BTCPay Server accessible via .onion address
- ✅ Customer payments can be completely anonymous
- ✅ No DNS leaks (Bitcoin doesn't use clearnet DNS)
### Storage Management:
- ✅ Bitcoin blockchain limited to 10GB (pruned)
- ✅ Automatic old block removal
- ✅ Safe for 387GB VPS with room to grow
- ✅ Full validation capability maintained
---
## 🔄 **MAINTENANCE COMMANDS**
### Daily Monitoring:
```bash
~/monitor-btcpay.sh # Overall status
sudo docker ps | grep btcpay # Container status
df -h / # Disk usage
sudo fail2ban-client status # Security status
```
### Maintenance:
```bash
sudo btcpay-restart.sh # Restart all services
sudo btcpay-update.sh # Update BTCPay Server
sudo btcpay-clean.sh # Clean old Docker images
docker logs btcpayserver_bitcoind # Check Bitcoin sync
```
### Emergency Recovery:
```bash
sudo btcpay-down.sh # Stop everything
sudo btcpay-up.sh # Start everything
# If needed: Re-run btcpay_tor_installer.sh
```
---
## 📞 **SUPPORT INFORMATION**
### If Something Goes Wrong:
1. **SSH Issues:** Contact Hostinger for console access
2. **Bitcoin Storage:** Monitor with `df -h` - should never exceed 15GB total
3. **BTCPay Problems:** Check `docker logs generated_btcpayserver_1`
4. **Tor Issues:** Restart tor containers, wait 5 minutes for onion addresses
### Key Files Backup:
- SSH Keys: `/home/ubuntu/.ssh/`
- BTCPay Config: `/opt/.env`
- Docker Compose: `/opt/btcpayserver-docker/Generated/docker-compose.generated.yml`
- Tor Keys: `/var/lib/docker/volumes/generated_tor_servicesdir/`
---
## 🎯 **SUCCESS CRITERIA**
**✅ Installation Complete When:**
1. SSH key access works on port 2255
2. All 8 Docker containers running
3. Bitcoin logs show pruning active
4. BTCPay accessible on both clearnet and onion
5. Disk usage under 20GB total
6. New onion addresses generated and documented
**🚀 Ready for LittleShop Integration When:**
1. Bitcoin initial sync completed (24 hours)
2. BTCPay setup wizard completed
3. Test payment successful
4. API endpoints responding
5. Webhook configuration tested
---
## 📋 **FINAL CHECKLIST**
**Before Declaring Success:**
- [ ] SSH key authentication working on port 2255
- [ ] Password authentication disabled
- [ ] UFW firewall active with 4 rules
- [ ] Fail2Ban showing 2+ active jails
- [ ] 8 Docker containers running
- [ ] Bitcoin pruning confirmed in logs
- [ ] BTCPay onion address generated
- [ ] Disk usage under 20GB
- [ ] Web interface accessible
- [ ] Monitoring script working
**Debian 13 advantages over Ubuntu:**
- More granular security controls
- Better systemd hardening options
- Reduced attack surface (minimal packages)
- More predictable package management
- Enhanced AppArmor/SELinux integration
---
**🎉 Total Setup Time: ~30 minutes + 24 hours Bitcoin sync**
**🔒 Security Level: Maximum (Tor + hardened OS + pruned storage)**
**💾 Storage Safe: Yes (10GB max Bitcoin + 10GB overhead = 20GB total)**
Ready to deploy! 🚀

182
Hostinger/DEPLOY_BTCPAY_API_TO_SILVERLABS.md Normal file
View File

@@ -0,0 +1,182 @@
# Deploy BTCPay API to SilverLABS Infrastructure
## Target Server: PORTAINER-02 (10.0.0.52)
**Location:** Same server as Mattermost (ops.silverlabs.uk)
## Files to Deploy
1. **mattermost_local_api.js** - Main API server
2. **vps_hardening_key** - SSH key for VPS access
3. **package.json** - Node.js dependencies
## Deployment Steps
### 1. Access PORTAINER-02 Server
```bash
# SSH to PORTAINER-02
ssh sysadmin@10.0.0.52
# Password: Phenom12#.
```
### 2. Create Directory Structure
```bash
# Create API directory
mkdir -p /home/sysadmin/btcpay-api
cd /home/sysadmin/btcpay-api
# Create SSH keys directory
mkdir -p ~/.ssh
```
### 3. Copy Files (Manual Transfer)
Copy these files to `/home/sysadmin/btcpay-api/`:
**mattermost_local_api.js** (already configured with correct SSH key path)
**vps_hardening_key** (SSH key for thebankofdebbie.giize.com)
### 4. Set Up SSH Key
```bash
# Copy SSH key to proper location
cp /home/sysadmin/btcpay-api/vps_hardening_key ~/.ssh/
chmod 600 ~/.ssh/vps_hardening_key
# Test SSH connectivity to BTCPay VPS
ssh -i ~/.ssh/vps_hardening_key -p 2255 -o ConnectTimeout=10 sysadmin@thebankofdebbie.giize.com "echo 'SSH test successful'"
```
### 5. Install Node.js Dependencies
```bash
cd /home/sysadmin/btcpay-api
# Install Node.js if not present
curl -fsSL https://deb.nodesource.com/setup_18.x | sudo -E bash -
sudo apt-get install -y nodejs
# Install required packages
npm install express
# Create package.json for future dependencies
cat > package.json << 'EOF'
{
"name": "btcpay-api",
"version": "1.0.0",
"description": "Mattermost BTCPay SSH API Server",
"main": "mattermost_local_api.js",
"dependencies": {
"express": "^4.18.0"
},
"scripts": {
"start": "node mattermost_local_api.js",
"dev": "node mattermost_local_api.js"
}
}
EOF
```
### 6. Update Configuration
Edit `mattermost_local_api.js` and verify these settings:
```javascript
const config = {
vps_domain: 'thebankofdebbie.giize.com',
vps_port: 2255,
vps_user: 'sysadmin',
ssh_key_path: '/home/sysadmin/.ssh/vps_hardening_key', // ✅ Correct path
mattermost_token: '7grgg4r7sjf4dx9qxa7wuybmnh', // ✅ Already configured
allowed_users: ['bankofdebbie', 'admin', 'sysadmin']
};
```
### 7. Test the API Server
```bash
cd /home/sysadmin/btcpay-api
# Start the server (test mode)
node mattermost_local_api.js
# Should see:
# 🚀 Mattermost BTCPay Local API running on localhost:3333
# 🎯 Target VPS: thebankofdebbie.giize.com:2255
```
### 8. Set Up as Service (Production)
```bash
# Create systemd service
sudo tee /etc/systemd/system/btcpay-api.service << 'EOF'
[Unit]
Description=BTCPay Mattermost API Server
After=network.target
[Service]
Type=simple
User=sysadmin
WorkingDirectory=/home/sysadmin/btcpay-api
ExecStart=/usr/bin/node mattermost_local_api.js
Restart=always
RestartSec=10
Environment=NODE_ENV=production
[Install]
WantedBy=multi-user.target
EOF
# Enable and start service
sudo systemctl daemon-reload
sudo systemctl enable btcpay-api
sudo systemctl start btcpay-api
# Check status
sudo systemctl status btcpay-api
```
### 9. Test Slash Command
In Mattermost, try:
- `/btcpay help`
- `/btcpay` (get onion addresses)
- `/btcpay status` (full system status)
## Troubleshooting
### If SSH fails:
```bash
# Check SSH key permissions
ls -la ~/.ssh/vps_hardening_key # Should be 600
# Test SSH manually
ssh -i ~/.ssh/vps_hardening_key -p 2255 sysadmin@thebankofdebbie.giize.com "echo test"
```
### If API server fails:
```bash
# Check logs
journalctl -u btcpay-api -f
# Check if port 3333 is available
sudo netstat -tlnp | grep 3333
```
### If Mattermost can't connect:
1. Verify AllowedUntrustedInternalConnections includes `localhost:3333`
2. Check that API server is running: `curl http://localhost:3333/health`
## Security Notes
- API server only listens on localhost:3333 (not accessible externally)
- SSH key has 600 permissions (owner read/write only)
- Only authorized Mattermost users can execute commands
- All VPS communication uses SSH key authentication on port 2255
## File Locations After Deployment
- API Server: `/home/sysadmin/btcpay-api/mattermost_local_api.js`
- SSH Key: `/home/sysadmin/.ssh/vps_hardening_key`
- Service: `/etc/systemd/system/btcpay-api.service`
- Logs: `journalctl -u btcpay-api`
## Current Configuration
- **Mattermost URL**: http://localhost:3333/btcpay
- **Token**: 7grgg4r7sjf4dx9qxa7wuybmnh
- **VPS Target**: thebankofdebbie.giize.com:2255
- **SSH User**: sysadmin
- **Allowed Users**: bankofdebbie, admin, sysadmin

121
Hostinger/DEPLOY_TO_MATTERMOST.txt Normal file
View File

@@ -0,0 +1,121 @@
================================================================================
DEPLOY TO MATTERMOST - READY TO GO!
================================================================================
✅ **SLASH COMMAND CREATED**
Token: 7grgg4r7sjf4dx9qxa7wuybmnh
✅ **FILES UPDATED WITH CORRECT TOKEN**
mattermost_local_api.js now has the correct Mattermost token
================================================================================
DEPLOYMENT COMMANDS
================================================================================
🚀 **RUN THESE COMMANDS ON YOUR MATTERMOST SERVER:**
# 1. Setup directory
mkdir ~/btcpay-api
cd ~/btcpay-api
# 2. Copy files from this directory to your Mattermost server:
# - mattermost_local_api.js
# - vps_hardening_key
# - mattermost-local-package.json (rename to package.json)
# 3. Set permissions and install:
chmod 600 ./vps_hardening_key
npm install express
# 4. Update SSH key path in mattermost_local_api.js:
# Change line 25: ssh_key_path: '/home/your-user/btcpay-api/vps_hardening_key'
# 5. Test SSH connectivity:
ssh -i ./vps_hardening_key -p 2255 sysadmin@thebankofdebbie.giize.com "echo 'SSH test'"
# 6. Start the API:
node mattermost_local_api.js
# Expected output:
# 🚀 Mattermost BTCPay Local API running on localhost:3333
# 🎯 Target VPS: thebankofdebbie.giize.com:2255
# 🔑 Method: SSH-based command execution
================================================================================
MATTERMOST CONFIGURATION
================================================================================
✅ **SLASH COMMAND ALREADY CREATED**
Command: /btcpay
Token: 7grgg4r7sjf4dx9qxa7wuybmnh
URL: http://localhost:3333/btcpay
================================================================================
TESTING
================================================================================
🧪 **AFTER DEPLOYMENT, TEST:**
1. In Mattermost, type: `/btcpay`
2. Expected response:
```
## 🧅 BTCPay Tor Onion Addresses
🌐 Domain: https://thebankofdebbie.giize.com
🧅 Tor Hidden Services:
• BTCPay Server: gs76yqhlb4oysidnnswfoigxtwz3kmlmz4ekp2r6knmerpvsjdtbpxyd.onion
• Bitcoin P2P: p4gve626jjn73ia35ikr7zhnmwknokrzv2eb2gfbqlytlgbckhaeibyd.onion
📅 Retrieved: [timestamp]
👤 Requested by: bankofdebbie
```
🔧 **TROUBLESHOOTING:**
If `/btcpay` doesn't work:
1. Check API is running: `curl http://localhost:3333/health`
2. Test SSH: `ssh -i vps_key -p 2255 sysadmin@thebankofdebbie.giize.com "echo test"`
3. Check Mattermost logs for connection errors
================================================================================
SUCCESS INDICATORS
================================================================================
✅ **API Health Check Returns:**
{"status":"healthy","service":"Mattermost BTCPay Local API",...}
✅ **SSH Test Returns:**
"SSH test successful"
✅ **Mattermost `/btcpay` Returns:**
Formatted onion addresses and BTCPay information
================================================================================
FINAL STATUS
================================================================================
🎯 **YOUR INFRASTRUCTURE:**
🔐 **VPS (thebankofdebbie.giize.com):**
- BTCPay Server with Tor ✅
- Bitcoin pruned node (10GB max) ✅
- Maximum security hardening ✅
- No webhook ports exposed ✅
🤖 **Mattermost Integration:**
- Local API for SSH commands ✅
- Slash command configured ✅
- Secure onion address retrieval ✅
- No persistent connections ✅
🧅 **Live Onion Addresses:**
- BTCPay: gs76yqhlb4oysidnnswfoigxtwz3kmlmz4ekp2r6knmerpvsjdtbpxyd.onion
- Bitcoin: p4gve626jjn73ia35ikr7zhnmwknokrzv2eb2gfbqlytlgbckhaeibyd.onion
🚀 **READY FOR PRODUCTION BITCOIN PAYMENTS!**
================================================================================
Deploy the local API to your Mattermost server and test `/btcpay` command!

119
Hostinger/EMERGENCY_FIX.md Normal file
View File

@@ -0,0 +1,119 @@
# BTCPay Server 502 Bad Gateway - Emergency Fix
## Quick SSH Access
```bash
# From Windows/WSL:
ssh -p 2255 root@thebankofdebbie.giize.com
# Password: Th3fa1r13sd1d1t.
```
## Immediate Fix Commands (Run as root)
### Option 1: Quick Restart (Try First)
```bash
cd /opt/btcpayserver-docker
./btcpay-restart.sh
```
### Option 2: Check and Fix Specific Issues
```bash
# Check what's running
docker ps -a
# Restart stopped containers
docker start generated_btcpayserver_1
docker start generated_nginx_1
docker start generated_postgres_1
# Check logs for errors
docker logs generated_btcpayserver_1 --tail 50
docker logs generated_nginx_1 --tail 30
```
### Option 3: Full Docker Restart
```bash
# Restart Docker daemon
systemctl restart docker
# Wait 30 seconds
sleep 30
# Restart BTCPay
cd /opt/btcpayserver-docker
./btcpay-restart.sh
```
### Option 4: Rebuild Configuration
```bash
# Reload environment
source /opt/.env
# Regenerate and restart
cd /opt/btcpayserver-docker
./btcpay-setup.sh -i
```
## Common Causes & Solutions
### 1. Disk Space Full
```bash
# Check space
df -h /
# Clean Docker
docker system prune -a --volumes
# WARNING: This removes unused data!
```
### 2. Memory Issues
```bash
# Check memory
free -h
# Restart to free memory
systemctl restart docker
```
### 3. Database Corruption
```bash
# Check PostgreSQL
docker logs generated_postgres_1 --tail 100 | grep ERROR
# If corrupted, may need to restore from backup
```
### 4. Certificate Issues
```bash
# Check certificate
docker logs generated_letsencrypt-nginx-proxy-companion_1 --tail 50
# Force renewal if needed
docker exec generated_letsencrypt-nginx-proxy-companion_1 /app/force_renew
```
## Monitor After Fix
```bash
# Watch container status
watch docker ps
# Check if site is up
curl -I https://thebankofdebbie.giize.com
# Monitor logs
docker logs -f generated_btcpayserver_1
```
## If Nothing Works
1. **Check Hostinger Panel**: Ensure VPS is running and not suspended
2. **Check DNS**: Verify domain still points to correct IP
3. **Restore from Backup**: Use the backup we just created
## Prevention
- Set up monitoring: `uptimerobot.com` for free monitoring
- Regular backups: Run backup script weekly
- Check disk space: Add cron job to alert on low space
## Contact Support
- BTCPay Discord: https://chat.btcpayserver.org/
- Hostinger Support: If VPS issue

106
Hostinger/FAST_SYNC_OPTIMIZATION.md Normal file
View File

@@ -0,0 +1,106 @@
# Fast Sync Optimization for BTCPay Server
**Date**: September 16, 2025
## Optimizations Applied
### Bitcoin Core Fast Sync
- **dbcache**: Increased from 1000MB to 2000MB for faster processing
- **assumevalid**: Added recent block hash to skip signature verification for known-good blocks
- Hash: `00000000000000000002a23d6df20eecec15b21d32c75833cce28f113de888b7`
- This significantly speeds up initial sync by skipping cryptographic verification
### Monero Fast Sync
- **fast-block-sync**: Enabled for faster block processing
- **block-sync-size**: Set to 20 blocks per batch
- **max-concurrency**: Increased from 2 to 4 threads
- **db-sync-mode**: Changed from `safe:sync` to `fast:async:250000000bytes`
- `safe:sync` - Slowest but safest (original setting)
- `fast:async` - Much faster, slight risk if power loss during sync
- `fastest:async` - Maximum speed but highest risk (not recommended)
## Configuration File
Location: `/opt/btcpayserver-docker/docker-compose.override.yml`
```yaml
version: "3.6"
services:
bitcoind:
environment:
BITCOIN_EXTRA_ARGS: |
prune=10000
maxmempool=300
dbcache=2000
maxconnections=40
rpcthreads=6
assumevalid=00000000000000000002a23d6df20eecec15b21d32c75833cce28f113de888b7
monerod:
environment:
MONERO_EXTRA_ARGS: |
--prune-blockchain
--sync-pruned-blocks
--fast-block-sync=1
--block-sync-size=20
--max-concurrency=4
--db-sync-mode=fast:async:250000000bytes
```
## Expected Sync Times (With Optimizations)
### Before Optimizations
- Bitcoin: 24-36 hours
- Monero: 48-72 hours
### After Optimizations
- **Bitcoin**: 8-12 hours (from current 43% progress)
- **Monero**: 18-24 hours (from current 0.2% progress)
## Alternative Fast Sync Options
### 1. Bootstrap Files (Not Used)
- Download pre-synced blockchain data
- Pros: Very fast (2-4 hours)
- Cons: Trust required, large download (50GB+)
### 2. Remote Node (Not Used)
- Connect to existing synced node
- Pros: Instant availability
- Cons: Less privacy, dependency on external service
### 3. Checkpoint Sync (Partially Used)
- Bitcoin: `assumevalid` implemented
- Monero: Built-in checkpoints used automatically
## Monitoring Commands
### Check Sync Progress
```bash
# Bitcoin
sudo docker exec btcpayserver_bitcoind bitcoin-cli getblockchaininfo | grep -E "blocks|progress"
# Monero
sudo docker exec btcpayserver_monerod monerod status
```
### View Sync Speed
```bash
# Bitcoin (blocks per minute)
sudo docker logs btcpayserver_bitcoind --tail 100 | grep UpdateTip
# Monero (blocks per second)
sudo docker logs btcpayserver_monerod --tail 100 | grep Synced
```
## Safety Notes
- `fast:async` mode trades some safety for speed
- After sync completes, mode automatically becomes safer
- Power loss during sync may require resync of recent blocks
- Pruning remains active to limit disk usage
## Rollback if Needed
Backup saved at: `/opt/btcpayserver-docker/docker-compose.override.yml.backup-*`
```bash
sudo cp /opt/btcpayserver-docker/docker-compose.override.yml.backup-* /opt/btcpayserver-docker/docker-compose.override.yml
cd /opt/btcpayserver-docker
sudo docker-compose restart bitcoind monerod
```

161
Hostinger/FINAL_NPM_BTCPAY_CONFIG.md Normal file
View File

@@ -0,0 +1,161 @@
# BTCPay Server with Nginx Proxy Manager - Final Configuration
**Date**: September 16, 2025
## ✅ Successfully Migrated from BTCPay nginx to NPM
### Current Architecture
```
Internet → NPM (80/443) → BTCPay (49392)
↓
SSL Termination
```
## Server Access
- **SSH**: `ssh -p 2255 -i vps_hardening_key sysadmin@thebankofdebbie.giize.com`
- **Password**: Phenom12#. (note the period)
- **Sudo**: Same password
## Service URLs
- **BTCPay Direct**: http://thebankofdebbie.giize.com:8080
- **NPM Admin**: http://thebankofdebbie.giize.com:81
- **BTCPay via NPM**: https://thebankofdebbie.giize.com (after proxy configuration)
## NPM Configuration Required
### 1. Access NPM Admin Panel
- URL: http://thebankofdebbie.giize.com:81
- Default Login: admin@example.com / changeme
- **CHANGE PASSWORD IMMEDIATELY**
### 2. Create Proxy Host
Navigate to Proxy Hosts → Add Proxy Host
**Details Tab:**
- Domain Names: thebankofdebbie.giize.com
- Scheme: http
- Forward IP: 172.20.0.4
- Forward Port: 49392
- Cache Assets: OFF
- Block Common Exploits: ON
- Websockets Support: ON ✅ (Critical for BTCPay)
**SSL Tab:**
- SSL Certificate: Request Let's Encrypt
- Force SSL: ON
- HTTP/2 Support: ON
- HSTS Enabled: ON
- Email: admin@thebankofdebbie.giize.com
**Advanced Tab (if needed):**
```nginx
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;
client_max_body_size 100M;
```
## Docker Container Status
```bash
# Check all services
sudo docker ps
# Current containers:
- nginx-proxy-manager (ports 80,443,81)
- generated_btcpayserver_1 (port 8080→49392)
- generated_nbxplorer_1 (blockchain explorer)
- generated_postgres_1 (database)
- tor (privacy network)
- portainer (management)
```
## BTCPay Environment Configuration
```bash
# /opt/.env
BTCPAY_HOST=thebankofdebbie.giize.com
BTCPAY_CRYPTOS=btc
NBITCOIN_NETWORK=mainnet
BTCPAYGEN_CRYPTO1=btc
BTCPAYGEN_REVERSEPROXY=none # Changed from nginx
BTCPAY_PROTOCOL=http # NPM handles SSL
NOREVERSEPROXY_HTTP_PORT=8080 # Avoid conflict with NPM
```
## Network Configuration
- NPM connected to btcpayserver-docker_default network
- BTCPay IP: 172.20.0.4
- All containers can communicate internally
## Backup Locations
- Configuration backup: `~/btcpay-backup-20250916/`
- Original .env: `/opt/.env.backup`
- Docker compose files: `~/btcpay-backup-20250916/`
## Troubleshooting Commands
### Check BTCPay Logs
```bash
sudo docker logs generated_btcpayserver_1 --tail 50
```
### Check NPM Logs
```bash
sudo docker logs nginx-proxy-manager --tail 50
```
### Restart Services
```bash
# BTCPay
cd /opt/btcpayserver-docker
sudo docker-compose restart
# NPM
sudo docker restart nginx-proxy-manager
```
### Test Connectivity
```bash
# From server
curl -I http://172.20.0.4:49392
curl -I http://localhost:8080
# From outside
curl -I https://thebankofdebbie.giize.com
```
## Monero Integration (TODO)
- Monero plugin needs to be installed in BTCPay
- Wallet already created: 49TnBo2VHbncxvrMFbX5uMS9mtAGkiG1L4N6i7MMz4MhA9AXfyRqBdmf1XrFtGXq2v2G72TNtiVFo2kot5SHnBBz3gwoMj9
- RPC Password: password
## Benefits of NPM over BTCPay nginx
✅ Web-based management interface
✅ Easy SSL certificate management
✅ Multiple domain support
✅ Better logging and monitoring
✅ Access lists and IP filtering
✅ Custom error pages
✅ Stream (TCP/UDP) proxy support
## Next Steps
1. Login to NPM admin panel
2. Change default admin password
3. Create proxy host for thebankofdebbie.giize.com
4. Test BTCPay access through HTTPS
5. Install Monero plugin in BTCPay
6. Configure additional security in NPM (access lists, etc.)
## Security Notes
⚠️ Change NPM admin password immediately
⚠️ Consider IP whitelisting for admin panels
⚠️ Regular backup of NPM configuration
⚠️ Monitor logs for suspicious activity
## Recovery
If issues arise:
1. Backup available at ~/btcpay-backup-20250916/
2. Can restore original nginx setup:
```bash
sudo cp /opt/.env.backup /opt/.env
cd /opt/btcpayserver-docker
. /opt/.env && ./btcpay-setup.sh -i
```

370
Hostinger/FINAL_SECURE_SETUP.md Normal file
View File

@@ -0,0 +1,370 @@
# FINAL SECURE BTCPAY + TOR + MATTERMOST SETUP
## Debian 13 with Maximum Security Configuration
**Deployment Date:** September 10, 2025
**Domain:** thebankofdebbie.giize.com
**Status:** ✅ FULLY OPERATIONAL WITH MAXIMUM SECURITY
---
## 🎉 **DEPLOYMENT COMPLETED SUCCESSFULLY**
### 🔐 **SECURITY STATUS: MAXIMUM**
- ✅ **Debian 13** - Latest hardened OS
- ✅ **SSH Key-only** - No password authentication
- ✅ **Custom SSH Port** - 2255 (not default 22)
- ✅ **No External Services** - All admin services localhost-only
- ✅ **Bitcoin Tor-only** - No clearnet Bitcoin connections
- ✅ **Pruned Bitcoin** - Maximum 10GB storage
### 💾 **STORAGE STATUS: COMPLETELY SAFE**
- **Total VPS**: 394GB SSD
- **Current Usage**: 4.4GB (1% full)
- **Bitcoin Max**: 10GB (pruned + confirmed in logs)
- **Available**: 374GB+
- **Safety Margin**: Massive - no storage concerns
---
## 🌐 **ACCESS INFORMATION**
### **BTCPay Server Access:**
```
Clearnet: https://thebankofdebbie.giize.com
Tor Onion: http://gs76yqhlb4oysidnnswfoigxtwz3kmlmz4ekp2r6knmerpvsjdtbpxyd.onion
```
### **SSH Access (Admin):**
```
ssh -i vps_hardening_key -p 2255 sysadmin@thebankofdebbie.giize.com
```
### **Bitcoin P2P Onion:**
```
p4gve626jjn73ia35ikr7zhnmwknokrzv2eb2gfbqlytlgbckhaeibyd.onion
```
---
## 🤖 **MATTERMOST WEBHOOK INTEGRATION**
### **SECURE SSH TUNNEL METHOD (RECOMMENDED)**
**No External Ports Exposed** - Maximum Security
**Setup SSH Tunnel on Mattermost Server:**
```bash
# Create persistent SSH tunnel (run on Mattermost server)
ssh -N -L 3001:localhost:3001 -p 2255 -i vps_hardening_key sysadmin@thebankofdebbie.giize.com &
# Or use autossh for persistent connection
autossh -N -L 3001:localhost:3001 -p 2255 -i vps_hardening_key sysadmin@thebankofdebbie.giize.com
```
**Mattermost Outgoing Webhook Configuration:**
- **Trigger Word**: `!btcpay`
- **Callback URL**: `http://localhost:3001/webhook/btcpay`
- **Token**: `dr7gz6xwmt8qjg71wxcqjwqz1r`
- **Bot Account**: bankofdebbie
### **Available Commands:**
```
!btcpay - Get onion addresses and status
!btcpay onion - Get onion addresses only
!btcpay status - Get full system status
!btcpay help - Show command help
```
### **Example Response:**
```
## 🧅 BTCPay Server Information
Domain: thebankofdebbie.giize.com
🌐 Clearnet Access:
• https://thebankofdebbie.giize.com
🧅 Tor Hidden Services:
• BTCPay: gs76yqhlb4oysidnnswfoigxtwz3kmlmz4ekp2r6knmerpvsjdtbpxyd.onion
• Bitcoin P2P: p4gve626jjn73ia35ikr7zhnmwknokrzv2eb2gfbqlytlgbckhaeibyd.onion
🔐 Access Methods:
• Tor Browser: http://gs76yqhlb4oysidnnswfoigxtwz3kmlmz4ekp2r6knmerpvsjdtbpxyd.onion
• SSH Tunnel: ssh -L 8080:localhost:80 sysadmin@thebankofdebbie.giize.com
⚡ Integration:
• API Endpoint: https://thebankofdebbie.giize.com/api
• Webhook URL: https://thebankofdebbie.giize.com/webhook
• Onion API: http://gs76yqhlb4oysidnnswfoigxtwz3kmlmz4ekp2r6knmerpvsjdtbpxyd.onion/api
🔒 Security Status: ✅ Tor-enabled, Pruned Bitcoin, Hardened Debian 13
```
---
## 🔒 **SECURITY ARCHITECTURE**
### **Network Security:**
```
Internet → BTCPay HTTPS (443) → nginx → BTCPay Server
SSH Tunnel (2255) → localhost:3001 → Webhook
Tor Network → Onion Services → Bitcoin/BTCPay
```
### **Access Control:**
- **Public**: BTCPay web interface (HTTPS only)
- **Admin**: SSH tunnel access only
- **Webhook**: SSH tunnel only (no external access)
- **Bitcoin**: Tor network only (no clearnet)
### **Exposed Ports (External):**
```
2255/tcp - SSH (key authentication only)
80/tcp - HTTP (redirects to HTTPS)
443/tcp - HTTPS (BTCPay web interface)
```
### **Internal Services (Localhost Only):**
```
3001/tcp - Mattermost webhook (SSH tunnel access only)
5432/tcp - PostgreSQL (Docker internal)
9050/tcp - Tor SOCKS proxy (Docker internal)
```
---
## 📊 **SERVICE STATUS**
### **Docker Containers (8 Running):**
```
✅ btcpayserver_bitcoind - Bitcoin Core (pruned, Tor-only)
✅ generated_btcpayserver_1 - BTCPay Server application
✅ generated_nbxplorer_1 - Blockchain explorer
✅ generated_postgres_1 - PostgreSQL database
✅ nginx - Reverse proxy + SSL
✅ tor - Tor daemon + onion services
✅ tor-gen - Tor configuration generator
✅ letsencrypt-nginx-proxy-companion - SSL certificate automation
```
### **Additional Services:**
```
✅ mattermost_btcpay_webhook.js - Webhook API (Node.js)
✅ WireGuard - VPN server (installed, ready if needed)
```
---
## 🔧 **MAINTENANCE & MONITORING**
### **System Health Commands:**
```bash
# SSH access
ssh -i vps_hardening_key -p 2255 sysadmin@thebankofdebbie.giize.com
# Check all containers
docker ps --format "table {{.Names}}\t{{.Status}}"
# Bitcoin sync status
docker exec btcpayserver_bitcoind bitcoin-cli getblockchaininfo
# Bitcoin pruning verification
docker logs btcpayserver_bitcoind | grep -i prune
# Disk usage monitoring
df -h /
# Webhook status
curl http://localhost:3001/health
```
### **BTCPay Management:**
```bash
btcpay-restart.sh # Restart all BTCPay services
btcpay-update.sh # Update BTCPay to latest version
btcpay-clean.sh # Clean old Docker images
btcpay-down.sh # Stop all services
btcpay-up.sh # Start all services
```
### **Security Monitoring:**
```bash
# Check firewall status
sudo iptables -L
sudo systemctl status fail2ban
# Monitor SSH attempts
sudo journalctl -u ssh -f
# Check for unauthorized access
sudo last
```
---
## 🛠️ **LITTLESHOP INTEGRATION**
### **API Endpoints:**
```
Production: https://thebankofdebbie.giize.com/api
Tor Access: http://gs76yqhlb4oysidnnswfoigxtwz3kmlmz4ekp2r6knmerpvsjdtbpxyd.onion/api
```
### **Webhook Configuration:**
```
Invoice Created: https://thebankofdebbie.giize.com/webhook/littleshop
Payment Confirmed: https://thebankofdebbie.giize.com/webhook/payment
```
### **For Maximum Privacy:**
Configure LittleShop to use the Tor onion API endpoint for all Bitcoin operations.
---
## 🚨 **BACKUP & RECOVERY**
### **Critical Data Locations:**
```bash
# BTCPay Database
/var/lib/docker/volumes/generated_postgres_*
# Bitcoin Wallet & Settings
/var/lib/docker/volumes/generated_bitcoin_*
# Tor Hidden Service Keys
/var/lib/docker/volumes/generated_tor_*
# Configuration Files
/opt/.env
/opt/btcpayserver-docker/Generated/docker-compose.generated.yml
```
### **Backup Command:**
```bash
sudo tar -czf btcpay-backup-$(date +%Y%m%d).tar.gz \
/var/lib/docker/volumes/generated_* \
/opt/.env \
/opt/btcpayserver-docker/ \
/home/sysadmin/mattermost-webhook/
```
### **Restore Process:**
```bash
sudo btcpay-down.sh
sudo tar -xzf btcpay-backup-YYYYMMDD.tar.gz -C /
sudo btcpay-up.sh
cd ~/mattermost-webhook && npm start
```
---
## 📞 **TROUBLESHOOTING**
### **Common Issues:**
**1. Webhook SSL Error in Mattermost:**
```bash
# Solution: Use SSH tunnel
ssh -N -L 3001:localhost:3001 -p 2255 -i vps_hardening_key sysadmin@thebankofdebbie.giize.com &
# Then configure Mattermost webhook URL as: http://localhost:3001/webhook/btcpay
```
**2. Bitcoin Sync Slow:**
```bash
# Normal over Tor - check progress:
docker logs btcpayserver_bitcoind | tail -20
```
**3. Onion Services Not Accessible:**
```bash
# Restart Tor containers:
docker restart tor tor-gen
# Wait 5 minutes for new addresses
```
**4. Storage Issues:**
```bash
# Check Bitcoin pruning is working:
docker logs btcpayserver_bitcoind | grep -i prune
# Should show: "Prune configured to target 10000 MiB"
```
---
## 🎯 **PRODUCTION READINESS CHECKLIST**
**✅ Security:**
- [ ] SSH key-only authentication tested
- [ ] All unnecessary ports closed
- [ ] Webhook accessible only via SSH tunnel
- [ ] Bitcoin traffic only via Tor
- [ ] SSL certificates active for domain
**✅ Functionality:**
- [ ] BTCPay web interface accessible
- [ ] Bitcoin node syncing (pruned mode confirmed)
- [ ] Onion addresses generated and accessible
- [ ] Mattermost bot responding to !btcpay commands
- [ ] Webhook returning onion addresses
**✅ Storage:**
- [ ] Bitcoin pruning active (confirmed in logs)
- [ ] Disk usage under 10GB total
- [ ] 370GB+ available space remaining
- [ ] Automated monitoring in place
**✅ Integration:**
- [ ] API endpoints responding
- [ ] LittleShop can connect to BTCPay API
- [ ] Payment processing tested
- [ ] Webhook notifications working
---
## 🚀 **NEXT STEPS**
### **Immediate (Today):**
1. **Set up SSH tunnel** from Mattermost server to VPS
2. **Test !btcpay command** in Mattermost
3. **Complete BTCPay setup wizard** (create admin account)
4. **Configure first store** in BTCPay
### **Within 24 Hours:**
1. **Wait for Bitcoin initial sync** to complete
2. **Test payment processing** with small amount
3. **Integrate LittleShop API** with BTCPay
4. **Test complete order flow**
### **Ongoing:**
1. **Monitor Bitcoin sync progress** daily
2. **Backup configuration** weekly
3. **Update BTCPay** monthly
4. **Security audit** quarterly
---
## 🏆 **ACHIEVEMENT UNLOCKED**
**You now have:**
- 🔒 **Maximum Security**: Hardened Debian 13, Tor-only Bitcoin, SSH tunnel access
- 🧅 **Complete Privacy**: All Bitcoin traffic via Tor, customer anonymity
- 💾 **Storage Safety**: Pruned Bitcoin (10GB max), 394GB VPS safe
- 🤖 **Team Integration**: Mattermost bot for easy onion address retrieval
- ⚡ **Production Ready**: Full Bitcoin payment processing capability
**This is an enterprise-grade, privacy-focused Bitcoin payment infrastructure!** 🎉
---
**Final SSH Tunnel Command for Mattermost:**
```bash
ssh -N -L 3001:localhost:3001 -p 2255 -i vps_hardening_key sysadmin@thebankofdebbie.giize.com
```
**Then configure Mattermost webhook URL as:**
```
http://localhost:3001/webhook/btcpay
```
**Ready to process secure, anonymous Bitcoin payments!** 🚀

151
Hostinger/FIX_VIA_CONSOLE.md Normal file
View File

@@ -0,0 +1,151 @@
# Fix BTCPay via Hostinger Console Access
Since SSH access isn't working, use the Hostinger web console:
## Step 1: Access Hostinger Console
1. Go to https://hpanel.hostinger.com/
2. Login to your Hostinger account
3. Find VPS server: srv1002428.hstgr.cloud
4. Click on the server
5. Look for "Console" or "VNC Console" or "Browser Terminal"
6. Click to open web-based terminal
## Step 2: Login via Console
```
Username: ubuntu
Password: (the one you set during hardening)
OR if that doesn't work:
Username: root
Password: Th3fa1r13sd1d1t.
```
## Step 3: Diagnose the Issue
Run these commands to see what's wrong:
```bash
# Become root if logged in as ubuntu
sudo su -
# Check container status
docker ps -a | grep -E "btcpay|nginx|postgres"
# Look for stopped containers
docker ps -a | grep Exited
```
## Step 4: Fix Based on What You Find
### If BTCPay container is "Exited":
```bash
# Start it
docker start generated_btcpayserver_1
# Check logs for why it crashed
docker logs generated_btcpayserver_1 --tail 100
```
### If Postgres is "Exited":
```bash
# Start database first
docker start generated_postgres_1
# Wait 10 seconds
sleep 10
# Then start BTCPay
docker start generated_btcpayserver_1
```
### If all containers are running but still 502:
```bash
# Full restart
cd /opt/btcpayserver-docker
./btcpay-restart.sh
# Wait 2 minutes for services to fully start
sleep 120
# Check status
docker ps
```
### If containers keep crashing:
```bash
# Check disk space
df -h /
# If disk is full (>90%):
docker system prune -a --volumes
# WARNING: Type 'y' carefully - this removes unused data
# Check memory
free -h
# If memory is low (<500MB free):
systemctl restart docker
```
## Step 5: Nuclear Option - Rebuild
If nothing works:
```bash
# Stop everything
cd /opt/btcpayserver-docker
docker-compose down
# Restart with fresh build
source /opt/.env
./btcpay-setup.sh -i
```
## Step 6: Monitor the Fix
```bash
# Watch containers starting
watch docker ps
# In another console tab, monitor logs
docker logs -f generated_btcpayserver_1
```
## What to Look For in Logs
**Good signs:**
- "BTCPay Server started"
- "Listening on port"
- "Connected to NBXplorer"
**Bad signs:**
- "Cannot connect to database"
- "Port already in use"
- "Out of memory"
- "No space left on device"
## If Database is Corrupted
```bash
# Last resort - reset database (loses data!)
docker-compose down
docker volume rm generated_postgres_datadir
./btcpay-setup.sh -i
```
## Re-enable SSH Access
While in console, fix SSH:
```bash
# Re-add your SSH key for ubuntu user
mkdir -p /home/ubuntu/.ssh
echo "ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIDoUnUn5wsJyelx5NAzP1lrcTBKAV93m8R1hlR0ZU07Z vps-hardening-20250910" > /home/ubuntu/.ssh/authorized_keys
chown -R ubuntu:ubuntu /home/ubuntu/.ssh
chmod 700 /home/ubuntu/.ssh
chmod 600 /home/ubuntu/.ssh/authorized_keys
# Restart SSH
systemctl restart sshd
```
Then test from your local machine:
```bash
ssh -p 2255 -i vps_hardening_key ubuntu@thebankofdebbie.giize.com
```

248
Hostinger/Infrastructure.txt Normal file
View File

@@ -0,0 +1,248 @@
================================================================================
LITTLESHOP HOSTINGER VPS INFRASTRUCTURE
================================================================================
Last Updated: September 12, 2025
Status: BTCPAY SERVER MULTI-CRYPTO OPERATIONAL ✅
================================================================================
SERVER INFORMATION
================================================================================
🖥️ SERVER DETAILS:
Provider: Hostinger
Hostname: srv1002428.hstgr.cloud / thebankofdebbie.giize.com
IP Address: 31.97.57.205
Operating System: Debian 13 (upgraded from Ubuntu 24.04)
CPU: x86_64 architecture
RAM: 16GB
Storage: 394GB SSD (✅ SUFFICIENT with Bitcoin pruning enabled)
🔐 ACCESS CREDENTIALS:
SSH Port: 2255 (changed from default 22 for security)
SSH User: sysadmin (root login DISABLED, ubuntu user not present)
SSH Key: vps_hardening_key (stored in this directory)
Sudo Password: Phenom12#. (same as SSH user password)
🌐 DOKPLOY ADMIN:
Original Credentials: sysadmin@server.local / Th3fa1r13sd1d1t.
Web Interface: http://srv1002428.hstgr.cloud:3000 (BLOCKED externally)
Secure Access: SSH tunnel required (see commands below)
================================================================================
SECURITY CONFIGURATION
================================================================================
🔒 SSH HARDENING STATUS:
✅ Port changed: 22 → 2255
✅ Root login: DISABLED
✅ SSH key authentication: CONFIGURED
✅ Password authentication: ENABLED (for safety - disable after testing)
✅ Max auth attempts: 3
✅ Login grace time: 30 seconds
✅ SSH banner: Security warning configured
✅ Strong encryption: AES-256, ChaCha20-Poly1305
🛡️ FIREWALL (UFW) STATUS:
✅ Status: ACTIVE and enabled on startup
✅ SSH (2255/tcp): ALLOWED with comment "SSH-Hardened"
✅ HTTP (80/tcp): ALLOWED with comment "HTTP-Dokploy"
✅ HTTPS (443/tcp): ALLOWED with comment "HTTPS-Dokploy"
✅ Dokploy (3000/tcp): DENIED with comment "Block-Dokploy-External"
✅ Default policy: DENY all other incoming traffic
🚨 FAIL2BAN PROTECTION:
✅ Status: ACTIVE with 2 jails
✅ SSH jail: 3 attempts → 2 hour ban
✅ Nginx jails: HTTP auth, bad bots, noscript protection
✅ Ban time: 1 hour (SSH: 2 hours)
✅ Find time: 10 minutes
✅ Monitoring: Auth logs and web access attempts
🔧 SYSTEM SECURITY:
✅ Automatic security updates: ENABLED
✅ Non-root sudo user: ubuntu user configured
✅ Package security: Latest security packages installed
✅ Docker access: Ubuntu user added to docker group
================================================================================
DOCKER SERVICES
================================================================================
🪙 BTCPAY SERVER (September 12, 2025):
✅ btcpayserver_bitcoind: Bitcoin Core (PRUNED 10GB, Tor-only)
✅ btcpayserver_dogecoind: Dogecoin daemon
✅ btcpayserver_monerod: Monero daemon
⚠️ btcpayserver_monero_wallet: Monero wallet (restarting - config issue)
⚠️ generated-zcash_walletd-1: Zcash wallet (restarting - needs daemon)
✅ generated_btcpayserver_1: BTCPay Server application
✅ generated_nbxplorer_1: Blockchain explorer
✅ generated_postgres_1: PostgreSQL database
✅ nginx: Reverse proxy with SSL
✅ tor: Tor daemon + onion services
✅ tor-gen: Tor configuration generator
✅ letsencrypt-nginx-proxy-companion: SSL certificate manager
🌐 BTCPAY ACCESS:
Clearnet: https://thebankofdebbie.giize.com
Tor Onion: njoc2ubkk7ymgqfg6plt3wcltvcvuv3j4eemixnovicegrlwhq2zwfad.onion (expected)
Bitcoin P2P Onion: s7n55wptvooma4gqsbdo5vn6v6nphjffqsmlufoa3fzqhwkqgeasslad.onion (expected)
🪙 CRYPTOCURRENCY STATUS:
✅ Bitcoin (BTC): Pruned mode (10GB max), Tor-only, fully operational
✅ Dogecoin (DOGE): Running (needs pruning configuration)
✅ Monero (XMR): Daemon operational, wallet setup in progress
⚠️ Ethereum (ETH): Configured in BTCPay but container missing
⚠️ Zcash (ZEC): Wallet present, main daemon needs configuration
🔧 CRITICAL CONFIGURATION FIX:
Problem: BTCPay Docker Compose YAML parsing broken for BITCOIN_EXTRA_ARGS
Solution: docker-compose.override.yml file (UPDATE-SAFE)
Location: /opt/btcpayserver-docker/docker-compose.override.yml
Status: Bitcoin pruning working via override file approach
🐳 LEGACY DOKPLOY CONTAINERS (if present):
✅ dokploy: Main application (port 3000 - blocked externally)
✅ dokploy-redis: Redis database (internal port 6379)
✅ dokploy-postgres: PostgreSQL database (internal port 5432)
✅ dokploy-traefik: Reverse proxy (ports 80, 443 - both protocols)
🔗 SERVICE STATUS:
BTCPay Services: 12 containers running, Bitcoin with proper pruning
Cryptocurrency Sync: In progress over Tor network
Disk Usage: 63GB used / 316GB available (safe with pruning)
================================================================================
STORAGE ANALYSIS
================================================================================
💾 CURRENT STORAGE:
Total Space: 387GB SSD
Used Space: 8.8GB (3% utilization)
Available: 378GB
Docker Data: 9.2GB
⚠️ BITCOIN NODE STORAGE REQUIREMENTS:
Current Blockchain: ~800GB (2025)
Annual Growth: 100-150GB
Recommended: 1TB+ SSD for full node
Status: CURRENT STORAGE INSUFFICIENT
📈 STORAGE OPTIONS:
1. Upgrade VPS to 1TB+ storage (RECOMMENDED)
2. Use Bitcoin pruned node (~10GB, limited functionality)
3. Add external storage solution
4. Use different VPS provider with larger storage
================================================================================
ACCESS COMMANDS
================================================================================
🔑 SSH ACCESS (SECURE):
ssh -i vps_hardening_key -p 2255 ubuntu@srv1002428.hstgr.cloud
🌐 DOKPLOY ADMIN ACCESS (via SSH tunnel):
ssh -i vps_hardening_key -p 2255 -L 3000:localhost:3000 ubuntu@srv1002428.hstgr.cloud
Then browse to: http://localhost:3000
🔍 SYSTEM MONITORING:
# Check firewall status
sudo ufw status numbered
# Check Fail2Ban status
sudo fail2ban-client status
# Check SSH security
sudo ss -tlnp | grep :2255
# Check Docker containers
docker ps
# Check system resources
df -h && free -h
🚨 EMERGENCY ACCESS:
If SSH keys fail, password authentication is still enabled:
ssh -p 2255 ubuntu@srv1002428.hstgr.cloud
Password: Th3fa1r13sd1d1t.
================================================================================
NEXT STEPS / TODO
================================================================================
🔄 IMMEDIATE ACTIONS:
1. Test SSH key access thoroughly from multiple locations
2. Once SSH keys proven reliable, disable password authentication:
Edit /etc/ssh/sshd_config: PasswordAuthentication no
3. Restart SSH service: sudo systemctl restart ssh
📦 BITCOIN/BTCPAY DEPLOYMENT:
1. ⚠️ CRITICAL: Upgrade storage to 1TB+ before Bitcoin node installation
2. Install Bitcoin Core for full node operation
3. Deploy BTCPay Server via Docker/Dokploy
4. Configure Lightning Network (if required)
5. Set up automated backups for Bitcoin/BTCPay data
🔐 SECURITY ENHANCEMENTS:
1. Configure email notifications for Fail2Ban alerts
2. Set up log monitoring and alerting
3. Implement automated backup verification
4. Configure VPN access for additional admin security (optional)
📊 MONITORING SETUP:
1. Configure disk space alerts (critical for Bitcoin node)
2. Set up service health monitoring
3. Implement performance monitoring
4. Configure backup success/failure notifications
================================================================================
SECURITY VERIFICATION
================================================================================
✅ HARDENING CHECKLIST COMPLETED:
[✅] System packages updated and automatic updates enabled
[✅] Non-root sudo user created (ubuntu)
[✅] SSH port changed from 22 to 2255
[✅] SSH key authentication configured and tested
[✅] Root login disabled
[✅] UFW firewall enabled with secure rules
[✅] Fail2Ban installed and configured
[✅] Dokploy admin interface secured (external access blocked)
[✅] SSH banner with security warning added
[✅] Strong SSH encryption ciphers configured
[✅] Docker access configured for ubuntu user
[✅] All unnecessary services removed/disabled
🔒 SECURITY POSTURE: EXCELLENT
Your VPS is now hardened against common attack vectors and ready for
production Bitcoin/BTCPay deployment once storage is upgraded.
================================================================================
SUPPORT CONTACTS
================================================================================
🏢 HOSTINGER SUPPORT:
Website: https://www.hostinger.com/contact
VPS Management: Hostinger Panel
Server ID: srv1002428
📧 EMERGENCY CONTACTS:
If locked out of server, contact Hostinger support with:
- Server hostname: srv1002428.hstgr.cloud
- Account credentials for VPS management panel
- Request console access or password reset
================================================================================
CHANGE LOG
================================================================================
2025-09-10: Initial VPS hardening completed
- SSH security hardening (port 2255, key auth, root disabled)
- UFW firewall configuration with secure rules
- Fail2Ban intrusion prevention system
- Dokploy security (blocked external access to port 3000)
- System updates and automatic update configuration
- Comprehensive security verification completed
================================================================================
END OF INFRASTRUCTURE DOCUMENT
================================================================================

270
Hostinger/MATTERMOST_LOCAL_SETUP.md Normal file
View File

@@ -0,0 +1,270 @@
# MATTERMOST LOCAL API SETUP
## SSH-based BTCPay Onion Address Retrieval
**Purpose:** Run a local web API on your Mattermost server that executes SSH commands to retrieve BTCPay onion addresses
**Method:** Mattermost Slash Command → Local API → SSH to VPS → Return Results
**Security:** No external ports exposed on VPS, SSH key authentication only
---
## 🚀 **SETUP ON YOUR MATTERMOST SERVER**
### **Step 1: Install Dependencies**
```bash
# On your Mattermost server
mkdir ~/btcpay-api
cd ~/btcpay-api
# Copy the local API script
# (Copy mattermost_local_api.js to this directory)
# Install Node.js if not installed
curl -fsSL https://deb.nodesource.com/setup_lts.x | sudo bash -
sudo apt-get install -y nodejs npm
# Install Express
npm init -y
npm install express
```
### **Step 2: Configure SSH Access**
```bash
# Copy your VPS SSH key to Mattermost server
# (Copy vps_hardening_key to your Mattermost server)
# Set correct permissions
chmod 600 ~/btcpay-api/vps_hardening_key
# Test SSH access to VPS
ssh -i ~/btcpay-api/vps_hardening_key -p 2255 sysadmin@thebankofdebbie.giize.com "echo 'SSH test successful'"
```
### **Step 3: Update Configuration**
```javascript
// Edit mattermost_local_api.js
const config = {
vps_domain: 'thebankofdebbie.giize.com',
vps_port: 2255,
vps_user: 'sysadmin',
ssh_key_path: '/home/your-user/btcpay-api/vps_hardening_key', // UPDATE THIS
mattermost_token: 'dr7gz6xwmt8qjg71wxcqjwqz1r',
allowed_users: ['bankofdebbie', 'admin', 'sysadmin'] // ADD YOUR USERS
};
```
### **Step 4: Start the Local API**
```bash
cd ~/btcpay-api
node mattermost_local_api.js
# Or run as service
nohup node mattermost_local_api.js > api.log 2>&1 &
```
**Expected Output:**
```
🚀 Mattermost BTCPay Local API running on localhost:3333
🎯 Target VPS: thebankofdebbie.giize.com:2255
🔑 Method: SSH-based command execution
💡 Endpoints:
POST /btcpay - Mattermost slash command handler
GET /test - Test SSH connectivity
GET /health - Health check
🔧 Mattermost Slash Command Setup:
Command: /btcpay
URL: http://localhost:3333/btcpay
Token: dr7gz6xwmt8qjg71wxcqjwqz1r
Method: POST
```
---
## 📱 **MATTERMOST SLASH COMMAND CONFIGURATION**
### **Create Slash Command in Mattermost:**
1. **Go to:** System Console → Integrations → Slash Commands
2. **Click:** Add Slash Command
3. **Configure:**
- **Title:** BTCPay Server Info
- **Command Trigger Word:** `btcpay`
- **Request URL:** `http://localhost:3333/btcpay`
- **Request Method:** POST
- **Response Username:** BTCPay Bot
- **Response Icon:** 🧅 (optional)
- **Autocomplete:** Yes
- **Autocomplete Description:** Get BTCPay Server onion addresses
### **Usage in Mattermost:**
```
/btcpay - Get onion addresses
/btcpay onion - Get onion addresses
/btcpay status - Get full system status
/btcpay help - Show available commands
```
---
## 🧅 **EXAMPLE RESPONSES**
### **`/btcpay` or `/btcpay onion`:**
```
## 🧅 BTCPay Tor Onion Addresses
🌐 Domain: https://thebankofdebbie.giize.com
🧅 Tor Hidden Services:
• BTCPay Server: gs76yqhlb4oysidnnswfoigxtwz3kmlmz4ekp2r6knmerpvsjdtbpxyd.onion
• Bitcoin P2P: p4gve626jjn73ia35ikr7zhnmwknokrzv2eb2gfbqlytlgbckhaeibyd.onion
🔐 Access Methods:
• Clearnet: https://thebankofdebbie.giize.com
• Tor Browser: http://gs76yqhlb4oysidnnswfoigxtwz3kmlmz4ekp2r6knmerpvsjdtbpxyd.onion
⚡ API Endpoints:
• REST API: https://thebankofdebbie.giize.com/api
• Tor API: http://gs76yqhlb4oysidnnswfoigxtwz3kmlmz4ekp2r6knmerpvsjdtbpxyd.onion/api
📅 Retrieved: 2025-09-10 17:20:15
👤 Requested by: bankofdebbie
```
### **`/btcpay status`:**
```
## 📊 BTCPay Server Status Report
🌐 Domain: https://thebankofdebbie.giize.com
🧅 Tor Onion Services:
• BTCPay: gs76yqhlb4oysidnnswfoigxtwz3kmlmz4ekp2r6knmerpvsjdtbpxyd.onion
• Bitcoin P2P: p4gve626jjn73ia35ikr7zhnmwknokrzv2eb2gfbqlytlgbckhaeibyd.onion
📊 System Health:
• Containers: 8 containers running
• Storage: 4.5G used / 394G total
• Bitcoin: 10000 MiB max storage
🔒 Security: Tor-only Bitcoin, Hardened Debian 13
📅 Retrieved: 2025-09-10 17:20:15
👤 Requested by: bankofdebbie
```
---
## 🔧 **SYSTEMD SERVICE (OPTIONAL)**
### **Create Service File:**
```bash
sudo tee /etc/systemd/system/btcpay-api.service << 'EOF'
[Unit]
Description=BTCPay Mattermost Local API
After=network.target
[Service]
Type=simple
User=your-username
WorkingDirectory=/home/your-username/btcpay-api
ExecStart=/usr/bin/node mattermost_local_api.js
Restart=always
RestartSec=10
Environment=NODE_ENV=production
[Install]
WantedBy=multi-user.target
EOF
# Enable and start
sudo systemctl enable btcpay-api
sudo systemctl start btcpay-api
sudo systemctl status btcpay-api
```
---
## 🔍 **TESTING**
### **Test SSH Connectivity:**
```bash
curl http://localhost:3333/test
```
### **Test Health Check:**
```bash
curl http://localhost:3333/health
```
### **Test Mattermost Webhook:**
```bash
curl -X POST http://localhost:3333/btcpay \
-H "Content-Type: application/json" \
-d '{
"token": "dr7gz6xwmt8qjg71wxcqjwqz1r",
"user_name": "bankofdebbie",
"text": "onion"
}'
```
---
## 🚨 **TROUBLESHOOTING**
### **Common Issues:**
**1. SSH Connection Failed:**
- Check SSH key path in config
- Verify SSH key permissions (600)
- Test manual SSH: `ssh -i path/to/key -p 2255 sysadmin@thebankofdebbie.giize.com`
**2. "Permission Denied" for sudo:**
- VPS sysadmin user needs passwordless sudo for reading onion files
- Or modify commands to not use sudo
**3. "Command Timeout":**
- VPS might be under load
- Increase timeout in executeSSHCommand function
**4. "Invalid Token":**
- Check Mattermost slash command token matches config
---
## 🔒 **SECURITY NOTES**
**✅ Secure Design:**
- API runs on localhost only (127.0.0.1)
- Uses SSH key authentication to VPS
- No persistent connections
- Token-based Mattermost authentication
- User authorization checks
**📝 Security Checklist:**
- [ ] SSH key has correct permissions (600)
- [ ] API runs on localhost only
- [ ] Authorized users configured in config
- [ ] VPS SSH key access tested
- [ ] Mattermost token configured correctly
---
## 📋 **SETUP SUMMARY**
**🏗️ Architecture:**
```
Mattermost → Slash Command → Local API (localhost:3333) → SSH → VPS → Return Data
```
**🔐 Security:**
- No external VPS ports exposed for webhook
- SSH key authentication only
- Localhost API binding
- Token validation
- User authorization
**⚡ Usage:**
- Simple `/btcpay` command in Mattermost
- Instant onion address retrieval
- Full system status on demand
- No persistent connections needed
**🎯 Ready to deploy on your Mattermost server!**

125
Hostinger/MATTERMOST_QUICK_SETUP.txt Normal file
View File

@@ -0,0 +1,125 @@
================================================================================
MATTERMOST LOCAL API - QUICK SETUP GUIDE
================================================================================
🎯 **SIMPLE SSH-BASED SOLUTION**
Instead of complex web routing, this runs a LOCAL API on your Mattermost server
that uses SSH to retrieve onion addresses from the VPS.
================================================================================
SETUP STEPS
================================================================================
📦 **1. ON YOUR MATTERMOST SERVER:**
mkdir ~/btcpay-api
cd ~/btcpay-api
# Copy files (adjust paths for your environment):
cp /path/to/mattermost_local_api.js ./
cp /path/to/mattermost-local-package.json ./package.json
cp /path/to/vps_hardening_key ./
# Install dependencies:
npm install
# Fix SSH key permissions:
chmod 600 ./vps_hardening_key
🔧 **2. UPDATE CONFIGURATION:**
Edit mattermost_local_api.js and update:
ssh_key_path: '/home/your-user/btcpay-api/vps_hardening_key'
🚀 **3. START THE API:**
node mattermost_local_api.js
📱 **4. CONFIGURE MATTERMOST SLASH COMMAND:**
System Console → Integrations → Slash Commands → Add Slash Command:
Command: /btcpay
URL: http://localhost:3333/btcpay
Method: POST
Token: dr7gz6xwmt8qjg71wxcqjwqz1r
================================================================================
USAGE
================================================================================
💬 **IN MATTERMOST:**
/btcpay → Get onion addresses
/btcpay status → Get system status
/btcpay help → Show commands
📤 **EXAMPLE RESPONSE:**
## 🧅 BTCPay Tor Onion Addresses
🌐 Domain: https://thebankofdebbie.giize.com
🧅 Tor Hidden Services:
• BTCPay Server: gs76yqhlb4oysidnnswfoigxtwz3kmlmz4ekp2r6knmerpvsjdtbpxyd.onion
• Bitcoin P2P: p4gve626jjn73ia35ikr7zhnmwknokrzv2eb2gfbqlytlgbckhaeibyd.onion
🔐 Access Methods:
• Clearnet: https://thebankofdebbie.giize.com
• Tor Browser: http://gs76yqhlb4oysidnnswfoigxtwz3kmlmz4ekp2r6knmerpvsjdtbpxyd.onion
📅 Retrieved: 2025-09-10 17:25:30
👤 Requested by: bankofdebbie
================================================================================
SECURITY
================================================================================
✅ **SECURE DESIGN:**
- Local API only (localhost:3333)
- SSH key authentication to VPS
- No VPS ports exposed for webhook
- Token validation for Mattermost
- On-demand connections only
❌ **NO PERSISTENT CONNECTIONS:**
- No permanent SSH tunnels
- No exposed VPS webhook ports
- No authentication issues
- Clean, simple architecture
================================================================================
TESTING
================================================================================
🧪 **TEST COMMANDS:**
# Test SSH connectivity:
curl http://localhost:3333/test
# Test health:
curl http://localhost:3333/health
# Test Mattermost webhook:
curl -X POST http://localhost:3333/btcpay -H "Content-Type: application/json" -d '{"token":"dr7gz6xwmt8qjg71wxcqjwqz1r","user_name":"bankofdebbie","text":"onion"}'
================================================================================
FINAL RESULT
================================================================================
🎯 **PERFECT SOLUTION:**
- No complex nginx routing
- No VPS web services
- No authentication issues
- Simple SSH-based retrieval
- Secure localhost-only API
- Clean Mattermost integration
🚀 **READY TO USE!**
Your BTCPay Server with Tor is fully operational.
Your Mattermost bot can now retrieve onion addresses securely via SSH.
No exposed ports, maximum security maintained.
================================================================================

278
Hostinger/MATTERMOST_WEBHOOK_SETUP.md Normal file
View File

@@ -0,0 +1,278 @@
# MATTERMOST BTCPAY WEBHOOK SETUP
## Retrieve BTCPay Server Onion Addresses via Mattermost
**Domain:** thebankofdebbie.giize.com
**Created:** September 10, 2025
**Purpose:** Get BTCPay Server and Bitcoin onion addresses in Mattermost
---
## 🚀 **QUICK SETUP**
### Step 1: Install Node.js Dependencies
```bash
# On your BTCPay server
ssh -i vps_hardening_key -p 2255 ubuntu@thebankofdebbie.giize.com
cd ~
mkdir mattermost-webhook
cd mattermost-webhook
# Copy webhook script
scp -i ../vps_hardening_key -P 2255 mattermost_btcpay_webhook.js ubuntu@thebankofdebbie.giize.com:~/mattermost-webhook/
# Install Node.js if not present
curl -fsSL https://deb.nodesource.com/setup_lts.x | sudo -E bash -
sudo apt-get install -y nodejs
# Install dependencies
npm init -y
npm install express
```
### Step 2: Configure Environment Variables
```bash
# Create environment file
cat > .env << 'EOF'
MATTERMOST_TOKEN=your-mattermost-outgoing-webhook-token
WEBHOOK_SECRET=your-webhook-secret-key
PORT=3001
EOF
# Set permissions
chmod 600 .env
```
### Step 3: Create Systemd Service
```bash
# Create systemd service file
sudo tee /etc/systemd/system/btcpay-webhook.service << 'EOF'
[Unit]
Description=BTCPay Mattermost Webhook Service
After=network.target docker.service
Requires=docker.service
[Service]
Type=simple
User=ubuntu
WorkingDirectory=/home/ubuntu/mattermost-webhook
ExecStart=/usr/bin/node mattermost_btcpay_webhook.js
Restart=always
RestartSec=10
Environment=NODE_ENV=production
[Install]
WantedBy=multi-user.target
EOF
# Enable and start service
sudo systemctl enable btcpay-webhook
sudo systemctl start btcpay-webhook
sudo systemctl status btcpay-webhook
```
### Step 4: Configure UFW Firewall
```bash
# Allow webhook port (local only)
sudo ufw allow from 127.0.0.0/8 to any port 3001 comment "BTCPay-Webhook-Local"
# Check status
sudo ufw status numbered
```
---
## 📡 **MATTERMOST CONFIGURATION**
### Step 1: Create Outgoing Webhook in Mattermost
1. Go to **System Console** → **Integrations** → **Outgoing Webhooks**
2. Click **Add Outgoing Webhook**
3. Configure:
- **Title:** BTCPay Server Info
- **Channel:** Your desired channel (or leave blank for any channel)
- **Trigger Words:** `!btcpay`
- **Callback URLs:** `http://thebankofdebbie.giize.com:3001/webhook/btcpay`
- **Token:** Copy the generated token for your `.env` file
### Step 2: Update Environment Variables
```bash
# Update with actual Mattermost token
nano ~/mattermost-webhook/.env
# Set the token you got from Mattermost
MATTERMOST_TOKEN=abc123def456ghi789
WEBHOOK_SECRET=your-secret-key-here
PORT=3001
# Restart service
sudo systemctl restart btcpay-webhook
```
---
## 🧅 **USAGE IN MATTERMOST**
### Available Commands:
- `!btcpay` - Get onion addresses
- `!btcpay onion` - Get onion addresses
- `!btcpay status` - Get system status
- `!btcpay help` - Show help
### Example Output:
```
## 🧅 BTCPay Server Information
Domain: thebankofdebbie.giize.com
🌐 Clearnet Access:
• https://thebankofdebbie.giize.com
🧅 Tor Hidden Services:
• BTCPay: abc123def456ghi789klmnopqrstuvwxyz123456789.onion
• Bitcoin P2P: xyz987uvw654tsr321opnmlkjihgfedcba987654321.onion
🔐 Access Methods:
• Tor Browser: http://abc123...onion
• SSH Tunnel: ssh -L 8080:localhost:80 ubuntu@thebankofdebbie.giize.com
⚡ Integration:
• API Endpoint: https://thebankofdebbie.giize.com/api
• Webhook URL: https://thebankofdebbie.giize.com/webhook
• Onion API: http://abc123...onion/api
🔒 Security Status: ✅ Tor-enabled, Pruned Bitcoin, Hardened VPS
📅 Updated: 2025-09-10 14:30:15
👤 Requested by: admin
```
---
## 🔧 **ADVANCED CONFIGURATION**
### Reverse Proxy Setup (Optional)
If you want to expose the webhook via HTTPS:
```bash
# Add to nginx config for thebankofdebbie.giize.com
sudo tee -a /etc/nginx/sites-available/default << 'EOF'
location /webhook/btcpay {
proxy_pass http://localhost:3001/webhook/btcpay;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_cache_bypass $http_upgrade;
}
EOF
# Test and reload nginx
sudo nginx -t
sudo systemctl reload nginx
```
### Security Enhancements
```bash
# Limit webhook to specific users
# Edit mattermost_btcpay_webhook.js
nano ~/mattermost-webhook/mattermost_btcpay_webhook.js
# Update allowed_users array:
allowed_users: ['admin', 'sysadmin', 'your-username']
# Restart service
sudo systemctl restart btcpay-webhook
```
### Monitoring & Logs
```bash
# Check webhook logs
sudo journalctl -u btcpay-webhook -f
# Test webhook directly
curl -X GET http://localhost:3001/webhook/btcpay/test
# Check health
curl http://localhost:3001/health
```
---
## 🚨 **SECURITY CONSIDERATIONS**
### ✅ **Security Features:**
- Webhook runs on localhost (not exposed externally)
- Token-based authentication
- User authorization (configurable allow-list)
- No sensitive data logged
- Service runs as non-root ubuntu user
### ⚠️ **Important Notes:**
- **Onion addresses are sensitive** - only share with trusted users
- **Limit Mattermost webhook access** to authorized team members
- **Monitor webhook logs** for suspicious activity
- **Rotate tokens periodically** for security
### 🔒 **Recommended Setup:**
1. Use private Mattermost channel for BTCPay commands
2. Limit webhook users to admins only
3. Enable webhook only when needed
4. Monitor access logs regularly
---
## 🔄 **MAINTENANCE**
### Regular Tasks:
```bash
# Check service status
sudo systemctl status btcpay-webhook
# Update webhook script
cd ~/mattermost-webhook
# Copy new version, then:
sudo systemctl restart btcpay-webhook
# View logs
sudo journalctl -u btcpay-webhook --since "1 hour ago"
# Test onion address retrieval
curl -s http://localhost:3001/webhook/btcpay/test | jq .
```
### Troubleshooting:
```bash
# Service not starting
sudo systemctl status btcpay-webhook -l
sudo journalctl -u btcpay-webhook -f
# Can't read onion addresses
ls -la /var/lib/docker/volumes/generated_tor_servicesdir/_data/
sudo cat /var/lib/docker/volumes/generated_tor_servicesdir/_data/BTCPayServer/hostname
# Webhook not responding in Mattermost
curl -X POST http://localhost:3001/webhook/btcpay \
-H "Content-Type: application/json" \
-d '{"token":"your-token","user_name":"admin","text":"!btcpay"}'
```
---
## 📞 **SUPPORT**
### Common Issues:
1. **"Service unavailable"** - Check if BTCPay containers are running
2. **"Onion addresses not found"** - Wait 5 minutes after BTCPay startup
3. **"Access denied"** - Add your Mattermost username to allowed_users
4. **"Token invalid"** - Update MATTERMOST_TOKEN in .env file
### Files to Backup:
- `~/mattermost-webhook/mattermost_btcpay_webhook.js`
- `~/mattermost-webhook/.env` (contains tokens)
- `/etc/systemd/system/btcpay-webhook.service`
---
**🎯 Ready to use! Type `!btcpay` in your Mattermost channel to get BTCPay Server information.**

51
Hostinger/NPM_CONFIG.md Normal file
View File

@@ -0,0 +1,51 @@
# 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
1. Login to NPM admin panel
2. Go to "Proxy Hosts" → "Add Proxy Host"
3. 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):
```nginx
# 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:
1. Check Docker network connectivity
2. Verify BTCPay is accessible locally: `curl http://localhost:8080`
3. Check NPM logs: `docker logs nginx-proxy-manager`
4. Ensure websockets are enabled in proxy host

75
Hostinger/QUICK_REFERENCE.txt Normal file
View File

@@ -0,0 +1,75 @@
================================================================================
DEBIAN 13 SETUP - QUICK REFERENCE CARD
================================================================================
🚀 **30-MINUTE SETUP PROCESS**
1️⃣ FRESH DEBIAN 13 INSTALL
- Hostinger control panel → Reinstall OS → Debian 13
- Password: Th3fa1r13sd1d1t.
2️⃣ COPY FILES (2 minutes)
scp -P 22 vps_hardening_key* root@thebankofdebbie.giize.com:/tmp/
scp -P 22 *.sh root@thebankofdebbie.giize.com:/tmp/
3️⃣ RUN HARDENING (5 minutes)
ssh root@thebankofdebbie.giize.com
chmod +x /tmp/*.sh
/tmp/debian13_vps_hardening.sh
# Add SSH key
cat /tmp/vps_hardening_key.pub > /home/ubuntu/.ssh/authorized_keys
chown ubuntu:ubuntu /home/ubuntu/.ssh/authorized_keys
4️⃣ TEST SSH KEYS (CRITICAL!)
ssh -i vps_hardening_key -p 2255 ubuntu@thebankofdebbie.giize.com
# If working, disable passwords:
sudo sed -i 's/PasswordAuthentication yes/PasswordAuthentication no/' /etc/ssh/sshd_config
sudo systemctl restart ssh
5️⃣ INSTALL BTCPAY (15 minutes)
sudo su -
/tmp/btcpay_tor_installer.sh
6️⃣ MONITOR
~/monitor-btcpay.sh
================================================================================
🔐 **SECURITY CHECKLIST**
□ SSH keys working on port 2255
□ Password auth disabled
□ UFW firewall: 4 rules active
□ Fail2Ban: 2+ jails active
□ Docker: 8 containers running
□ Bitcoin: Pruning confirmed in logs
□ Onion addresses generated
💾 **STORAGE SAFETY**
□ Bitcoin pruned: max 10GB
□ Total usage: ~20GB
□ Available: 367GB+
□ Safe for 387GB VPS ✅
🧅 **TOR INTEGRATION**
□ BTCPay onion service active
□ Bitcoin P2P over Tor only
□ No clearnet Bitcoin connections
□ Customer payment privacy ✅
⚡ **READY FOR PRODUCTION**
□ 24-hour Bitcoin sync complete
□ BTCPay setup wizard done
□ Test payment successful
□ LittleShop API integration ready
================================================================================
📞 **EMERGENCY COMMANDS**
sudo btcpay-restart.sh # Fix most issues
docker ps | grep btcpay # Check containers
df -h # Check disk space
~/monitor-btcpay.sh # Overall status
🎯 **SUCCESS = All green checkboxes above completed!**

8
Hostinger/bankofdebbie Debbie2025.txt Normal file
View File

@@ -0,0 +1,8 @@
bankofdebbie / Debbie2025
ukm.serverssh.net
bankofdebbie / Phenom12#
sysadmin@thebankofdebbie.local

29
Hostinger/btcpay-backup-20250916/docker-compose.override.yml Normal file
View File

@@ -0,0 +1,29 @@
version: "3.6"
services:
bitcoind:
environment:
BITCOIN_EXTRA_ARGS: |
prune=10000
maxmempool=300
dbcache=1000
onlynet=onion
proxyrandomize=1
maxtxfee=0.1
disablewallet=1
btcpayserver_monero:
environment:
XMR_PRUNE_BLOCKCHAIN: 1
XMR_SYNC_PRUNED_BLOCKS: 1
XMR_MAX_CONNECTIONS_IN: 16
XMR_MAX_CONNECTIONS_OUT: 16
XMR_ENABLE_DNS_BLOCKLIST: 1
btcpayserver_monero_wallet:
environment:
MONERO_WALLET_RPC_BIND_IP: 0.0.0.0
MONERO_WALLET_RPC_BIND_PORT: 18083
MONERO_WALLET_RPC_USERNAME: rpc
MONERO_WALLET_RPC_PASSWORD: password
MONERO_DAEMON_ADDRESS: btcpayserver_monero:18081

20
Hostinger/btcpay-backup-20250916/monero-wallet-info.txt Normal file
View File

@@ -0,0 +1,20 @@
Monero Wallet Information
========================
Wallet Address:
49TnBo2VHbncxvrMFbX5uMS9mtAGkiG1L4N6i7MMz4MhA9AXfyRqBdmf1XrFtGXq2v2G72TNtiVFo2kot5SHnBBz3gwoMj9
RPC Credentials:
Username: rpc
Password: password
Wallet Files:
- btcpay (main wallet file)
- btcpay.keys (wallet keys)
- password.txt (contains: password)
Container: btcpayserver_monero_wallet
RPC Port: 18083
Note: This wallet was created on September 16, 2025 to fix the missing wallet issue in BTCPay Server.
The wallet files are stored in Docker volume: generated_xmr_wallet

171
Hostinger/btcpay-backup-20250916/restore-instructions.md Normal file
View File

@@ -0,0 +1,171 @@
# BTCPay Server Restoration Guide
## Prerequisites
- Fresh Debian 13 server
- Root access
- At least 50GB free disk space
- Domain name pointed to server IP
## Restoration Steps
### 1. Initial Server Setup
```bash
# Login as root
ssh root@yourserver.com
# Update system
apt update && apt upgrade -y
# Install required packages
apt install -y git docker.io docker-compose curl
```
### 2. Copy Backup Files
```bash
# Copy this backup folder to server
scp -r btcpay-backup-20250916 root@yourserver.com:/root/
# Navigate to backup
cd /root/btcpay-backup-20250916
```
### 3. Install BTCPay Server
```bash
# Clone BTCPay Docker repository
git clone https://github.com/btcpayserver/btcpayserver-docker /opt/btcpayserver-docker
cd /opt/btcpayserver-docker
# Copy environment file
cp /root/btcpay-backup-20250916/.env /opt/.env
# Copy override file
cp /root/btcpay-backup-20250916/docker-compose.override.yml ./
# Update domain in .env if needed
nano /opt/.env
# Change BTCPAY_HOST to your new domain if different
```
### 4. Run BTCPay Setup
```bash
# Load environment
source /opt/.env
# Run setup
./btcpay-setup.sh -i
# This will:
# - Generate docker-compose configuration
# - Create necessary volumes
# - Start all containers
# - Setup SSL certificates
```
### 5. Restore Monero Wallet (if needed)
```bash
# Wait for containers to start
docker ps
# Create wallet password file
docker exec btcpayserver_monero_wallet sh -c 'echo "password" > /wallet/password.txt'
# Restart wallet container
docker restart btcpayserver_monero_wallet
# Verify wallet is running
docker logs btcpayserver_monero_wallet --tail 50
```
### 6. Configure BTCPay Store
1. Access BTCPay at https://yourdomain.com
2. Create admin account
3. Create store
4. Enable Bitcoin and install Monero plugin:
- Server Settings → Plugins → Install Monero plugin
- Restart BTCPay after plugin installation
5. Configure Monero wallet in store settings:
- Wallet Address: Use the address from monero-wallet-info.txt
- Or generate new wallet if preferred
### 7. Security Hardening
```bash
# Setup firewall
ufw allow 22/tcp
ufw allow 80/tcp
ufw allow 443/tcp
ufw allow 2255/tcp # If using custom SSH port
ufw --force enable
# Change SSH port (optional)
sed -i 's/#Port 22/Port 2255/' /etc/ssh/sshd_config
systemctl restart ssh
# Install fail2ban
apt install -y fail2ban
systemctl enable fail2ban
systemctl start fail2ban
```
### 8. Verify Installation
```bash
# Check all containers running
docker ps
# Check Bitcoin sync status
docker logs generated_bitcoin_1 | grep -i "progress"
# Check Monero status
docker logs btcpayserver_monero | tail -20
# Check BTCPay logs
docker logs generated_btcpayserver_1 | tail -50
# Verify pruning is active
docker logs generated_bitcoin_1 | grep -i "prune"
```
## Important Notes
### Monero Wallet
The Monero wallet address in this backup is:
```
49TnBo2VHbncxvrMFbX5uMS9mtAGkiG1L4N6i7MMz4MhA9AXfyRqBdmf1XrFtGXq2v2G72TNtiVFo2kot5SHnBBz3gwoMj9
```
RPC Password: `password`
### Bitcoin Pruning
Bitcoin is configured to use maximum 10GB disk space. The configuration is in docker-compose.override.yml and will be applied automatically.
### Domain Changes
If restoring to a different domain:
1. Update BTCPAY_HOST in /opt/.env
2. Update REVERSEPROXY_DEFAULT_HOST in /opt/.env
3. Re-run: `./btcpay-setup.sh -i`
### Troubleshooting
**Monero wallet not connecting:**
```bash
docker exec btcpayserver_monero_wallet sh -c 'ls -la /wallet/'
docker restart btcpayserver_monero_wallet
```
**Bitcoin not pruning:**
```bash
# Verify override file is in place
cat /opt/btcpayserver-docker/docker-compose.override.yml
# Restart Bitcoin container
docker restart generated_bitcoin_1
```
**SSL certificate issues:**
```bash
# Force renewal
docker exec generated_letsencrypt-nginx-proxy-companion_1 /app/force_renew
```
## Support
For BTCPay Server support: https://docs.btcpayserver.org/
For Monero plugin: Check BTCPay Server Plugins documentation

56
Hostinger/btcpay-backup-20250916/system-info.txt Normal file
View File

@@ -0,0 +1,56 @@
BTCPay Server System Information
================================
Date: September 16, 2025
Server Details:
- Host: srv1002428.hstgr.cloud (Hostinger VPS)
- Domain: thebankofdebbie.giize.com
- OS: Debian 13
- SSH Port: 2255
- Root Password: Th3fa1r13sd1d1t.
BTCPay Configuration:
- Version: 2.2.1
- Network: Mainnet
- Cryptocurrencies: Bitcoin (BTC), Monero (XMR)
- DOGE: Successfully removed (0 traces)
- Tor: Enabled with onion addresses
- SSL: Let's Encrypt certificate valid until Dec 10, 2025
Bitcoin Configuration:
- Pruning: Enabled (10GB max)
- Sync Status: 99.7% (as of backup)
- Network: Tor-only (onlynet=onion)
- Memory Pool: 300MB max
- DB Cache: 1GB
Monero Configuration:
- Plugin: Installed and configured
- Wallet: Created with RPC access
- Pruning: Enabled
- Daemon: Running and syncing
Docker Containers (11 running):
- generated_btcpayserver_1
- generated_bitcoin_1
- btcpayserver_monero
- btcpayserver_monero_wallet
- generated_postgres_1
- generated_nbxplorer_1
- generated_tor_1
- generated_nginx_1
- generated_letsencrypt-nginx-proxy-companion_1
- generated_docker-gen_1
- autoheal
Storage:
- VPS Total: 394GB
- Available: 239GB (after cleanup)
- Bitcoin Pruned: ~10GB
- Database: ~500MB
Security:
- UFW Firewall: Active (4 rules)
- Fail2Ban: Active (SSH jail)
- SSH: Key authentication on port 2255
- Tor: All crypto traffic routed through Tor

288
Hostinger/btcpay_tor_installer.sh Normal file
View File

@@ -0,0 +1,288 @@
#!/bin/bash
#===============================================================================
# BTCPAY SERVER + TOR AUTOMATED INSTALLER
#===============================================================================
# Created: September 10, 2025
# Purpose: Automated BTCPay Server installation with Tor integration and pruned Bitcoin
# Target: Debian 13 VPS (works on Ubuntu too)
# Prerequisites: Docker installed, user in docker group
set -e # Exit on any error
# Colors for output
RED='\033[0;31m'
GREEN='\033[0;32m'
YELLOW='\033[1;33m'
BLUE='\033[0;34m'
NC='\033[0m' # No Color
# Configuration
BTCPAY_HOST="thebankofdebbie.giize.com"
BITCOIN_PRUNE_SIZE="10000" # 10GB in MB
INSTALL_DIR="/opt/btcpayserver-docker"
# Logging function
log() {
echo -e "${GREEN}[$(date +'%Y-%m-%d %H:%M:%S')] $1${NC}"
}
warn() {
echo -e "${YELLOW}[WARNING] $1${NC}"
}
error() {
echo -e "${RED}[ERROR] $1${NC}"
exit 1
}
info() {
echo -e "${BLUE}[INFO] $1${NC}"
}
# Check if running as root
if [ "$EUID" -ne 0 ]; then
error "Please run as root (use sudo su -)"
fi
log "Starting BTCPay Server + Tor Installation..."
log "Host: $BTCPAY_HOST"
log "Bitcoin Pruning: ${BITCOIN_PRUNE_SIZE}MB (~10GB)"
#===============================================================================
# PHASE 1: PREPARE INSTALLATION DIRECTORY
#===============================================================================
log "PHASE 1: Preparing installation directory..."
# Create and setup BTCPay directory
mkdir -p "$INSTALL_DIR"
cd "$INSTALL_DIR"
# Clone BTCPay Server Docker repository
if [ -d ".git" ]; then
log "BTCPay repository already exists, updating..."
git pull
else
log "Cloning BTCPay Server repository..."
git clone https://github.com/btcpayserver/btcpayserver-docker.git .
fi
chmod +x btcpay-setup.sh
#===============================================================================
# PHASE 2: CONFIGURE ENVIRONMENT VARIABLES
#===============================================================================
log "PHASE 2: Configuring BTCPay environment..."
export BTCPAY_HOST="$BTCPAY_HOST"
export NBITCOIN_NETWORK="mainnet"
export BTCPAYGEN_CRYPTO1="btc"
export BTCPAYGEN_ADDITIONAL_FRAGMENTS="opt-add-tor"
export BTCPAY_ENABLE_SSH="true"
log "Environment configured:"
log " BTCPAY_HOST: $BTCPAY_HOST"
log " NETWORK: $NBITCOIN_NETWORK"
log " CRYPTO: $BTCPAYGEN_CRYPTO1"
log " TOR: $BTCPAYGEN_ADDITIONAL_FRAGMENTS"
log " SSH: $BTCPAY_ENABLE_SSH"
#===============================================================================
# PHASE 3: RUN BTCPAY INSTALLATION
#===============================================================================
log "PHASE 3: Running BTCPay Server installation..."
# Run BTCPay setup
source ./btcpay-setup.sh -i
log "BTCPay Server installation completed"
#===============================================================================
# PHASE 4: CONFIGURE BITCOIN PRUNING
#===============================================================================
log "PHASE 4: Configuring Bitcoin pruning..."
# Stop Bitcoin to modify configuration
docker stop btcpayserver_bitcoind || warn "Bitcoin container not running"
# Add pruning to Docker Compose configuration
COMPOSE_FILE="$INSTALL_DIR/Generated/docker-compose.generated.yml"
if [ -f "$COMPOSE_FILE" ]; then
# Add pruning to BITCOIN_EXTRA_ARGS in docker-compose.yml
sed -i "/maxmempool=500/a\\ prune=$BITCOIN_PRUNE_SIZE" "$COMPOSE_FILE"
log "Added pruning configuration to Docker Compose"
# Verify the change
if grep -q "prune=$BITCOIN_PRUNE_SIZE" "$COMPOSE_FILE"; then
log "✅ Pruning configuration verified in Docker Compose"
else
warn "Failed to add pruning to Docker Compose, adding manually..."
# Alternative method: modify the environment file
echo "BITCOIN_EXTRA_ARGS=prune=$BITCOIN_PRUNE_SIZE" >> /opt/.env
fi
else
warn "Docker Compose file not found, will configure after restart"
fi
#===============================================================================
# PHASE 5: CONFIGURE TOR-ONLY BITCOIN NETWORKING
#===============================================================================
log "PHASE 5: Configuring Tor-only Bitcoin networking..."
# Additional Tor configuration will be applied when container starts
info "Bitcoin will be configured for:"
info " - Pruned mode (${BITCOIN_PRUNE_SIZE}MB max storage)"
info " - Tor-only networking (onlynet=onion via compose config)"
info " - Automatic onion service creation"
#===============================================================================
# PHASE 6: START SERVICES
#===============================================================================
log "PHASE 6: Starting BTCPay services..."
# Start all services
btcpay-up.sh
# Wait for services to start
log "Waiting for services to initialize..."
sleep 30
#===============================================================================
# PHASE 7: VERIFY INSTALLATION
#===============================================================================
log "PHASE 7: Verifying installation..."
# Check Docker containers
log "Checking Docker containers:"
docker ps --format "table {{.Names}}\t{{.Status}}" | grep -E "(btcpay|bitcoin|tor|nginx)"
# Wait for Tor hidden services to be created
log "Waiting for Tor hidden services..."
sleep 30
# Display onion addresses
BTCPAY_ONION=""
BITCOIN_ONION=""
# Try to get onion addresses
if [ -f "/var/lib/docker/volumes/generated_tor_servicesdir/_data/BTCPayServer/hostname" ]; then
BTCPAY_ONION=$(cat /var/lib/docker/volumes/generated_tor_servicesdir/_data/BTCPayServer/hostname)
fi
if [ -f "/var/lib/docker/volumes/generated_tor_servicesdir/_data/BTC-P2P/hostname" ]; then
BITCOIN_ONION=$(cat /var/lib/docker/volumes/generated_tor_servicesdir/_data/BTC-P2P/hostname)
fi
#===============================================================================
# PHASE 8: CONFIGURE BITCOIN PRUNING POST-INSTALL
#===============================================================================
log "PHASE 8: Ensuring Bitcoin pruning is active..."
# Stop Bitcoin to clear any existing blockchain data if needed
docker stop btcpayserver_bitcoind 2>/dev/null || true
# Clear blockchain data to ensure pruning starts fresh
docker run --rm -v generated_bitcoin_datadir:/data alpine sh -c "
if [ -d '/data/blocks' ] && [ -d '/data/chainstate' ]; then
echo 'Clearing existing blockchain data for fresh pruned start...'
rm -rf /data/blocks /data/chainstate /data/indexes
echo 'Blockchain data cleared for pruned node'
else
echo 'No existing blockchain data found'
fi
"
# Restart Bitcoin with pruning
docker start btcpayserver_bitcoind
log "Bitcoin restarted with pruning configuration"
#===============================================================================
# COMPLETION AND STATUS REPORT
#===============================================================================
log "==================================================================="
log "BTCPAY SERVER + TOR INSTALLATION COMPLETED!"
log "==================================================================="
log ""
log "🌐 ACCESS INFORMATION:"
log " Clearnet: https://$BTCPAY_HOST"
if [ -n "$BTCPAY_ONION" ]; then
log " Tor Onion: http://$BTCPAY_ONION"
else
log " Tor Onion: Generating... (check in 5 minutes)"
fi
log ""
log "🔒 SECURITY FEATURES:"
log " ✅ Tor hidden service for BTCPay Server"
log " ✅ Bitcoin P2P over Tor network"
log " ✅ Pruned Bitcoin node (${BITCOIN_PRUNE_SIZE}MB max)"
log " ✅ SSL/HTTPS with Let's Encrypt"
log ""
log "📊 STORAGE MANAGEMENT:"
log " Bitcoin blockchain: ~10GB maximum (pruned)"
log " Total estimated usage: ~20GB for full setup"
log " Safe for 387GB VPS with plenty of room"
log ""
log "⚡ NEXT STEPS:"
log " 1. Wait for Bitcoin initial sync (12-24 hours over Tor)"
log " 2. Access BTCPay via Tor Browser or clearnet"
log " 3. Complete BTCPay setup wizard"
log " 4. Test payment processing"
log ""
if [ -n "$BTCPAY_ONION" ]; then
log "🧅 YOUR TOR ADDRESSES:"
log " BTCPay: $BTCPAY_ONION"
if [ -n "$BITCOIN_ONION" ]; then
log " Bitcoin P2P: $BITCOIN_ONION"
fi
fi
log ""
log "🔧 USEFUL COMMANDS:"
log " btcpay-restart.sh - Restart all services"
log " btcpay-update.sh - Update BTCPay Server"
log " docker logs btcpayserver_bitcoind - Check Bitcoin sync"
log ""
# Show current disk usage
log "💾 CURRENT DISK USAGE:"
df -h / | grep -v tmpfs
# Create monitoring script
log "Creating monitoring script..."
cat > /home/ubuntu/monitor-btcpay.sh << 'EOF'
#!/bin/bash
echo "=== BTCPay + Bitcoin Status - $(date) ==="
echo ""
echo "Docker Containers:"
docker ps --format "table {{.Names}}\t{{.Status}}" | grep -E "(btcpay|bitcoin|tor)"
echo ""
echo "Bitcoin Sync Status:"
docker exec btcpayserver_bitcoind bitcoin-cli getblockchaininfo 2>/dev/null | jq '{blocks, headers, pruned, verificationprogress}' || echo "Bitcoin still starting..."
echo ""
echo "Disk Usage:"
echo "Bitcoin data: $(docker exec btcpayserver_bitcoind du -sh /data/ 2>/dev/null || echo "N/A")"
echo "Total disk: $(df -h / | grep -v Filesystem | awk '{print $3 " used / " $2 " total (" $5 " full)"}')"
echo ""
echo "Tor Onion Addresses:"
echo "BTCPay: $(cat /var/lib/docker/volumes/generated_tor_servicesdir/_data/BTCPayServer/hostname 2>/dev/null || echo "Not ready")"
echo "Bitcoin: $(cat /var/lib/docker/volumes/generated_tor_servicesdir/_data/BTC-P2P/hostname 2>/dev/null || echo "Not ready")"
EOF
chmod +x /home/ubuntu/monitor-btcpay.sh
chown ubuntu:ubuntu /home/ubuntu/monitor-btcpay.sh
log "✅ Installation complete! Use /home/ubuntu/monitor-btcpay.sh to check status"
warn "IMPORTANT: Bitcoin will sync over Tor (slower but private)"
warn "Monitor disk usage, though pruning should keep it under 10GB"

287
Hostinger/debian13_vps_hardening.sh Normal file
View File

@@ -0,0 +1,287 @@
#!/bin/bash
#===============================================================================
# DEBIAN 13 VPS HARDENING AUTOMATION SCRIPT
#===============================================================================
# Created: September 10, 2025
# Purpose: Automated security hardening for Debian 13 VPS
# Target: Hostinger VPS srv1002428.hstgr.cloud
set -e # Exit on any error
# Colors for output
RED='\033[0;31m'
GREEN='\033[0;32m'
YELLOW='\033[1;33m'
NC='\033[0m' # No Color
# Logging function
log() {
echo -e "${GREEN}[$(date +'%Y-%m-%d %H:%M:%S')] $1${NC}"
}
warn() {
echo -e "${YELLOW}[WARNING] $1${NC}"
}
error() {
echo -e "${RED}[ERROR] $1${NC}"
exit 1
}
# Check if running as root
if [ "$EUID" -ne 0 ]; then
error "Please run as root (use sudo su -)"
fi
log "Starting Debian 13 VPS Hardening..."
log "Target: thebankofdebbie.giize.com (31.97.57.205)"
#===============================================================================
# PHASE 1: SYSTEM UPDATES AND PACKAGES
#===============================================================================
log "PHASE 1: Updating system packages..."
apt update && apt upgrade -y
apt install -y curl wget git vim htop ufw fail2ban unattended-upgrades apt-listchanges
# Enable automatic security updates
log "Configuring automatic security updates..."
echo unattended-upgrades unattended-upgrades/enable_auto_updates boolean true | debconf-set-selections
dpkg-reconfigure -f noninteractive unattended-upgrades
#===============================================================================
# PHASE 2: USER SETUP AND SSH KEYS
#===============================================================================
log "PHASE 2: Setting up non-root user..."
# Create sysadmin user
if ! id -u sysadmin > /dev/null 2>&1; then
useradd -m -s /bin/bash sysadmin
usermod -aG sudo sysadmin
log "Created sysadmin user with sudo access"
fi
# Set up SSH directory for sysadmin user
mkdir -p /home/sysadmin/.ssh
chmod 700 /home/sysadmin/.ssh
chown sysadmin:sysadmin /home/sysadmin/.ssh
log "SSH key directory prepared. Add your public key to /home/sysadmin/.ssh/authorized_keys"
#===============================================================================
# PHASE 3: SSH HARDENING
#===============================================================================
log "PHASE 3: Hardening SSH configuration..."
# Backup original SSH config
cp /etc/ssh/sshd_config /etc/ssh/sshd_config.backup
# Create hardened SSH config
cat >> /etc/ssh/sshd_config << 'EOF'
# Security Hardening Configuration - Added by automation script
# Port changed from default 22 for security
Port 2255
# Disable root login - use ubuntu user with sudo instead
PermitRootLogin no
# Authentication settings
PubkeyAuthentication yes
PasswordAuthentication yes
# NOTE: Password auth kept enabled initially - disable after testing keys
AuthorizedKeysFile .ssh/authorized_keys
# Security limits
MaxAuthTries 3
LoginGraceTime 30
MaxStartups 3
# Disable unused authentication methods
ChallengeResponseAuthentication no
UsePAM yes
# Protocol and encryption
Protocol 2
Ciphers aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,aes256-ctr
MACs hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,umac-128-etm@openssh.com
# Disable X11 forwarding and other features
X11Forwarding no
AllowTcpForwarding no
AllowAgentForwarding no
PermitTunnel no
# User restrictions - only allow sysadmin user
AllowUsers sysadmin
# Banner
Banner /etc/ssh/ssh-banner
EOF
# Create SSH banner
cat > /etc/ssh/ssh-banner << 'EOF'
================================================================================
AUTHORIZED ACCESS ONLY
================================================================================
This system is for authorized users only. Activities on this system are
monitored and recorded. By accessing this system, you acknowledge that your
activities may be monitored for security and administrative purposes.
Unauthorized access is prohibited and punishable by law.
================================================================================
EOF
# Test SSH config
sshd -t || error "SSH configuration has syntax errors"
# Disable SSH socket (systemd) to use our custom port
systemctl disable ssh.socket 2>/dev/null || true
systemctl stop ssh.socket 2>/dev/null || true
log "SSH configuration updated. NEW PORT: 2255"
warn "IMPORTANT: Test SSH key access on port 2255 before disconnecting!"
#===============================================================================
# PHASE 4: FIREWALL CONFIGURATION
#===============================================================================
log "PHASE 4: Configuring UFW firewall..."
# Reset UFW to defaults
ufw --force reset
# Set default policies
ufw default deny incoming
ufw default allow outgoing
# Allow new SSH port
ufw allow 2255/tcp comment "SSH-Hardened"
# Allow web traffic for BTCPay
ufw allow 80/tcp comment "HTTP-BTCPay"
ufw allow 443/tcp comment "HTTPS-BTCPay"
# Allow Tor for local connections
ufw allow from 127.0.0.0/8 to any port 9050 comment "Tor-Local"
# Enable firewall
ufw --force enable
log "UFW firewall configured and enabled"
#===============================================================================
# PHASE 5: FAIL2BAN CONFIGURATION
#===============================================================================
log "PHASE 5: Configuring Fail2Ban..."
cat > /etc/fail2ban/jail.local << 'EOF'
[DEFAULT]
# Ban time: 1 hour
bantime = 3600
# Time window for counting failures: 10 minutes
findtime = 600
# Maximum retry attempts before ban
maxretry = 3
# Log level
loglevel = INFO
[sshd]
enabled = true
port = 2255
filter = sshd
backend = systemd
bantime = 7200
maxretry = 3
[nginx-http-auth]
enabled = true
port = 80,443
filter = nginx-http-auth
logpath = /var/log/nginx/error.log
[nginx-noscript]
enabled = true
port = 80,443
filter = nginx-noscript
logpath = /var/log/nginx/access.log
[nginx-badbots]
enabled = true
port = 80,443
filter = nginx-badbots
logpath = /var/log/nginx/access.log
maxretry = 2
EOF
systemctl enable fail2ban
systemctl restart fail2ban
log "Fail2Ban configured for SSH and web protection"
#===============================================================================
# PHASE 6: DOCKER INSTALLATION
#===============================================================================
log "PHASE 6: Installing Docker..."
# Install Docker
curl -fsSL https://get.docker.com -o get-docker.sh
sh get-docker.sh
rm get-docker.sh
# Add sysadmin user to docker group
usermod -aG docker sysadmin
# Start and enable Docker
systemctl start docker
systemctl enable docker
log "Docker installed and configured"
#===============================================================================
# PHASE 7: RESTART SSH WITH NEW CONFIGURATION
#===============================================================================
log "PHASE 7: Restarting SSH service..."
systemctl restart ssh
log "SSH restarted on port 2255"
#===============================================================================
# COMPLETION
#===============================================================================
log "==================================================================="
log "DEBIAN 13 VPS HARDENING COMPLETED SUCCESSFULLY!"
log "==================================================================="
log ""
log "CRITICAL NEXT STEPS:"
log "1. Test SSH access on port 2255 with your SSH keys"
log "2. Add your public key to /home/ubuntu/.ssh/authorized_keys"
log "3. Test: ssh -p 2255 ubuntu@srv1002428.hstgr.cloud"
log "4. Once SSH keys work, disable password authentication"
log "5. Run the BTCPay installation script"
log ""
log "SECURITY STATUS:"
log "✅ SSH hardened (port 2255, key auth, root disabled)"
log "✅ UFW firewall active with secure rules"
log "✅ Fail2Ban monitoring intrusions"
log "✅ Automatic security updates enabled"
log "✅ Docker installed and ready"
log ""
warn "DO NOT DISCONNECT until SSH keys are tested on port 2255!"
# Display current status
log "Current system status:"
ufw status numbered
echo ""
systemctl status fail2ban --no-pager -l | head -5
echo ""
docker --version

75
Hostinger/diagnose-btcpay.sh Normal file
View File

@@ -0,0 +1,75 @@
#!/bin/bash
# BTCPay Server Diagnostic Script
# Run this from your local machine
echo "=== BTCPay Server Remote Diagnostics ==="
echo "Testing: thebankofdebbie.giize.com"
echo "Date: $(date)"
echo ""
# 1. Test DNS resolution
echo "1. DNS Resolution:"
nslookup thebankofdebbie.giize.com | grep -A1 "Name:"
echo ""
# 2. Test HTTP/HTTPS connectivity
echo "2. HTTP/HTTPS Status:"
echo -n " HTTP (80): "
curl -s -o /dev/null -w "%{http_code}" -m 5 http://thebankofdebbie.giize.com
echo ""
echo -n " HTTPS (443): "
curl -s -o /dev/null -w "%{http_code}" -m 5 https://thebankofdebbie.giize.com
echo ""
# 3. Check what's actually being served
echo "3. Server Response Headers:"
curl -I -s https://thebankofdebbie.giize.com | head -10
echo ""
# 4. Test specific BTCPay endpoints
echo "4. BTCPay Endpoints:"
echo -n " /api/v1/health: "
curl -s -o /dev/null -w "%{http_code}" -m 5 https://thebankofdebbie.giize.com/api/v1/health
echo ""
echo -n " /api/v1/server/info: "
curl -s -o /dev/null -w "%{http_code}" -m 5 https://thebankofdebbie.giize.com/api/v1/server/info
echo ""
# 5. Check error details
echo "5. Error Details (if any):"
curl -s -m 5 https://thebankofdebbie.giize.com 2>&1 | grep -E "502|503|504|Bad Gateway|Service Unavailable" | head -5
echo ""
# 6. Test SSH connectivity
echo "6. SSH Connectivity Tests:"
echo -n " Port 22: "
nc -zv -w 2 thebankofdebbie.giize.com 22 2>&1 | grep -o "succeeded\|refused\|timed out"
echo -n " Port 2255: "
nc -zv -w 2 thebankofdebbie.giize.com 2255 2>&1 | grep -o "succeeded\|refused\|timed out"
echo ""
# 7. Try emergency access instructions
echo "7. Manual Access Instructions:"
echo " If you can access via console/VNC from Hostinger panel:"
echo " a) Login as root with password: Th3fa1r13sd1d1t."
echo " b) Run: docker ps -a"
echo " c) Run: cd /opt/btcpayserver-docker && ./btcpay-restart.sh"
echo " d) Check logs: docker logs generated_btcpayserver_1 --tail 50"
echo ""
# 8. Alternative access methods
echo "8. Alternative Access Methods:"
echo " - Hostinger Control Panel: https://hpanel.hostinger.com/"
echo " - VNC/Console access from control panel"
echo " - Support ticket if server is down"
echo ""
echo "=== Summary ==="
if curl -s -o /dev/null -w "%{http_code}" https://thebankofdebbie.giize.com | grep -q "502"; then
echo "STATUS: Bad Gateway (502) - BTCPay container likely down"
echo "ACTION: Need to restart BTCPay services via console access"
elif curl -s -o /dev/null -w "%{http_code}" https://thebankofdebbie.giize.com | grep -q "200"; then
echo "STATUS: Site appears to be working (200 OK)"
else
echo "STATUS: Unknown issue - check manually"
fi

76
Hostinger/fix-bad-gateway.sh Normal file
View File

@@ -0,0 +1,76 @@
#!/bin/bash
# BTCPay Server Bad Gateway Fix Script
# Run this on the server as root
echo "=== BTCPay Server Bad Gateway Troubleshooting ==="
echo "Date: $(date)"
echo ""
# 1. Check disk space
echo "1. Checking disk space..."
df -h / | grep -v Filesystem
echo ""
# 2. Check memory
echo "2. Checking memory..."
free -h | grep Mem
echo ""
# 3. Check Docker service
echo "3. Checking Docker service..."
systemctl status docker | head -5
echo ""
# 4. List all containers (running and stopped)
echo "4. Checking container status..."
docker ps -a --format "table {{.Names}}\t{{.Status}}\t{{.State}}" | head -15
echo ""
# 5. Check BTCPay container specifically
echo "5. BTCPay Server container logs (last 20 lines)..."
docker logs generated_btcpayserver_1 2>&1 | tail -20
echo ""
# 6. Check nginx container
echo "6. Nginx container logs (last 10 lines)..."
docker logs generated_nginx_1 2>&1 | tail -10
echo ""
# 7. Check PostgreSQL
echo "7. PostgreSQL container status..."
docker logs generated_postgres_1 2>&1 | tail -5
echo ""
# Quick fix attempts
echo "=== Attempting Quick Fixes ==="
# 8. Restart BTCPay container
echo "8. Restarting BTCPay Server container..."
docker restart generated_btcpayserver_1
sleep 5
# 9. Check if it's running now
echo "9. BTCPay container status after restart:"
docker ps | grep btcpayserver
echo ""
# 10. If still not working, restart all BTCPay services
echo "10. If still having issues, restart all services with:"
echo " cd /opt/btcpayserver-docker && ./btcpay-restart.sh"
echo ""
# 11. Nuclear option - restart Docker
echo "11. If nothing works, restart Docker daemon:"
echo " systemctl restart docker"
echo " cd /opt/btcpayserver-docker && ./btcpay-restart.sh"
echo ""
echo "=== Diagnostic Summary ==="
docker ps --format "table {{.Names}}\t{{.Status}}" | grep -E "btcpay|nginx|postgres" | head -10
echo ""
echo "Common fixes:"
echo "- If disk full: Clean up with 'docker system prune -a'"
echo "- If memory full: 'systemctl restart docker'"
echo "- If database corrupted: Restore from backup"
echo "- If config issues: cd /opt/btcpayserver-docker && ./btcpay-setup.sh -i"

30
Hostinger/mattermost-local-package.json Normal file
View File

@@ -0,0 +1,30 @@
{
"name": "btcpay-mattermost-local-api",
"version": "1.0.0",
"description": "Local API for Mattermost to retrieve BTCPay onion addresses via SSH",
"main": "mattermost_local_api.js",
"scripts": {
"start": "node mattermost_local_api.js",
"test": "curl http://localhost:3333/health",
"dev": "nodemon mattermost_local_api.js"
},
"dependencies": {
"express": "^4.18.2"
},
"devDependencies": {
"nodemon": "^3.0.1"
},
"keywords": [
"mattermost",
"btcpay",
"ssh",
"onion",
"webhook",
"local-api"
],
"author": "LittleShop Team",
"license": "MIT",
"engines": {
"node": ">=16.0.0"
}
}

344
Hostinger/mattermost_btcpay_webhook.js Normal file
View File

@@ -0,0 +1,344 @@
#!/usr/bin/env node
/**
* ===============================================================================
* MATTERMOST BTCPAY ONION ADDRESS WEBHOOK
* ===============================================================================
* Created: September 10, 2025
* Purpose: Retrieve BTCPay Server and Bitcoin onion addresses via Mattermost
* Domain: thebankofdebbie.giiz.com
* Usage: Post "!btcpay" or "!onion" in Mattermost to get current addresses
*/
const express = require('express');
const { exec } = require('child_process');
const fs = require('fs');
const path = require('path');
const app = express();
const PORT = process.env.PORT || 3001;
// Configuration
const config = {
domain: 'thebankofdebbie.giize.com',
mattermost_token: process.env.MATTERMOST_TOKEN || 'dr7gz6xwmt8qjg71wxcqjwqz1r',
btcpay_tor_path: '/var/lib/docker/volumes/generated_tor_servicesdir/_data/BTCPayServer/hostname',
bitcoin_tor_path: '/var/lib/docker/volumes/generated_tor_servicesdir/_data/BTC-P2P/hostname',
allowed_users: ['admin', 'sysadmin', 'bankofdebbie'], // Add authorized users
webhook_secret: process.env.WEBHOOK_SECRET || 'your-secret-here'
};
app.use(express.json());
app.use(express.urlencoded({ extended: true }));
/**
* Utility function to read onion address from file
*/
function readOnionAddress(filePath) {
return new Promise((resolve, reject) => {
fs.readFile(filePath, 'utf8', (err, data) => {
if (err) {
resolve(null);
} else {
resolve(data.trim());
}
});
});
}
/**
* Get BTCPay Server status
*/
function getBTCPayStatus() {
return new Promise((resolve) => {
exec('docker ps --format "table {{.Names}}\\t{{.Status}}" | grep -E "(btcpay|bitcoin|tor)"', (error, stdout) => {
if (error) {
resolve('BTCPay services status unavailable');
} else {
resolve(stdout.trim() || 'No BTCPay services found');
}
});
});
}
/**
* Get Bitcoin sync status
*/
function getBitcoinSync() {
return new Promise((resolve) => {
exec('docker exec btcpayserver_bitcoind bitcoin-cli getblockchaininfo 2>/dev/null', (error, stdout) => {
if (error) {
resolve('Bitcoin RPC not available');
} else {
try {
const info = JSON.parse(stdout);
const progress = (info.verificationprogress * 100).toFixed(2);
resolve(`Blocks: ${info.blocks}/${info.headers} (${progress}% synced)${info.pruned ? ' - PRUNED' : ''}`);
} catch (e) {
resolve('Bitcoin sync data unavailable');
}
}
});
});
}
/**
* Get disk usage
*/
function getDiskUsage() {
return new Promise((resolve) => {
exec('df -h / | grep -v Filesystem', (error, stdout) => {
if (error) {
resolve('Disk usage unavailable');
} else {
const parts = stdout.trim().split(/\s+/);
resolve(`${parts[2]} used / ${parts[1]} total (${parts[4]} full)`);
}
});
});
}
/**
* Main webhook endpoint
*/
app.post('/webhook/btcpay', async (req, res) => {
try {
// Log the incoming request for debugging
console.log('Webhook received:', JSON.stringify(req.body, null, 2));
const { token, team_domain, user_name, text, trigger_word } = req.body;
// Validate token (basic security)
if (token !== config.mattermost_token) {
return res.status(401).json({ text: 'Unauthorized: Invalid token' });
}
// Check if user is authorized
if (!config.allowed_users.includes(user_name)) {
return res.status(403).json({
text: `❌ Access denied for user: ${user_name}. Contact admin for BTCPay access.`
});
}
// Parse command
const command = text.toLowerCase().trim();
const isOnionCommand = command.includes('onion') || command.includes('btcpay') || command.includes('tor');
const isStatusCommand = command.includes('status');
const isHelpCommand = command.includes('help');
if (isHelpCommand) {
return res.json({
text: `## BTCPay Server Commands\n\n` +
`**Available commands:**\n` +
`• \`!btcpay onion\` - Get onion addresses\n` +
`• \`!btcpay status\` - Get system status\n` +
`• \`!btcpay help\` - Show this help\n\n` +
`**Domain:** ${config.domain}\n` +
`**User:** ${user_name}\n` +
`**Access:** ✅ Authorized`
});
}
if (isOnionCommand || isStatusCommand) {
// Get onion addresses
const [btcpayOnion, bitcoinOnion] = await Promise.all([
readOnionAddress(config.btcpay_tor_path),
readOnionAddress(config.bitcoin_tor_path)
]);
// Get system status if requested
let statusInfo = '';
if (isStatusCommand) {
const [btcpayStatus, bitcoinSync, diskUsage] = await Promise.all([
getBTCPayStatus(),
getBitcoinSync(),
getDiskUsage()
]);
statusInfo = `\n\n**📊 System Status:**\n` +
`**Bitcoin:** ${bitcoinSync}\n` +
`**Disk:** ${diskUsage}\n` +
`**Services:** Running\n\n` +
`\`\`\`\n${btcpayStatus}\n\`\`\``;
}
// Format response
const response = {
text: `## 🧅 BTCPay Server Information\n\n` +
`**Domain:** ${config.domain}\n\n` +
`**🌐 Clearnet Access:**\n` +
`• https://${config.domain}\n\n` +
`**🧅 Tor Hidden Services:**\n` +
`• **BTCPay:** ${btcpayOnion || '⏳ Generating...'}\n` +
`• **Bitcoin P2P:** ${bitcoinOnion || '⏳ Generating...'}\n\n` +
`**🔐 Access Methods:**\n` +
`• **Tor Browser:** \`http://${btcpayOnion || 'pending'}\`\n` +
`• **SSH Tunnel:** \`ssh -L 8080:localhost:80 ubuntu@${config.domain}\`\n\n` +
`**⚡ Integration:**\n` +
`• **API Endpoint:** \`https://${config.domain}/api\`\n` +
`• **Webhook URL:** \`https://${config.domain}/webhook\`\n` +
`• **Onion API:** \`http://${btcpayOnion || 'pending'}/api\`\n\n` +
`**🔒 Security Status:** ✅ Tor-enabled, Pruned Bitcoin, Hardened VPS\n` +
`**📅 Updated:** ${new Date().toLocaleString()}\n` +
`**👤 Requested by:** ${user_name}` +
statusInfo
};
return res.json(response);
}
// Default response
return res.json({
text: `❓ Unknown command. Use \`!btcpay help\` for available commands.\n\n` +
`**Quick commands:**\n` +
`• \`!btcpay onion\` - Get onion addresses\n` +
`• \`!btcpay status\` - Get system status`
});
} catch (error) {
console.error('Webhook error:', error);
return res.status(500).json({
text: `❌ Error retrieving BTCPay information: ${error.message}`
});
}
});
/**
* Health check endpoint
*/
app.get('/health', (req, res) => {
res.json({
status: 'healthy',
service: 'BTCPay Mattermost Webhook',
domain: config.domain,
timestamp: new Date().toISOString()
});
});
/**
* Root health endpoint with HTML response
*/
app.get('/', async (req, res) => {
try {
const [btcpayOnion, bitcoinOnion, diskUsage] = await Promise.all([
readOnionAddress(config.btcpay_tor_path),
readOnionAddress(config.bitcoin_tor_path),
getDiskUsage()
]);
const html = `<!DOCTYPE html>
<html>
<head>
<title>BTCPay Server Health - ${config.domain}</title>
<meta charset="UTF-8">
<style>
body { font-family: Arial, sans-serif; margin: 40px; background: #f5f5f5; }
.container { max-width: 800px; margin: 0 auto; background: white; padding: 30px; border-radius: 8px; box-shadow: 0 2px 10px rgba(0,0,0,0.1); }
.status { color: #28a745; font-weight: bold; }
.onion { background: #f8f9fa; padding: 15px; border-radius: 5px; margin: 10px 0; word-break: break-all; }
.section { margin: 20px 0; padding: 15px; border-left: 4px solid #007bff; }
</style>
</head>
<body>
<div class="container">
<h1>🔒 BTCPay Server Health Status</h1>
<p><strong>Domain:</strong> ${config.domain}</p>
<p><strong>Status:</strong> <span class="status">✅ OPERATIONAL</span></p>
<p><strong>Last Updated:</strong> ${new Date().toLocaleString()}</p>
<div class="section">
<h2>🌐 Access Points</h2>
<p><strong>Clearnet:</strong> <a href="https://${config.domain}">https://${config.domain}</a></p>
<p><strong>Health Dashboard:</strong> <a href="https://health.${config.domain}">https://health.${config.domain}</a></p>
</div>
<div class="section">
<h2>🧅 Tor Hidden Services</h2>
<p><strong>BTCPay Server:</strong></p>
<div class="onion">${btcpayOnion || '⏳ Generating...'}</div>
<p><strong>Bitcoin P2P Node:</strong></p>
<div class="onion">${bitcoinOnion || '⏳ Generating...'}</div>
</div>
<div class="section">
<h2>📊 System Information</h2>
<p><strong>Disk Usage:</strong> ${diskUsage}</p>
<p><strong>Bitcoin Mode:</strong> Pruned (10GB maximum)</p>
<p><strong>Network:</strong> Tor-only Bitcoin connections</p>
<p><strong>Security:</strong> Hardened Debian 13</p>
</div>
<div class="section">
<h2>⚡ API Integration</h2>
<p><strong>REST API:</strong> <code>https://${config.domain}/api</code></p>
<p><strong>Tor API:</strong> <code>http://${btcpayOnion || 'pending'}/api</code></p>
<p><strong>Webhooks:</strong> <code>https://${config.domain}/webhook</code></p>
</div>
<div class="section">
<h2>🤖 Mattermost Integration</h2>
<p><strong>Bot Account:</strong> bankofdebbie</p>
<p><strong>Commands:</strong> !btcpay, !btcpay onion, !btcpay status</p>
<p><strong>Webhook URL:</strong> <code>https://health.${config.domain}/webhook</code></p>
<p><strong>Info API:</strong> <code>https://health.${config.domain}/info</code></p>
</div>
</div>
</body>
</html>`;
res.send(html);
} catch (error) {
res.status(500).send(`<h1>Error</h1><p>${error.message}</p>`);
}
});
/**
* Info endpoint for API information (GET request)
*/
app.get('/info', async (req, res) => {
try {
const [btcpayOnion, bitcoinOnion, btcpayStatus, diskUsage] = await Promise.all([
readOnionAddress(config.btcpay_tor_path),
readOnionAddress(config.bitcoin_tor_path),
getBTCPayStatus(),
getDiskUsage()
]);
res.json({
domain: config.domain,
btcpay_onion: btcpayOnion,
bitcoin_onion: bitcoinOnion,
clearnet_url: `https://${config.domain}`,
api_url: `https://${config.domain}/api`,
disk_usage: diskUsage,
services_status: btcpayStatus,
timestamp: new Date().toISOString()
});
} catch (error) {
res.status(500).json({ error: error.message });
}
});
/**
* Start server
*/
app.listen(PORT, () => {
console.log(`🚀 BTCPay Mattermost Webhook Server running on port ${PORT}`);
console.log(`📡 Domain: ${config.domain}`);
console.log(`🧅 Monitoring onion services...`);
console.log(`💡 Endpoints:`);
console.log(` POST /webhook/btcpay - Main webhook`);
console.log(` GET /webhook/btcpay/test - Test endpoint`);
console.log(` GET /health - Health check`);
console.log(`\n🔧 Setup in Mattermost:`);
console.log(` Trigger: !btcpay`);
console.log(` URL: http://localhost:${PORT}/webhook/btcpay`);
console.log(` Token: ${config.mattermost_token}`);
});
// Graceful shutdown
process.on('SIGTERM', () => {
console.log('🛑 Shutting down webhook server...');
process.exit(0);
});
module.exports = app;

285
Hostinger/mattermost_local_api.js Normal file
View File

@@ -0,0 +1,285 @@
#!/usr/bin/env node
/**
* ===============================================================================
* MATTERMOST LOCAL API FOR BTCPAY SSH COMMANDS
* ===============================================================================
* Created: September 10, 2025
* Purpose: Local web API that runs SSH commands to retrieve BTCPay onion addresses
* Deploy: On your Mattermost server (not the VPS)
* Usage: Mattermost slash commands → Local API → SSH to VPS → Return data
*/
const express = require('express');
const { exec } = require('child_process');
const path = require('path');
const fs = require('fs');
const app = express();
const PORT = process.env.PORT || 3333;
// Configuration - ADJUST THESE PATHS FOR YOUR MATTERMOST SERVER
const config = {
vps_domain: 'thebankofdebbie.giize.com',
vps_port: 2255,
vps_user: 'sysadmin',
ssh_key_path: '/mnt/c/Production/Source/LittleShop/Hostinger/vps_hardening_key',
mattermost_token: '7grgg4r7sjf4dx9qxa7wuybmnh',
allowed_users: ['bankofdebbie', 'admin', 'sysadmin']
};
app.use(express.json());
app.use(express.urlencoded({ extended: true }));
/**
* Execute SSH command to VPS
*/
function executeSSHCommand(command) {
return new Promise((resolve, reject) => {
const sshCmd = `ssh -i ${config.ssh_key_path} -p ${config.vps_port} -o StrictHostKeyChecking=no -o ConnectTimeout=15 ${config.vps_user}@${config.vps_domain} "${command}"`;
console.log(`Executing SSH command: ${command}`);
exec(sshCmd, { timeout: 30000 }, (error, stdout, stderr) => {
if (error) {
console.error(`SSH Error: ${error.message}`);
reject(new Error(`SSH command failed: ${error.message}`));
return;
}
if (stderr) {
console.warn(`SSH Warning: ${stderr}`);
}
resolve(stdout.trim());
});
});
}
/**
* Get BTCPay onion address
*/
async function getBTCPayOnion() {
try {
const result = await executeSSHCommand('sudo cat /var/lib/docker/volumes/generated_tor_servicesdir/_data/BTCPayServer/hostname 2>/dev/null || echo "pending"');
return result || 'pending';
} catch (error) {
return 'error: ' + error.message;
}
}
/**
* Get Bitcoin P2P onion address
*/
async function getBitcoinOnion() {
try {
const result = await executeSSHCommand('sudo cat /var/lib/docker/volumes/generated_tor_servicesdir/_data/BTC-P2P/hostname 2>/dev/null || echo "pending"');
return result || 'pending';
} catch (error) {
return 'error: ' + error.message;
}
}
/**
* Get system status
*/
async function getSystemStatus() {
try {
const commands = [
'docker ps --format "table {{.Names}}\\t{{.Status}}" | grep -E "(btcpay|bitcoin|tor)" | wc -l',
'df -h / | grep -v Filesystem | awk "{print \\$3 \\" used / \\" \\$2 \\" total\\"}"',
'docker logs btcpayserver_bitcoind 2>&1 | grep -i "prune configured" | tail -1 | grep -o "[0-9]* MiB" || echo "10000 MiB"'
];
const [containers, disk, pruning] = await Promise.all(
commands.map(cmd => executeSSHCommand(cmd).catch(err => 'error'))
);
return {
containers: containers + ' containers running',
disk_usage: disk,
bitcoin_pruning: pruning + ' max storage'
};
} catch (error) {
return { error: error.message };
}
}
/**
* Main Mattermost slash command endpoint
*/
app.post('/btcpay', async (req, res) => {
try {
console.log('Mattermost request:', JSON.stringify(req.body, null, 2));
const { token, user_name, text, command } = req.body;
// Validate token
if (token !== config.mattermost_token) {
return res.json({
response_type: 'ephemeral',
text: '❌ Unauthorized: Invalid token'
});
}
// Check if user is authorized
if (!config.allowed_users.includes(user_name)) {
return res.json({
response_type: 'ephemeral',
text: `❌ Access denied for user: ${user_name}. Contact admin for BTCPay access.`
});
}
const commandText = (text || '').toLowerCase().trim();
const isOnionCommand = commandText.includes('onion') || commandText === '' || commandText.includes('addresses');
const isStatusCommand = commandText.includes('status');
const isHelpCommand = commandText.includes('help');
if (isHelpCommand) {
return res.json({
response_type: 'ephemeral',
text: `## BTCPay Server Commands\n\n` +
`**Available commands:**\n` +
`• \`/btcpay\` or \`/btcpay onion\` - Get onion addresses\n` +
`• \`/btcpay status\` - Get system status\n` +
`• \`/btcpay help\` - Show this help\n\n` +
`**VPS:** ${config.vps_domain}\n` +
`**Method:** SSH-based secure retrieval\n` +
`**User:** ${user_name} ✅`
});
}
if (isStatusCommand) {
// Get full system status
const [btcpayOnion, bitcoinOnion, systemStatus] = await Promise.all([
getBTCPayOnion(),
getBitcoinOnion(),
getSystemStatus()
]);
const response = {
response_type: 'in_channel',
text: `## 📊 BTCPay Server Status Report\n\n` +
`**🌐 Domain:** https://${config.vps_domain}\n\n` +
`**🧅 Tor Onion Services:**\n` +
`• **BTCPay:** \`${btcpayOnion}\`\n` +
`• **Bitcoin P2P:** \`${bitcoinOnion}\`\n\n` +
`**📊 System Health:**\n` +
`• **Containers:** ${systemStatus.containers || 'checking...'}\n` +
`• **Storage:** ${systemStatus.disk_usage || 'checking...'}\n` +
`• **Bitcoin:** ${systemStatus.bitcoin_pruning || 'Pruned mode'}\n\n` +
`**🔒 Security:** Tor-only Bitcoin, Hardened Debian 13\n` +
`**📅 Retrieved:** ${new Date().toLocaleString()}\n` +
`**👤 Requested by:** ${user_name}`
};
return res.json(response);
}
if (isOnionCommand) {
// Get onion addresses only
const [btcpayOnion, bitcoinOnion] = await Promise.all([
getBTCPayOnion(),
getBitcoinOnion()
]);
const response = {
response_type: 'in_channel',
text: `## 🧅 BTCPay Tor Onion Addresses\n\n` +
`**🌐 Domain:** https://${config.vps_domain}\n\n` +
`**🧅 Tor Hidden Services:**\n` +
`• **BTCPay Server:** \`${btcpayOnion}\`\n` +
`• **Bitcoin P2P:** \`${bitcoinOnion}\`\n\n` +
`**🔐 Access Methods:**\n` +
`• **Clearnet:** https://${config.vps_domain}\n` +
`• **Tor Browser:** http://${btcpayOnion}\n\n` +
`**⚡ API Endpoints:**\n` +
`• **REST API:** https://${config.vps_domain}/api\n` +
`• **Tor API:** http://${btcpayOnion}/api\n\n` +
`**📅 Retrieved:** ${new Date().toLocaleString()}\n` +
`**👤 Requested by:** ${user_name}`
};
return res.json(response);
}
// Default response
return res.json({
response_type: 'ephemeral',
text: `❓ Unknown command: "${commandText}"\n\n` +
`Use \`/btcpay help\` for available commands.\n\n` +
`**Quick commands:**\n` +
`• \`/btcpay\` - Get onion addresses\n` +
`• \`/btcpay status\` - Get system status`
});
} catch (error) {
console.error('API Error:', error);
return res.json({
response_type: 'ephemeral',
text: `❌ **Error retrieving BTCPay information:**\n\`\`\`\n${error.message}\n\`\`\`\n\nPlease check VPS connectivity.`
});
}
});
/**
* Health check endpoint
*/
app.get('/health', (req, res) => {
res.json({
status: 'healthy',
service: 'Mattermost BTCPay Local API',
vps_target: config.vps_domain,
method: 'SSH-based commands',
timestamp: new Date().toISOString()
});
});
/**
* Test endpoint
*/
app.get('/test', async (req, res) => {
try {
const [btcpayOnion, bitcoinOnion] = await Promise.all([
getBTCPayOnion(),
getBitcoinOnion()
]);
res.json({
vps_domain: config.vps_domain,
btcpay_onion: btcpayOnion,
bitcoin_onion: bitcoinOnion,
method: 'SSH retrieval',
timestamp: new Date().toISOString()
});
} catch (error) {
res.status(500).json({ error: error.message });
}
});
/**
* Start server
*/
app.listen(PORT, '127.0.0.1', () => {
console.log(`🚀 Mattermost BTCPay Local API running on localhost:${PORT}`);
console.log(`🎯 Target VPS: ${config.vps_domain}:${config.vps_port}`);
console.log(`🔑 Method: SSH-based command execution`);
console.log(`💡 Endpoints:`);
console.log(` POST /btcpay - Mattermost slash command handler`);
console.log(` GET /test - Test SSH connectivity`);
console.log(` GET /health - Health check`);
console.log(`\n🔧 Mattermost Slash Command Setup:`);
console.log(` Command: /btcpay`);
console.log(` URL: http://localhost:${PORT}/btcpay`);
console.log(` Token: ${config.mattermost_token}`);
console.log(` Method: POST`);
console.log(`\n⚠️ IMPORTANT: Update ssh_key_path in config before running!`);
console.log(` Current path: ${config.ssh_key_path}`);
});
// Graceful shutdown
process.on('SIGTERM', () => {
console.log('🛑 Shutting down local API server...');
process.exit(0);
});
module.exports = app;

278
Hostinger/mattermost_ssh_webhook.js Normal file
View File

@@ -0,0 +1,278 @@
#!/usr/bin/env node
/**
* ===============================================================================
* MATTERMOST SSH-BASED BTCPAY WEBHOOK
* ===============================================================================
* Created: September 10, 2025
* Purpose: SSH-based webhook to retrieve BTCPay onion addresses via Mattermost
* Domain: thebankofdebbie.giize.com
* Method: SSH connection to retrieve data (no persistent web server)
*/
const express = require('express');
const { exec } = require('child_process');
const path = require('path');
const app = express();
const PORT = process.env.PORT || 3002;
// Configuration
const config = {
domain: 'thebankofdebbie.giize.com',
ssh_host: 'thebankofdebbie.giize.com',
ssh_port: 2255,
ssh_user: 'sysadmin',
ssh_key_path: '/home/sysadmin/.ssh/vps_hardening_key', // Adjust path as needed
mattermost_token: 'dr7gz6xwmt8qjg71wxcqjwqz1r',
allowed_users: ['admin', 'sysadmin', 'bankofdebbie']
};
app.use(express.json());
app.use(express.urlencoded({ extended: true }));
/**
* Execute SSH command to retrieve onion addresses
*/
function getOnionAddresses() {
return new Promise((resolve, reject) => {
const sshCmd = `ssh -i ${config.ssh_key_path} -p ${config.ssh_port} -o StrictHostKeyChecking=no ${config.ssh_user}@${config.ssh_host} "
echo 'BTCPay_Onion:' && sudo cat /var/lib/docker/volumes/generated_tor_servicesdir/_data/BTCPayServer/hostname 2>/dev/null || echo 'pending';
echo 'Bitcoin_Onion:' && sudo cat /var/lib/docker/volumes/generated_tor_servicesdir/_data/BTC-P2P/hostname 2>/dev/null || echo 'pending';
echo 'Disk_Usage:' && df -h / | grep -v Filesystem | awk '{print \$3 \" used / \" \$2 \" total\"}';
echo 'Bitcoin_Status:' && docker exec btcpayserver_bitcoind bitcoin-cli getblockchaininfo 2>/dev/null | jq -r '{blocks, headers, pruned}' || echo 'syncing'
"`;
exec(sshCmd, { timeout: 30000 }, (error, stdout, stderr) => {
if (error) {
reject(new Error(`SSH command failed: ${error.message}`));
return;
}
try {
const lines = stdout.split('\n').filter(line => line.trim());
const result = {
btcpay_onion: 'pending',
bitcoin_onion: 'pending',
disk_usage: 'unknown',
bitcoin_status: 'syncing'
};
lines.forEach(line => {
if (line.startsWith('BTCPay_Onion:')) {
result.btcpay_onion = line.split('BTCPay_Onion:')[1].trim();
} else if (line.startsWith('Bitcoin_Onion:')) {
result.bitcoin_onion = line.split('Bitcoin_Onion:')[1].trim();
} else if (line.startsWith('Disk_Usage:')) {
result.disk_usage = line.split('Disk_Usage:')[1].trim();
} else if (line.startsWith('Bitcoin_Status:')) {
result.bitcoin_status = line.split('Bitcoin_Status:')[1].trim();
}
});
resolve(result);
} catch (parseError) {
reject(new Error(`Failed to parse SSH output: ${parseError.message}`));
}
});
});
}
/**
* Get BTCPay system status via SSH
*/
function getSystemStatus() {
return new Promise((resolve, reject) => {
const sshCmd = `ssh -i ${config.ssh_key_path} -p ${config.ssh_port} -o StrictHostKeyChecking=no ${config.ssh_user}@${config.ssh_host} "
echo 'Container_Count:' && docker ps | grep -E '(btcpay|bitcoin|tor)' | wc -l;
echo 'Uptime:' && uptime | awk '{print \$3 \$4}' | sed 's/,//';
echo 'Bitcoin_Pruned:' && docker logs btcpayserver_bitcoind 2>&1 | grep -i 'prune configured' | tail -1 | grep -o '[0-9]* MiB' || echo 'checking'
"`;
exec(sshCmd, { timeout: 20000 }, (error, stdout) => {
if (error) {
resolve('Status check failed');
return;
}
const lines = stdout.split('\n').filter(line => line.trim());
const result = {};
lines.forEach(line => {
if (line.startsWith('Container_Count:')) {
result.containers = line.split('Container_Count:')[1].trim() + ' containers';
} else if (line.startsWith('Uptime:')) {
result.uptime = line.split('Uptime:')[1].trim();
} else if (line.startsWith('Bitcoin_Pruned:')) {
result.pruning = line.split('Bitcoin_Pruned:')[1].trim();
}
});
resolve(result);
});
});
}
/**
* Main webhook endpoint for Mattermost
*/
app.post('/webhook/btcpay', async (req, res) => {
try {
const { token, user_name, text, trigger_word } = req.body;
// Validate token
if (token !== config.mattermost_token) {
return res.status(401).json({ text: 'Unauthorized: Invalid token' });
}
// Check if user is authorized
if (!config.allowed_users.includes(user_name)) {
return res.status(403).json({
text: `❌ Access denied for user: ${user_name}. Contact admin for BTCPay access.`
});
}
// Parse command
const command = text.toLowerCase().trim();
const isOnionCommand = command.includes('onion') || command.includes('btcpay') || command.includes('tor');
const isStatusCommand = command.includes('status');
const isHelpCommand = command.includes('help');
if (isHelpCommand) {
return res.json({
text: `## BTCPay Server Commands (SSH-based)\n\n` +
`**Available commands:**\n` +
`• \`!btcpay onion\` - Get onion addresses\n` +
`• \`!btcpay status\` - Get system status\n` +
`• \`!btcpay help\` - Show this help\n\n` +
`**Domain:** ${config.domain}\n` +
`**Method:** SSH-based retrieval\n` +
`**User:** ${user_name} ✅`
});
}
if (isOnionCommand || isStatusCommand) {
// Retrieve data via SSH
const [onionData, statusData] = await Promise.all([
getOnionAddresses().catch(err => ({ error: err.message })),
isStatusCommand ? getSystemStatus().catch(err => ({ error: err.message })) : Promise.resolve({})
]);
if (onionData.error) {
return res.json({
text: `❌ **Error retrieving BTCPay data:**\n\`\`\`\n${onionData.error}\n\`\`\`\n\nPlease check VPS connectivity.`
});
}
let statusInfo = '';
if (isStatusCommand && !statusData.error) {
statusInfo = `\n\n**📊 System Status:**\n` +
`**Containers:** ${statusData.containers || 'checking...'}\n` +
`**Uptime:** ${statusData.uptime || 'checking...'}\n` +
`**Bitcoin:** ${statusData.pruning || 'Pruned mode active'}\n` +
`**Disk:** ${onionData.disk_usage}\n` +
`**Sync:** ${onionData.bitcoin_status}`;
}
// Format response
const response = {
text: `## 🧅 BTCPay Server Information (SSH Retrieved)\n\n` +
`**🌐 Domain:** https://${config.domain}\n\n` +
`**🧅 Tor Hidden Services:**\n` +
`• **BTCPay:** \`${onionData.btcpay_onion}\`\n` +
`• **Bitcoin P2P:** \`${onionData.bitcoin_onion}\`\n\n` +
`**🔐 Access Methods:**\n` +
`• **Clearnet:** https://${config.domain}\n` +
`• **Tor Browser:** http://${onionData.btcpay_onion}\n` +
`• **SSH Access:** \`ssh -p ${config.ssh_port} ${config.ssh_user}@${config.domain}\`\n\n` +
`**⚡ API Integration:**\n` +
`• **REST API:** https://${config.domain}/api\n` +
`• **Tor API:** http://${onionData.btcpay_onion}/api\n\n` +
`**🔒 Security:** Hardened Debian 13, Tor-only Bitcoin, SSH-based monitoring\n` +
`**📅 Retrieved:** ${new Date().toLocaleString()}\n` +
`**👤 Requested by:** ${user_name}` +
statusInfo
};
return res.json(response);
}
// Default response
return res.json({
text: `❓ Unknown command. Use \`!btcpay help\` for available commands.\n\n` +
`**Quick access:**\n` +
`• \`!btcpay onion\` - Get Tor onion addresses\n` +
`• \`!btcpay status\` - Get full system status`
});
} catch (error) {
console.error('Webhook error:', error);
return res.status(500).json({
text: `❌ Error retrieving BTCPay information: ${error.message}`
});
}
});
/**
* Health check endpoint
*/
app.get('/health', (req, res) => {
res.json({
status: 'healthy',
service: 'BTCPay SSH Webhook',
domain: config.domain,
method: 'SSH-based retrieval',
timestamp: new Date().toISOString()
});
});
/**
* Info endpoint - SSH-based onion address retrieval
*/
app.get('/info', async (req, res) => {
try {
const data = await getOnionAddresses();
res.json({
domain: config.domain,
btcpay_onion: data.btcpay_onion,
bitcoin_onion: data.bitcoin_onion,
clearnet_url: `https://${config.domain}`,
api_url: `https://${config.domain}/api`,
tor_api_url: `http://${data.btcpay_onion}/api`,
disk_usage: data.disk_usage,
bitcoin_status: data.bitcoin_status,
method: 'SSH retrieval',
timestamp: new Date().toISOString()
});
} catch (error) {
res.status(500).json({
error: error.message,
method: 'SSH retrieval failed'
});
}
});
/**
* Start server
*/
app.listen(PORT, '127.0.0.1', () => {
console.log(`🚀 BTCPay SSH Webhook Server running on localhost:${PORT}`);
console.log(`📡 Domain: ${config.domain}`);
console.log(`🔑 Method: SSH-based onion address retrieval`);
console.log(`💡 Endpoints:`);
console.log(` POST /webhook/btcpay - Main webhook (SSH-based)`);
console.log(` GET /info - Info endpoint (SSH-based)`);
console.log(` GET /health - Health check`);
console.log(`\n🔧 Mattermost Setup:`);
console.log(` Trigger: !btcpay`);
console.log(` URL: Use SSH tunnel to access localhost:${PORT}/webhook/btcpay`);
console.log(` Token: ${config.mattermost_token}`);
console.log(`\n🔒 Security: Binds to localhost only, uses SSH keys for data retrieval`);
});
// Graceful shutdown
process.on('SIGTERM', () => {
console.log('🛑 Shutting down SSH webhook server...');
process.exit(0);
});
module.exports = app;

311
Hostinger/memoires.txt Normal file
View File

@@ -0,0 +1,311 @@
================================================================================
BTCPAY SERVER DEPLOYMENT MEMOIRES
================================================================================
Project: LittleShop Multi-Cryptocurrency Payment System
Deployment Date: September 11-12, 2025
Target: Hostinger VPS (srv1002428.hstgr.cloud / thebankofdebbie.giize.com)
Status: LEARNING EXPERIENCE - COMPLEX SYSTEM WITH FUNDAMENTAL ISSUES
================================================================================
DEPLOYMENT TIMELINE
================================================================================
📅 September 11, 2025:
- Initial BTCPay Server installation attempted on Hostinger VPS
- Discovered Bitcoin daemon restarting due to pruning configuration issues
- Multiple cryptocurrency setup attempted (BTC, DOGE, XMR, DASH, LTC)
📅 September 12, 2025:
- Major disk space crisis discovered (129GB consumed by non-pruned blockchains)
- Extensive troubleshooting of Bitcoin pruning configuration
- Documentation and cleanup of lessons learned
================================================================================
CRITICAL DISCOVERIES
================================================================================
🚨 **MAJOR ISSUE: BTCPAY DOCKER COMPOSE CONFIGURATION SYSTEM IS BROKEN**
Root Problem: BTCPay's docker-compose generator creates corrupted YAML that prevents
environment variables from being properly passed to cryptocurrency containers.
Evidence:
- BITCOIN_EXTRA_ARGS appears correctly in docker-compose.yml
- Environment variable is EMPTY when checked inside Bitcoin container
- Multiple YAML format attempts all failed (|-, |, >, single-line escaped)
- Manual bitcoin.conf modifications get overwritten by entrypoint script
Technical Details:
- Bitcoin container uses /entrypoint.sh that overwrites bitcoin.conf from environment
- Environment variable parsing in BTCPay template system is unreliable
- Configuration hierarchy: .env → docker-compose.yml → container (breaks at last step)
================================================================================
ATTEMPTED SOLUTIONS
================================================================================
❌ **APPROACH 1: Manual bitcoin.conf Editing**
Method: Directly add prune=10000 to bitcoin.conf in Docker volume
Result: FAILED - Container entrypoint overwrites config file on startup
Lesson: Bitcoin container completely regenerates config from environment variables
❌ **APPROACH 2: Docker Compose YAML Direct Editing**
Method: Modify BITCOIN_EXTRA_ARGS in generated docker-compose.yml
Result: FAILED - YAML formatting corruption prevents variable parsing
Lesson: BTCPay's multiline YAML generation is fragile and unreliable
❌ **APPROACH 3: Environment File Override**
Method: Add BITCOIN_EXTRA_ARGS directly to /opt/.env file
Result: FAILED - Environment variables not inherited properly
Lesson: BTCPay doesn't use .env file for Docker Compose environment variables
❌ **APPROACH 4: YAML Format Variations**
Method: Tried |- (literal), | (literal), > (folded), single-line escaped
Result: ALL FAILED - Environment variable still empty in container
Lesson: The issue is not YAML syntax but fundamental parsing/generation bug
❌ **APPROACH 5: Docker Compose Override File**
Method: Create docker-compose.override.yml to override Bitcoin configuration
Result: PARTIAL SUCCESS - Pruning config read but RPC authentication broken
Status: Closest to working solution, needs refinement
❌ **APPROACH 6: Clean Bitcoin Core from Scratch**
Method: Build standard Bitcoin Core container bypassing BTCPay entirely
Result: MOUNT ISSUES - Docker volume configuration problems
Status: Interrupted due to complexity
================================================================================
SPACE MANAGEMENT CRISIS
================================================================================
🚨 **DISK SPACE EMERGENCY (September 12, 2025)**
Crisis Discovery:
- Litecoin daemon: 78GB (no pruning configured)
- Dogecoin daemon: 51GB (no pruning configured)
- Monero daemon: 6.5GB
- Total impact: 135GB consumed (34% of 394GB disk)
Resolution:
- Emergency stop of all cryptocurrency daemons
- Manual deletion of blockchain data: sudo rm -rf /var/lib/docker/volumes/*/data/*
- Space recovered: 129GB freed
- Final usage: 63GB used / 316GB available (safe)
Lesson Learned:
ALL cryptocurrency daemons need explicit pruning configuration, not just Bitcoin.
Default behavior downloads full blockchains (50-80GB each).
================================================================================
CRYPTOCURRENCY INTEGRATION STATUS
================================================================================
✅ **WORKING SERVICES:**
- BTCPay Web Interface: Operational (https://thebankofdebbie.giize.com)
- Database: PostgreSQL running and accessible
- SSL/TLS: nginx reverse proxy with Let's Encrypt working
- Tor Network: Hidden services configured and operational
⚠️ **CRYPTOCURRENCY STATUS:**
Bitcoin (BTC):
- Container runs but pruning config not applied
- Shows height 0 in BTCPay interface
- RPC connectivity issues with NBXplorer
Dogecoin (DOGE):
- Container runs and loads block index
- Shows height 0 in BTCPay interface
- RPC not ready during startup phase
Monero (XMR):
- Daemon container operational
- Wallet container restarting (configuration issues)
- Missing from BTCPay interface (NBXplorer not configured)
Ethereum (ETH):
- Configured in BTCPAY_CRYPTOS environment
- NO CONTAINERS CREATED (possibly unsupported in this BTCPay version)
Zcash (ZEC):
- Only wallet container present, main daemon missing
- Not appearing in BTCPay interface
❌ **CORE PROBLEM:**
NBXplorer (blockchain explorer) only configured for "btc,doge" instead of full
cryptocurrency set. This explains why other cryptocurrencies don't appear in
BTCPay interface even when containers are running.
================================================================================
TECHNICAL ARCHITECTURE ANALYSIS
================================================================================
**BTCPay Server Components:**
1. **BTCPay Application**: Web interface, store management, payment processing
2. **NBXplorer**: Blockchain explorer that connects BTCPay to cryptocurrency daemons
3. **Cryptocurrency Daemons**: Bitcoin Core, Dogecoin Core, Monero, etc.
4. **Database**: PostgreSQL for BTCPay data storage
5. **Proxy**: nginx with SSL termination and Tor integration
**Configuration Flow:**
.env file → BTCPay setup script → docker-compose generation → container environment → config files
**Failure Points Identified:**
- Step 3→4: docker-compose to container environment (YAML parsing broken)
- Step 4→5: Container environment to config files (entrypoint script issues)
**Working Components:**
- BTCPay web interface and database
- SSL/nginx proxy infrastructure
- Tor network integration
- Basic container orchestration
**Broken Components:**
- Cryptocurrency daemon configuration management
- Bitcoin pruning configuration persistence
- Multi-cryptocurrency NBXplorer integration
================================================================================
LESSONS LEARNED
================================================================================
🔧 **Docker & Configuration Management:**
1. **BTCPay Complexity**: BTCPay Server's Docker setup is overly complex with multiple
layers of configuration that can break independently
2. **Environment Variable Reliability**: Docker Compose multiline YAML strings are
fragile and prone to parsing failures in BTCPay's template system
3. **Container Entrypoint Behavior**: Cryptocurrency containers completely regenerate
config files from environment variables, ignoring manual modifications
4. **Override File Limitations**: docker-compose.override.yml works for passing
variables but doesn't guarantee proper parsing by container entrypoints
🪙 **Cryptocurrency Management:**
1. **Pruning is Critical**: Without explicit pruning, cryptocurrency daemons will
consume 50-80GB each, quickly filling disk space
2. **Sync Time Reality**: Tor-only networking significantly slows blockchain sync
(12-24 hours for Bitcoin vs 2-4 hours clearnet)
3. **RPC Dependency**: BTCPay requires cryptocurrency RPC to be fully operational
before showing proper status (height 0 = RPC not ready)
4. **NBXplorer Central Role**: All cryptocurrencies must be configured in NBXplorer
to appear in BTCPay interface, regardless of daemon status
📊 **Resource Planning:**
1. **Storage Requirements**: Even pruned Bitcoin (10GB) + multiple altcoins can
consume 50+ GB during sync before pruning kicks in
2. **Memory Usage**: Multiple cryptocurrency daemons running simultaneously
requires careful memory allocation
3. **Network Bandwidth**: Initial blockchain download over Tor is bandwidth intensive
4. **Monitoring Necessity**: Real-time disk space monitoring essential during setup
================================================================================
SUCCESSFUL APPROACHES
================================================================================
✅ **What Actually Worked:**
1. **Manual Command Line Parameters**:
Direct Bitcoin Core with command line pruning parameters worked perfectly
Evidence: "Prune configured to target 10000 MiB on disk for block and undo files."
2. **Docker Volume Management**:
Manual deletion of blockchain data effective for space recovery
Command: sudo rm -rf /var/lib/docker/volumes/*/data/*
3. **Service Isolation**:
Individual container management more reliable than BTCPay's orchestration
Docker individual start/stop commands work better than btcpay-restart.sh
4. **Configuration Verification**:
Direct log analysis most reliable method for confirming configuration application
grep -E '(prune|Prune)' provides definitive confirmation
================================================================================
RECOMMENDATIONS
================================================================================
🎯 **For Future Cryptocurrency Payment Systems:**
**SIMPLE APPROACH (Recommended):**
1. Use standard Bitcoin Core Docker image with direct configuration
2. Mount proper bitcoin.conf file with known working settings
3. Create simple payment processing API that connects to Bitcoin RPC
4. Avoid complex orchestration systems like BTCPay for basic needs
**BTCPAY APPROACH (If Required):**
1. Start with single cryptocurrency (Bitcoin only)
2. Use docker-compose.override.yml for configuration overrides
3. Expect configuration issues and plan for extensive troubleshooting
4. Monitor disk space continuously during setup
5. Test in regtest mode first to verify connectivity
**INFRASTRUCTURE REQUIREMENTS:**
- Minimum 1TB storage for multiple cryptocurrencies
- Real-time disk monitoring and alerts
- Automated backup of cryptocurrency wallet data
- Network redundancy for Tor connectivity
================================================================================
CURRENT STATE
================================================================================
**System Status (September 12, 2025):**
- Host: Hostinger VPS (394GB storage, 316GB available)
- BTCPay Web Interface: Operational
- Bitcoin Daemon: Stopped (pruning configuration failed)
- Dogecoin Daemon: Running but not syncing properly
- Other Cryptocurrencies: Partially configured, not operational
- Disk Space: Safe (crisis resolved through manual cleanup)
**Working Components:**
- SSL certificates and nginx proxy
- Tor network integration
- BTCPay application framework
- Database and core infrastructure
**Unresolved Issues:**
- Bitcoin pruning configuration persistence
- Multi-cryptocurrency NBXplorer integration
- Height 0 display in BTCPay interface (RPC connectivity)
- Missing Ethereum and Zcash main daemons
**Documentation Status:**
- Technical discoveries recorded in CLAUDE.md
- Infrastructure details updated in Infrastructure.txt
- Complete troubleshooting history preserved
================================================================================
FINAL ASSESSMENT
================================================================================
**Time Investment:** 6+ hours of intensive troubleshooting
**Success Rate:** Partial (infrastructure working, cryptocurrencies problematic)
**Learning Value:** High (discovered fundamental BTCPay limitations)
**Production Readiness:** Low (requires significant additional work)
**Recommendation:**
For production cryptocurrency payment processing, consider simpler alternatives
to BTCPay Server. The complexity-to-reliability ratio is unfavorable for
straightforward payment processing needs.
A simple Bitcoin Core node + custom payment API would be more reliable and
maintainable than BTCPay's complex Docker orchestration system.
================================================================================
END OF DEPLOYMENT MEMOIRES
================================================================================
Total Configuration Attempts: 15+
Working Solutions Found: 1 (partial - docker-compose.override.yml)
Time to Working System: 6+ hours (still incomplete)
Complexity Rating: EXCESSIVE for basic cryptocurrency payment processing
Conclusion: BTCPay Server is a powerful but overly complex system that requires
extensive expertise to configure properly. For basic needs, simpler solutions
are more appropriate.

5
Hostinger/package.json Normal file
View File

@@ -0,0 +1,5 @@
{
"dependencies": {
"express": "^5.1.0"
}
}

7
Hostinger/vps_hardening_key Normal file
View File

@@ -0,0 +1,7 @@
-----BEGIN OPENSSH PRIVATE KEY-----
b3BlbnNzaC1rZXktdjEAAAAABG5vbmUAAAAEbm9uZQAAAAAAAAABAAAAMwAAAAtzc2gtZW
QyNTUxOQAAACA6FJ1J+cLCcnpceTQMz9Za3EwSgFfd5vEdYZUdGVNO2QAAAKCIXIdMiFyH
TAAAAAtzc2gtZWQyNTUxOQAAACA6FJ1J+cLCcnpceTQMz9Za3EwSgFfd5vEdYZUdGVNO2Q
AAAED0lVOb+ITmHrQGEnWUZ9OkZyCswBYDEheIcDUfEXvPdToUnUn5wsJyelx5NAzP1lrc
TBKAV93m8R1hlR0ZU07ZAAAAFnZwcy1oYXJkZW5pbmctMjAyNTA5MTABAgMEBQYH
-----END OPENSSH PRIVATE KEY-----

1
Hostinger/vps_hardening_key.pub Normal file
View File

@@ -0,0 +1 @@
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIDoUnUn5wsJyelx5NAzP1lrcTBKAV93m8R1hlR0ZU07Z vps-hardening-20250910

30
Hostinger/webhook-package.json Normal file
View File

@@ -0,0 +1,30 @@
{
"name": "btcpay-mattermost-webhook",
"version": "1.0.0",
"description": "Mattermost webhook to retrieve BTCPay Server onion addresses",
"main": "mattermost_btcpay_webhook.js",
"scripts": {
"start": "node mattermost_btcpay_webhook.js",
"test": "curl http://localhost:3001/health",
"dev": "nodemon mattermost_btcpay_webhook.js"
},
"dependencies": {
"express": "^4.18.2"
},
"devDependencies": {
"nodemon": "^3.0.1"
},
"keywords": [
"btcpay",
"mattermost",
"webhook",
"tor",
"onion",
"bitcoin"
],
"author": "LittleShop Team",
"license": "MIT",
"engines": {
"node": ">=16.0.0"
}
}