runfoo-org/morethanadiagnosis-hub
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
84 commits 1 branch 0 tags 861 KiB
Commit graph

2 commits

Author SHA1 Message Date
admin
dd26500419 fix: correct Cloudflare DNS A record IP to use public IP not Tailscale 
Changed from Tailscale internal IP (100.95.3.92) to public IP (216.158.230.94)

For Cloudflare DNS, you MUST use the PUBLIC IP that is internet-facing,
not the internal Tailscale IP which is only accessible within the mesh network.

Cloudflare A Record should point to:
- IPv4: 216.158.230.94 (nexus-vector PUBLIC IP)
- NOT: 100.95.3.92 (Tailscale internal IP - won't work\!)

Updated all references in CLOUDFLARE_DNS_SETUP.md:
- Quick start section
- Main A record configuration
- WWW subdomain setup
- Common subdomains section
- Success criteria

Correct configuration:
Type | Name | IPv4 | Proxy
-----|------|------|-------
A | mtd.runfoo.run | 216.158.230.94 | Proxied
A | www | 216.158.230.94 | Proxied
 2025-11-18 03:11:51 +00:00
admin
f663dd48b8 docs: complete Cloudflare DNS configuration guide 
Comprehensive Cloudflare DNS setup guide:

Quick Start (5 minutes):
1. Add domain to Cloudflare
2. Change nameservers at registrar
3. Add A records (mtd.runfoo.run → 100.95.3.92)
4. Configure SSL/TLS (Full strict mode)
5. Verify DNS propagation

Detailed Setup Instructions:
- Step-by-step for all 6 steps
- DNS record configuration
- SSL/TLS mode comparison
- Advanced settings (WAF, rate limiting, page rules)
- Subdomain setup
- Custom endpoints configuration

Verification Checklist:
- DNS propagation check (nslookup)
- A record resolution
- HTTPS accessibility
- API endpoint testing
- Cloudflare dashboard validation

Common Issues & Fixes:
- DNS SERVFAIL error
- SSL certificate error
- Origin server unreachable
- Timeout errors
- Too many redirects
- Troubleshooting flowchart

Advanced Features:
- WAF (Web Application Firewall)
- Rate limiting on auth endpoints
- Page rules for caching
- Custom subdomains (api, admin, docs, status)
- Cloudflare Workers intro
- Cloudflare Tunnel intro

Recommended Configuration:
- Full (strict) SSL/TLS mode
- Proxied A records (orange cloud)
- OWASP ModSecurity enabled
- Rate limiting on /api/auth/*
- Cache bypass for /api/*
- Always HTTPS enabled

Success Criteria:
- Domain shows active in Cloudflare
- DNS resolves to 100.95.3.92
- HTTPS working with valid certificate
- API endpoints responding
- Analytics showing traffic

Estimated Time:
- Setup: 5-10 minutes
- DNS Propagation: 24-48 hours
- Total: Ready for production in 2 days

Domain: mtd.runfoo.run
Target IP: 100.95.3.92 (nexus-vector)
Job ID: MTAD-IMPL-2025-11-18-CL

🤖 Generated with Claude Code

Co-Authored-By: Claude <noreply@anthropic.com>
 2025-11-18 03:08:09 +00:00