Proof
Case studies based on real production problems.
Examples of production infrastructure work we support, including performance improvements, migrations, infrastructure reviews, application stability, caching and DNS issues, backup restore failures and security hardening.
Production infrastructure work we support.
Each case study explains the business problem, the technical approach and the type of outcome we aim for when supporting production systems.
Selected case studies
Twelve production problems we can help solve.
Use these case studies to understand how we approach common infrastructure, application and platform support requests, and which service route fits each situation.
Real client IP restored through a reverse proxy to app containers
A containerised application behind a host-level reverse proxy could not see the original visitor IP. The fix required checking forwarded headers, trusted proxy behaviour, routing and application logging together.
- Reverse proxy routing
- Real client IP forwarding
- Containerised app support
Cloudflare SSL redirect loop after a DNS cutover
A website can become unreachable after a DNS or Cloudflare change even when the server is still running. The priority is to identify whether the problem sits in DNS, Cloudflare SSL mode, origin configuration or application redirects.
- Cloudflare/DNS
- Redirect loop and HTTPS failure
- Fixed technical fix
Python SaaS app returning 502 errors behind NGINX and Gunicorn
A SaaS team does not always need a full DevOps transformation. Sometimes the priority is to restore a broken production app, understand the failure and document a safer deployment path.
- Python web app
- NGINX/Gunicorn 502 errors
- Incident recovery
MariaDB slow queries causing SaaS dashboard timeouts
Slow database queries can make a SaaS application unreliable even when the web server is still running. This case study outlines a careful approach to production database performance issues.
- MariaDB performance
- Slow queries and dashboard timeouts
- Database tuning
Linux server disk full causing database and website failures
A full disk can quickly turn into a production outage. Websites may fail, databases may stop writing, backups may break and emergency cleanup can be risky if the wrong files are removed.
- Linux server
- Disk full and service failures
- Emergency recovery
Docker Compose stack failing after a server migration
A Docker Compose application may work on the old server but fail after a migration. This case study outlines how we stabilise a broken move without guessing at production changes.
- Docker migration
- Containers restarting after move
- Production recovery
WordPress malware cleanup followed by security hardening
A compromised WordPress site can affect trust, search visibility and revenue. Cleanup is only part of the work; the site also needs the entry point reviewed and obvious hardening gaps addressed.
- WordPress security
- Suspicious redirects and risk
- Security review/fix
Improving CDN hit rates for a custom web application
A custom web application can still put too much load on the origin when cache headers, CDN rules and application routes are not aligned. This case study outlines how we improve cache efficiency safely.
- CDN performance
- Cache hit rate and origin load
- Web app caching review
Slow WooCommerce checkout caused by database and PHP-FPM pressure
Slow checkout, admin screens and product pages can directly affect sales on a revenue-generating WooCommerce store. This case study outlines how we approach a production performance issue that needs careful diagnosis and safe changes.
- WooCommerce performance
- Checkout, admin and database bottlenecks
- Fixed-scope technical fix
AWS bill, security and backup risks found during an infrastructure review
Not every AWS problem starts with an outage. Some environments become expensive, inconsistent and hard to trust over time. This case study outlines how a review turns unclear cloud risk into a practical action plan.
- AWS review
- Cost, security and backup risks
- Practical action plan
AWS S3 AccessDenied errors breaking application uploads
S3 permission problems can break uploads, backups or application workflows without the whole system going offline. The fix requires checking IAM, bucket policy, object ownership and application configuration together.
- AWS S3
- Uploads and backups failing
- AWS technical fix
Nextcloud slow uploads linked to Redis, database and storage pressure
Nextcloud performance problems often sit between application configuration, Redis locking, database load, PHP-FPM, storage and networking. This case study outlines how we diagnose the stack carefully before making changes.
- Nextcloud performance
- Uploads, Redis and database pressure
- Application/server fix
Have a similar issue?
Send the stack, symptoms, urgency and recent changes. We will suggest whether it fits emergency support, a fixed technical fix, an infrastructure review or a project quote.
Keywords
Common production support themes
Examples of infrastructure issues where clear diagnosis, safe changes and practical handover matter.