A Large WordPress Migration Times Out Before the Database Finishes
Move a large WordPress database safely when browser imports time out, with integrity checks, compression and a controlled cutover.
SPECIALIST DIAGNOSTIC GUIDES
Find the failing layer.
Repair the website safely.
Hands-on guides for outages, broken releases, login failures, redirects, certificates and missing assets across modern web platforms.
START WITH THE VISIBLE SYMPTOM
Guidance organised around real incidents.
Choose the symptom closest to what you see, collect the evidence and follow a controlled route to verification.
01
Blank pages and server errors
Trace the failure across the browser, hosting, runtime, database and application before changing production.
Explore the guides 02Broken releases and migrations
Compare the deployed artifact, configuration, permissions and data state with the last known-good release.
Explore the guides 03Login and access failures
Separate identity, session and permissions problems without granting unnecessary administrator access.
Explore the guides 04Redirect and certificate faults
Find the first incorrect handoff across DNS, TLS, CDN, proxy and application routing.
Explore the guides 05Missing content and assets
Follow one record or asset from source and build through cache, CDN and browser delivery.
Explore the guides 06Slow or unstable websites
Measure server time, transfer, rendering and third parties under one repeatable test.
Explore the guidesExplore: Admin Media Frontend
Administracio Mitjans Frontend
Administrador Medios Frontend
Administrador Mitjans Frontend
Base Dades I Dades Wordpress
Base Datos Y Datos Wordpress
Connectors Temes Actualitzacions
Database Wordpress Data
Errores Visibles Http Php
Errores y diagnóstico
Errors & Diagnosis
Errors i diagnòstic
Errors Visibles Http Php
Hosting Dns Ssl
Http Php Visible Failures
Manteniment Recurrent
Mantenimiento Recurrente
Migraciones Copias Seguridad
Migracions Copies Seguretat
Migrations And Backups
Plugins Temas Actualizaciones
Plugins Themes Updates
Recurring Maintenance
Read the guide ↗
WordPress Enters a Redirect Loop After Enabling HTTPS
Fix a WordPress HTTPS redirect loop by aligning site URLs, reverse-proxy detection, Cloudflare SSL mode, server rules and cookies.
A Corrupted WordPress Database Table Breaks Only One Feature
Diagnose and repair one corrupted WordPress MySQL table using error evidence, backup, engine-aware checks and feature-level verification.
A WordPress Migration Changes URLs Inside Content and Widgets
Repair wrong URLs in WordPress content and widgets after migration without damaging serialized options or replacing unrelated text.
A DNS Change Sends Some Visitors to the Old WordPress Server
Manage split traffic after a WordPress DNS change by checking authoritative records, TTL, IPv6, caches, old-server writes and reconciliation.
WordPress Core Update Stops Halfway and Leaves Maintenance Mode
Recover a WordPress core update stuck in maintenance mode by checking active processes, disk, permissions, checksums and database upgrade.
WordPress Works Before Migration but Fails on the New Server
Diagnose a WordPress site that worked before migration but fails on its new server, without changing several variables at once.
WordPress Works by IP Address but Not by Domain Name
Diagnose WordPress reachable by server IP but not its domain through DNS, virtual host, SSL, canonical URLs and proxy configuration.
WordPress Admin Redirects Back to the Login Page
Fix a WordPress admin login loop by tracing authentication cookies, domain and HTTPS settings, cache, plugins and user sessions.
A WordPress Plugin Update Breaks the Entire Site
Recover WordPress after a plugin update using PHP evidence, safe deactivation, trusted rollback and full feature validation.
WordPress Permalinks Return 404 After a Hosting Change
Fix WordPress permalink 404s after hosting migration by checking rewrite rules, Apache/Nginx configuration, document root and canonical URLs.
CSS Changes Do Not Appear After Updating a WordPress Site
Find why WordPress CSS changes do not appear by checking loaded asset versions, cascade, generated files, CDN/page cache and deployment paths.