01 / Understand the situation
What may be getting in the way
A 502 usually means one server could not get a valid response from another. Hosting, a reverse proxy, an application crash or a recent deployment can be involved. Domain expiration and SSL warnings need different investigations. The exact error and when it started matter more than guessing which provider is at fault.
02 / Start here
Concrete first steps
- Save the exact error, affected URL and approximate start time. Test on mobile data as well as your shop Wi-Fi to separate a local connection issue from an outage.
- Check hosting status and recent DNS or deployment changes. Keep the last working backup untouched. Do not change email DNS records just to fix the website.
- Put a working phone number or alternate booking route on channels you control. Before a rollback, verify it will not erase new orders or submissions.
03 / The work
How Blaze can help
Blaze can trace the request from DNS and Cloudflare through hosting and the application, restore an available clean version and test forms after recovery. If the host is the recurring weak point, we can plan a controlled move with backups, monitoring and a rollback instead of an emergency nameserver change.
See website, search and workflow services, or tell us what is happening so we can scope the right work before quoting.
04 / Check the result
What to verify before calling it done
Recovery means more than the home page opening. Check key service URLs, HTTPS, contact delivery and booking from a phone. A follow-up incident note should identify what failed and how a repeat will be detected.
Questions you may still have
Before you decide
Do I need a complete rebuild to fix a 502?
Not necessarily. An origin outage, broken deployment or resource limit may be repairable without changing the design. We diagnose the failure first.
Should I turn off Cloudflare?
Not as a first step. The origin may still be down, and changing DNS can introduce another problem. Check the origin and proxy configuration with a rollback available.
Can you promise a recovery time?
No fixed recovery time is promised before access and the cause are understood. Share the affected URL and recent changes so we can agree on the next step.