Operational Troubleshooting Notes

502 from https://www.renewed-renaissance.com/

These are the steps I followed on 2025-11-15 to diagnose a Cloudflare 502 Bad Gateway and bring the storefront back online.

1. Check container health quickly

• Run docker compose ps and make sure cloudflared, wordpress, db, redis, and maildev are all Up (healthy).
• If anything is down, restart with docker compose up -d --force-recreate <service>.

2. Reproduce the symptom from the public edge

curl -I https://www.renewed-renaissance.com/

Capture the cf-ray value; it helps correlate with Cloudflare logs if you open a support ticket.

3. Exercise the origin directly

curl -I http://127.0.0.1:8080/
curl -I -H "Host: www.renewed-renaissance.com" http://127.0.0.1:8080/

If you see redirects to /wp-admin/install.php, the database volume may be empty.

4. Inspect logs for root cause clues

docker compose logs wordpress --tail=200
docker compose logs db --tail=200
docker compose logs cloudflared --tail=200

5. Validate local data stores

• Check that ./db_data still contains wordpress/ tables.
• Ensure ./wordpress has the expected core files, plugins, and uploads.

6. Confirm tunnel origin target

Cloudflared currently forwards to http://192.168.1.129:8080 (see the config snippet in tunnel logs).

hostname -I
ip addr

If the IP changed (e.g., DHCP gave you 192.168.1.128), add the expected alias:

sudo ip addr add 192.168.1.129/24 dev wlx3894edb09248

7. Re-run health checks

curl -I https://www.renewed-renaissance.com/

Should return 200 or a healthy 302. Also browse wp-admin/ to verify you aren't stuck at the install wizard.

8. Document and commit

Once resolved, jot down what changed (env vars, tunnel token, DB restore) and commit updates for the next incident.