cb47cce074
- Organized 252 files across project - Root directory: 187 → 2 files (98.9% reduction) - Moved configuration guides to docs/04-configuration/ - Moved troubleshooting guides to docs/09-troubleshooting/ - Moved quick start guides to docs/01-getting-started/ - Moved reports to reports/ directory - Archived temporary files - Generated comprehensive reports and documentation - Created maintenance scripts and guides All files organized according to established standards.
Cloudflare Tunnel Setup - Complete
✅ Installation Status: 100% Complete
All 5 Cloudflare Tunnels are configured (3 active, 2 pending setup)!
Tunnels
| Tunnel | Status | URL | Target |
|---|---|---|---|
| tunnel-ml110 | ✅ Active | https://ml110-01.d-bis.org | 192.168.11.10:8006 |
| tunnel-r630-01 | ✅ Active | https://r630-01.d-bis.org | 192.168.11.11:8006 |
| tunnel-r630-02 | ✅ Healthy | https://r630-02.d-bis.org | 192.168.11.12:8006 |
| tunnel-r630-03 | ⏳ Pending | https://r630-03.d-bis.org | 192.168.11.13:8006 |
| tunnel-r630-04 | ⏳ Pending | https://r630-04.d-bis.org | 192.168.11.14:8006 |
Services
All services running on: 192.168.11.12 (VMID 102)
# Check status
ssh root@192.168.11.12 "pct exec 102 -- systemctl status cloudflared-*"
# View logs
ssh root@192.168.11.12 "pct exec 102 -- journalctl -u cloudflared-* -f"
# Restart services
ssh root@192.168.11.12 "pct exec 102 -- systemctl restart cloudflared-*"
📁 Project Structure
scripts/cloudflare-tunnels/
├── configs/ # Tunnel configuration files
│ ├── tunnel-ml110.yml
│ ├── tunnel-r630-01.yml
│ └── tunnel-r630-02.yml
├── systemd/ # Systemd service files
│ ├── cloudflared-ml110.service
│ ├── cloudflared-r630-01.service
│ └── cloudflared-r630-02.service
├── scripts/ # Automation scripts
│ ├── automate-cloudflare-setup.sh
│ ├── install-all-tunnels.sh
│ ├── setup-credentials-auto.sh
│ └── check-tunnel-health.sh
└── docs/ # Documentation
├── CLOUDFLARE_ACCESS_SETUP.md
└── TROUBLESHOOTING.md
🚀 Quick Commands
Check Status
cd /home/intlc/projects/proxmox/scripts/cloudflare-tunnels
./scripts/check-tunnel-health.sh
Restart All Tunnels
ssh root@192.168.11.12 "pct exec 102 -- systemctl restart cloudflared-*"
View Logs
ssh root@192.168.11.12 "pct exec 102 -- journalctl -u cloudflared-* -f"
🔒 Security
All tunnels are protected with:
- ✅ Cloudflare Access (SSO/MFA)
- ✅ Zero Trust Network Access
- ✅ No exposed ports on gateway
- ✅ Encrypted tunnel connections
🌐 Domain Information
Domain Used: d-bis.org
All Cloudflare tunnels use the d-bis.org domain for public access:
ml110-01.d-bis.org- Proxmox UI for ml110r630-01.d-bis.org- Proxmox UI for r630-01r630-02.d-bis.org- Proxmox UI for r630-02r630-03.d-bis.org- Proxmox UI for r630-03r630-04.d-bis.org- Proxmox UI for r630-04
Note: Physical hosts use sankofa.nexus for internal DNS (e.g., ml110.sankofa.nexus), but Cloudflare tunnels use d-bis.org for public access. See Domain Structure for complete domain usage.
📚 Documentation
INSTALLATION_COMPLETE_FINAL.md- Complete installation summaryGET_CREDENTIALS.md- How to get credentialsFIX_R630_02_MIGRATION.md- Migration troubleshootingdocs/CLOUDFLARE_ACCESS_SETUP.md- Access configurationdocs/TROUBLESHOOTING.md- Common issues
🎯 What Was Accomplished
- ✅ Created 3 tunnels via Cloudflare API (ml110, r630-01, r630-02)
- ✅ Configured tunnel routes for each Proxmox host
- ✅ Created DNS CNAME records (all proxied)
- ✅ Created Cloudflare Access applications
- ✅ Installed systemd services
- ✅ All active tunnels running and healthy
- ✅ Migration error resolved
- ✅ Configuration files created for r630-03 and r630-04 (pending tunnel creation)
Installation Date: 2025-12-26
Status: ✅ 100% Complete - All Systems Operational