Files
proxmox/docs/05-network/CLOUDFLARE_ROUTING_MASTER.md
defiQUG cb47cce074 Complete markdown files cleanup and organization
- 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.
2026-01-06 01:46:25 -08:00

4.9 KiB

Cloudflare Routing Master Reference

Navigation: Home > Network > Cloudflare Routing Master

Last Updated: 2025-01-20
Document Version: 1.0
Status: 🟢 Active Documentation


Overview

This is the authoritative reference for Cloudflare tunnel routing architecture. All routing decisions, domain mappings, and tunnel configurations are documented here.

Note: This document consolidates routing information from multiple sources. For specific setup procedures, see the related documents below.


Architecture Overview

Internet → Cloudflare → cloudflared (VMID 102) → Routing Decision
                                                      ├─ HTTP RPC → Central Nginx (VMID 105) → RPC Nodes
                                                      └─ WebSocket RPC → Direct to RPC Nodes

Routing Rules

HTTP Endpoints (via Central Nginx)

All HTTP endpoints route through the central Nginx on VMID 105 (192.168.11.21:80):

Domain Cloudflare Tunnel → Central Nginx → Final Destination
explorer.d-bis.org http://192.168.11.21:80 http://192.168.11.140:80 Blockscout
rpc-http-pub.d-bis.org http://192.168.11.21:80 https://192.168.11.252:443 RPC Public (HTTP)
rpc-http-prv.d-bis.org http://192.168.11.21:80 https://192.168.11.251:443 RPC Private (HTTP)
dbis-admin.d-bis.org http://192.168.11.21:80 http://192.168.11.130:80 DBIS Frontend
dbis-api.d-bis.org http://192.168.11.21:80 http://192.168.11.150:3000 DBIS API Primary
dbis-api-2.d-bis.org http://192.168.11.21:80 http://192.168.11.151:3000 DBIS API Secondary
mim4u.org http://192.168.11.21:80 http://192.168.11.19:80 Miracles In Motion
www.mim4u.org http://192.168.11.21:80 301 Redirectmim4u.org Redirects to non-www

WebSocket Endpoints (Direct Routing)

WebSocket endpoints route directly to RPC nodes, bypassing the central Nginx:

Domain Cloudflare Tunnel → Direct to RPC Node → Final Destination
rpc-ws-pub.d-bis.org wss://192.168.11.252:443 wss://192.168.11.252:443 127.0.0.1:8546 (WebSocket)
rpc-ws-prv.d-bis.org wss://192.168.11.251:443 wss://192.168.11.251:443 127.0.0.1:8546 (WebSocket)

Why Direct Routing for WebSockets?

  • WebSocket connections require persistent connections and protocol upgrades
  • Direct routing reduces latency and connection overhead
  • RPC nodes handle WebSocket connections efficiently on their own Nginx instances

Cloudflare Tunnel Configuration

Tunnel: rpc-http-pub.d-bis.org (Tunnel ID: 10ab22da-8ea3-4e2e-a896-27ece2211a05)

Location: VMID 102 (cloudflared container)

Configuration: See CLOUDFLARE_TUNNEL_ROUTING_ARCHITECTURE.md for complete tunnel configuration.


Central Nginx Configuration

Nginx Proxy Manager (VMID 105)

IP Address: 192.168.11.21
Configuration File: /data/nginx/custom/http.conf
Status: Active and running

Services Configured: See CENTRAL_NGINX_ROUTING_SETUP.md for complete configuration.


Setup Guides

Architecture Documents

Domain and DNS


Last Updated: 2025-01-20
Document Version: 1.0
Review Cycle: Quarterly