Drupal Maintenance Mode vs. an Unreachable Server: What Visitors Actually See

A branded 503 page means Drupal chose to pause; a blank browser error means the server itself stopped answering.

A branded 503 page means Drupal chose to pause; a blank browser error means the server itself stopped answering.

A quick guide to telling a stale Drupal page apart from a stale DNS lookup, and clearing the right one first.

A 403 on uploaded Drupal files traces to either file-system permissions or a mismatch between the configured and actual storage URL — not the same fix.

Composer audit should run on every CI build plus a recurring cron job, because advisory data changes even when a Drupal site's code doesn't.

Match Wednesday Drupal releases to your overnight low-traffic window and run safe updates.

Match your content, modules, and custom code to a realistic Drupal timeline before you set scope and launch dates.

Compare same-tier Drupal hourly rates by region, then add a 10-20% contingency before you sign.

Learn to test rewrites, fix .htaccess and Nginx rules, and restore Drupal clean URLs after a host move.

Configure Drupal's trusted proxies correctly so IP bans, allowlists, throttles, and security logs use the intended address.

Update Drupal's trusted host patterns with precise hostname rules and avoid unsafe wildcards during a domain migration.