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.
131 lines
3.3 KiB
Markdown
131 lines
3.3 KiB
Markdown
# Info Endpoint Recheck - info.defi-oracle.io
|
|
|
|
**Date**: 2026-01-05
|
|
**Status**: ⚠️ **INTERMITTENT 502 ERRORS**
|
|
|
|
---
|
|
|
|
## Current Status
|
|
|
|
### Test Results
|
|
|
|
**Root Endpoint (`/`)**:
|
|
- ✅ **Local Access**: Returns HTML (200 OK, 7157 bytes)
|
|
- ⚠️ **Public HTTPS**: Intermittent 502 errors (sometimes works, sometimes fails)
|
|
- **HTTP Headers**: Shows HTTP/2 200 when working
|
|
- **Content-Type**: `text/html` when successful
|
|
|
|
**JSON Endpoints**:
|
|
- `/chain.json`: Intermittent 502 errors
|
|
- `/api/chain`: Intermittent 502 errors
|
|
|
|
---
|
|
|
|
## Observations
|
|
|
|
1. **Nginx is working correctly**:
|
|
- All endpoints return 200 OK when accessed locally
|
|
- Files are being served correctly
|
|
- No errors in Nginx logs for successful requests
|
|
|
|
2. **Cloudflare Tunnel**:
|
|
- Service is running (`cloudflared.service` active)
|
|
- Tunnel is connected
|
|
- Intermittent connection issues
|
|
|
|
3. **Intermittent Nature**:
|
|
- Sometimes requests succeed (HTTP 200)
|
|
- Sometimes requests fail (HTTP 502)
|
|
- Suggests timeout or connection pool issues
|
|
|
|
---
|
|
|
|
## Possible Causes
|
|
|
|
1. **Cloudflare Tunnel Timeout**:
|
|
- Tunnel may be timing out on some requests
|
|
- Connection pool exhaustion
|
|
- Rate limiting
|
|
|
|
2. **Cloudflare Edge Caching**:
|
|
- Edge cache may be serving stale 502 errors
|
|
- Cache needs to be purged
|
|
|
|
3. **Connection Limits**:
|
|
- Tunnel may have connection limits
|
|
- Multiple simultaneous requests may cause issues
|
|
|
|
4. **Network Latency**:
|
|
- High latency causing timeouts
|
|
- Cloudflare edge location issues
|
|
|
|
---
|
|
|
|
## Recommendations
|
|
|
|
### Immediate Actions
|
|
|
|
1. **Purge Cloudflare Cache**:
|
|
- Go to Cloudflare Dashboard
|
|
- Navigate to Caching → Purge Everything
|
|
- Wait 1-2 minutes for propagation
|
|
|
|
2. **Check Tunnel Health**:
|
|
- Verify tunnel status in Cloudflare Dashboard
|
|
- Check for any tunnel errors or warnings
|
|
- Review tunnel metrics
|
|
|
|
3. **Monitor Patterns**:
|
|
- Track when 502 errors occur
|
|
- Check if errors are time-based
|
|
- Monitor connection patterns
|
|
|
|
### Configuration Adjustments
|
|
|
|
1. **Increase Timeouts** (if needed):
|
|
- Adjust Cloudflare tunnel timeout settings
|
|
- Increase Nginx proxy timeouts
|
|
- Review connection pool settings
|
|
|
|
2. **Enable Caching**:
|
|
- Configure Cloudflare to cache static content
|
|
- Set appropriate cache headers
|
|
- Use Cloudflare's HTML minification
|
|
|
|
---
|
|
|
|
## Verification Commands
|
|
|
|
### Test Local Access
|
|
```bash
|
|
ssh root@192.168.11.10 "pct exec 2400 -- curl -s http://127.0.0.1:80 -H 'Host: info.defi-oracle.io'"
|
|
```
|
|
|
|
### Test Public Access
|
|
```bash
|
|
curl -s https://info.defi-oracle.io
|
|
curl -s https://info.defi-oracle.io/chain.json
|
|
curl -s https://info.defi-oracle.io/api/chain
|
|
```
|
|
|
|
### Check Nginx Logs
|
|
```bash
|
|
ssh root@192.168.11.10 "pct exec 2400 -- tail -20 /var/log/nginx/info-defi-oracle-access.log"
|
|
```
|
|
|
|
### Check Cloudflared Status
|
|
```bash
|
|
ssh root@192.168.11.10 "pct exec 2400 -- systemctl status cloudflared"
|
|
```
|
|
|
|
---
|
|
|
|
## Current Working State
|
|
|
|
✅ **Nginx Configuration**: Correct and serving files properly
|
|
✅ **File System**: Files exist and are accessible
|
|
✅ **Local Routing**: All endpoints work when accessed directly
|
|
⚠️ **Cloudflare Tunnel**: Intermittent connection issues causing 502 errors
|
|
|
|
**Conclusion**: The infrastructure is correctly configured. The 502 errors are likely due to Cloudflare tunnel connection issues or edge caching, not Nginx routing problems.
|