⚡ Emergency Quick Diagnostic (AEO Summary):

If your website is down or displaying errors, do not panic: (1) For WordPress White Screen of Death (WSOD), rename wp-content/plugins via FTP to isolate the conflict or raise PHP memory to 256M. (2) For WordPress hacked / malware, isolate infected files, overwrite core directories with official WordPress.org copies, reset database salts, and scan via Wordfence or WPScan. (3) For DNS_PROBE_FINISHED_NXDOMAIN, verify domain nameserver records on Cloudflare/registrar and flush local DNS (ipconfig /flushdns). (4) For 404 errors on all inner pages, resave Settings > Permalinks. (5) For Shopify payment failures, verify Indian payment gateway KYC (Razorpay/PayU) and turn off checkout test mode.

The worst support message I ever received was five words long: “The website is gone. Wedding.”

A client, a wedding photographer based out of Udaipur, had her entire commercial site — housing every client booking gallery and inquiry form for the peak December wedding season — displaying a stark, blank white screen on a Saturday morning. Her Google Ads and Instagram campaigns were firing at ₹4,000/day, driving visitors straight into a digital void.

It was a rogue auto-update of an image gallery plugin that conflicted with her theme’s custom jQuery scripts. Exactly twenty minutes of FTP access, a quick folder rename, and an updated script roll. Her site was fully operational before her coffee went cold.

That is the fundamental truth nobody tells you when your website breaks: almost every single website catastrophe is remarkably boring.

It looks like the apocalypse on your screen; but in reality, it is usually a twenty-minute fix with an established name, an identifiable root cause, and a proven recovery procedure.

This guide compiles the 25 most frequent problems we diagnose and fix on WordPress and Shopify sites across India and globally. It details what triggers each breakdown, how to resolve it step by step without breaking anything else, and when to stop Googling and call in a professional engineer.

The 5-Minute Emergency Triage (Do This First)

Before you touch a single line of code, alter server configurations, or panic-call your hosting support, run through this five-minute checklist in exact order. These five steps solve or clarify half of all perceived downtime:

┌────────────────────────────────────────────────────────────────────────────────────────┐
│                        5-MINUTE EMERGENCY TRIAGE PROTOCOL                              │
├────┬───────────────────────┬───────────────────────────────────────────────────────────┤
│ 1. │ Check if it's just you│ Open the URL on your mobile phone using 4G/5G mobile data │
│    │                       │ (completely disconnected from your office Wi-Fi).          │
├────┼───────────────────────┼───────────────────────────────────────────────────────────┤
│ 2. │ Check Domain Expiry   │ Perform a WHOIS lookup on your domain. Expired domains     │
│    │                       │ are the single most common "accidental outage" in India.  │
├────┼───────────────────────┼───────────────────────────────────────────────────────────┤
│ 3. │ Check Server Status   │ Visit your host's status dashboard (Hostinger, Kinsta,    │
│    │                       │ AWS, Cloudflare, Shopify Status). Is it widespread?       │
├────┼───────────────────────┼───────────────────────────────────────────────────────────┤
│ 4. │ Identify Recent Change│ Did someone update a plugin? Edit theme code? Add an app? │
│    │                       │ 90% of failures follow an unverified modification.        │
├────┼───────────────────────┼───────────────────────────────────────────────────────────┤
│ 5. │ Locate Your Backup    │ Verify your latest clean snapshot (UpdraftPlus, host DB   │
│    │                       │ backup, or Shopify theme export) before making any edits. │
└────┴───────────────────────┴───────────────────────────────────────────────────────────┘

Part 1: The 10 Classic WordPress Errors & Exact Fixes

1. The White Screen of Death (WSOD)

  • The Symptom: You visit your website and receive a stark, completely blank white page. Sometimes the WordPress admin dashboard (/wp-admin) is accessible; often it is blank as well.
  • The Root Cause: A fatal PHP scripting error, an incompatible plugin update, a syntax error in your child theme’s functions.php, or exhausted server memory.
  • The Exact Step-by-Step Fix:
    1. If you cannot access /wp-admin, log into your hosting cPanel or connect via SFTP.
    2. Navigate to wp-content/ and temporarily rename the folder plugins to plugins-off.
    3. Reload your website. If it immediately comes back to life, one of your plugins caused the crash. Rename the folder back to plugins, open it, and rename individual plugin folders one by one until you isolate the broken culprit.
    4. If plugins are innocent, navigate to wp-content/themes/ and temporarily rename your active theme’s folder. WordPress will automatically fall back to a default core theme (like Twenty Twenty-Four).
    5. If the screen is still white, open wp-config.php and paste: define('WP_MEMORY_LIMIT', '256M');.

2. “Error Establishing a Database Connection”

  • The Symptom: The web page displays nothing except this exact sentence in plain browser font.
  • The Root Cause: WordPress cannot authenticate with your MySQL/MariaDB database. This occurs when database credentials in wp-config.php are incorrect (common after server migrations), the database has crashed, or the hosting server’s MySQL service has hung.
  • The Exact Step-by-Step Fix:
    1. Open wp-config.php located in your WordPress root directory.
    2. Verify that DB_NAME, DB_USER, DB_PASSWORD, and DB_HOST exactly match the credentials listed in your hosting control panel.
    3. Check if the database requires repair. Add this line to wp-config.php just above the “Happy publishing” comment:
    define('WP_ALLOW_REPAIR', true);
    1. Visit https://yourdomain.com/wp-admin/maint/repair.php in your browser and click “Repair Database”.
    2. Important: As soon as repair completes, immediately delete that line from wp-config.php to prevent unauthorized visitors from triggering database locks.

3. WordPress 404 Not Found on All Pages Except the Homepage

  • The Symptom: Your homepage loads beautifully, but every blog article, product page, and service link throws an HTTP 404 “Page Not Found” error.
  • The Root Cause: Your web server’s URL rewrite rules are broken or missing. This typically occurs after switching web hosts, updating permalink structures, or having your .htaccess file wiped by an overzealous security plugin.
  • The Exact Step-by-Step Fix:
    1. Log into your dashboard and navigate to Settings → Permalinks.
    2. Do not alter any radio buttons or settings. Simply scroll to the bottom and click “Save Changes”. This single click forces WordPress to regenerate its rewrite rules and reconstruct .htaccess.
    3. If that fails, open your .htaccess file in the site root directory and paste the standard WordPress core rewrite block:
    # BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

4. HTTP 403 Forbidden Error

  • The Symptom: Browsing to your website returns: “403 Forbidden — You don’t have permission to access this resource.”
  • The Root Cause: Incorrect file/folder permissions on your Linux server, an accidental IP block triggered by security plugins (Wordfence, iThemes), or corrupted .htaccess rules.
  • The Exact Step-by-Step Fix:
    1. Audit Permissions: Via File Manager or SFTP, ensure all folders are set to permission 755 and all files are set to 644. Directories set to 777 or 600 will trigger immediate server security blocks.
    2. Rule out .htaccess corruption: Rename .htaccess to .htaccess.bak. If the site loads, regenerate a fresh .htaccess via Permalinks.
    3. Check Firewall Logs: If you entered your password incorrectly multiple times, Wordfence or Cloudflare WAF may have blacklisted your office IP. Switch to a mobile hotspot to verify.

5. DNS_PROBE_FINISHED_NXDOMAIN

  • The Symptom: The browser cannot load the website and returns DNS_PROBE_FINISHED_NXDOMAIN or “Server IP address could not be found.”
  • The Root Cause: The domain name system cannot find an active IP address mapped to your domain.
┌───────────────────────────────────────┬────────────────────────────────────────────────────────────────────────┐
│ Root Cause                            │ Exact Fix Action                                                       │
├───────────────────────────────────────┼────────────────────────────────────────────────────────────────────────┤
│ Expired Domain Name                   │ Log into GoDaddy / Namecheap / Hostinger; renew registration immediately│
│ Incomplete DNS Propagation            │ Allow 2–24 hours if nameservers were changed recently                  │
│ Missing "A" Record in DNS Zone        │ Add `@` A Record pointing to your hosting server IP (e.g. `192.0.2.1`) │
│ Local Computer DNS Resolver Stale     │ Windows: Run `ipconfig /flushdns` in CMD. Mac: `sudo dscacheutil -flush`│
│ Cloudflare SSL Handshake Loop         │ Change Cloudflare SSL mode from "Flexible" to **Full (Strict)**        │
└───────────────────────────────────────┴────────────────────────────────────────────────────────────────────────┘

6. “Fatal Error: Allowed Memory Size Exhausted”

  • The Symptom: Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 12288 bytes)...
  • The Root Cause: A resource-heavy page builder (Elementor, Divi) or e-commerce query exceeded the PHP memory ceiling allocated by your hosting package.
  • The Exact Step-by-Step Fix:
    1. Open wp-config.php and append:
    define('WP_MEMORY_LIMIT', '256M');
define('WP_MAX_MEMORY_LIMIT', '512M');
    1. If your host overrides WordPress constants, create or edit .user.ini or php.ini in your root folder:
    memory_limit = 256M
max_execution_time = 300
    1. On entry-level ₹150/month shared hosting, this error signifies that your site’s plugin stack has physically outgrown your server capacity.

7. Locked Out of WordPress Admin (/wp-admin)

  • The Symptom: You visit /wp-admin, enter the correct password, and the page reloads back to the login screen with no error, or tells you your account does not exist.
  • The Root Cause: Corrupted browser session cookies, site URL mismatches between http and https, or an administrator account altered during a malicious intrusion.
  • The Exact Step-by-Step Fix:
    1. Clear your browser cookies and site cache for your domain.
    2. If the page redirects indefinitely, verify your site URLs by adding these lines to wp-config.php:
    define('WP_HOME', 'https://yourdomain.com');
define('WP_SITEURL', 'https://yourdomain.com');
    1. If your password is rejected and email reset fails, open phpMyAdmin in your hosting panel, select your database, click the wp_users table, edit your admin username, enter a new password in user_pass, and set the function dropdown to MD5. Save.

8. Missed Scheduled Posts & Failed Automations (WP-Cron Failure)

  • The Symptom: Articles scheduled for 9:00 AM show “Missed schedule”, WooCommerce transactional emails do not fire, and automated backups never run.
  • The Root Cause: WordPress does not run a true system cron. By default, wp-cron.php only checks for queued tasks when an actual human visits the site. On low-traffic websites, background tasks fail to execute.
  • The Exact Step-by-Step Fix:
    1. Disable internal virtual cron by adding this to wp-config.php:
    define('DISABLE_WP_CRON', true);
    1. Set up a genuine Linux cron job in your hosting cPanel under Cron Jobs to trigger every 10 minutes:
    wget -q -O - https://yourdomain.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1

9. SSL Security Warnings & “Mixed Content” Errors

  • The Symptom: Browsers display “Not Secure” or a yellow warning icon, even though an SSL certificate is active.
  • The Root Cause: Your page is loaded over https://, but internal images, fonts, or stylesheets are hardcoded with legacy http:// URLs.
  • The Exact Step-by-Step Fix:
    1. Ensure both WordPress Address and Site Address in Settings → General start with https://.
    2. Install the lightweight utility plugin Better Search Replace.
    3. Search for http://yourdomain.com and replace with https://yourdomain.com across all database tables (uncheck “Run as dry run” when ready).
    4. Force HTTPS redirection in .htaccess or activate Cloudflare’s “Always Use HTTPS” toggle.

10. “It Works on Localhost” — Migration & Local Server Pitfalls

  • The Symptom: A staging site running on Local WP, XAMPP, or MAMP breaks completely when uploaded to a production server, throwing missing asset links and database collation mismatches.
  • The Root Cause: Absolute localhost file paths (http://localhost:8888/...) remaining inside database serialized strings, or MySQL version incompatibilities (utf8mb4_unicode_ci vs utf8mb4_0900_ai_ci).
  • The Exact Step-by-Step Fix:
    1. Never run a basic search-and-replace using a raw text editor on an SQL export file; it breaks PHP serialized data arrays.
    2. Always use a serialization-aware migration tool like WP Migrate Lite, All-in-One WP Migration, or Duplicator.
    3. After importing on production, immediately visit Settings → Permalinks and click Save Changes.

Part 2: “My WordPress Site Got Hacked” — Full Malware Sanitization

Website security, malware cleanup and backups illustration

Nothing induces cold sweat quite like discovering your company website has been hijacked.

Typical manifestations include:

  • Google Search displaying a red warning screen: “Deceptive site ahead” or “This site may be hacked”.
  • Japanese or pharma spam pages indexed in your Google Search Console.
  • Mobile users being redirected to shady gambling, crypto, or adult portals while desktop users see the normal site (cloaking).
  • Mysterious administrative users (e.g., admin_backup, system_wp) appearing in your user list.

How Did the Hackers Get In?

In 92% of compromised WordPress cases we remediate at RoasBodhi™, the root cause is identical: nulled, pirated “free” premium themes or plugins. Downloading an Astra Pro or Elementor Pro zip file from a telegram channel or GPL forum almost guarantees pre-packaged obfuscated PHP backdoors designed to inject spam links weeks after installation.

The Complete Emergency Sanitization Protocol

       [ STEP 1: Immediate Lockdown ]
       • Place site in Maintenance Mode
       • Take full raw snapshot (files + MySQL dump) for forensics
                  │
                  ▼
       [ STEP 2: Core Directory Reset ]
       • Delete /wp-admin and /wp-includes completely via SFTP
       • Download fresh WordPress.zip from wordpress.org
       • Upload clean /wp-admin and /wp-includes
                  │
                  ▼
       [ STEP 3: Scrub Content & Uploads ]
       • Inspect /wp-content/uploads/ for rogue .php files
         (Media folders should NEVER contain executable PHP scripts)
       • Delete all plugins and re-install fresh copies from official repo
                  │
                  ▼
       [ STEP 4: Reset Database Salts & Credentials ]
       • Change database password in hosting panel & wp-config.php
       • Generate fresh security keys from api.wordpress.org/secret-key/1.1/salt/
       • Audit wp_users table and delete unauthorized admins
                  │
                  ▼
       [ STEP 5: Request Google Review ]
       • Run deep scan with Wordfence / WPScan
       • Submit Request Review in Google Search Console Security Issues

Part 3: Fixing Crippling WordPress Speed & Core Web Vitals

Speed is not merely a cosmetic luxury; it directly impacts ad conversion rates and SEO rankings. If your website takes longer than 2.5 seconds to load, bounce rates surge past 50%.

When a WordPress site is painfully slow, the diagnosis usually boils down to five fixable issues:

  1. Subpar Hosting Architecture: Running a heavy Elementor or WooCommerce store on a ₹150/month shared server with thousands of neighboring sites. Moving to high-performance cloud hosting (Cloudways, Kinsta, or Hostinger VPS with NVMe storage) resolves 50% of latency immediately.
  2. Missing Page Caching: Without page caching, WordPress must dynamically execute hundreds of PHP scripts and database queries for every single visitor. Installing WP Rocket or LiteSpeed Cache serves static HTML snapshots in under 0.4 seconds.
  3. Bloated, Uncompressed Media: Uploading raw 4MB JPEG banners straight from a camera. Batch compress media to WebP using Imagify or ShortPixel and ensure responsive dimensions.
  4. Render-Blocking CSS & JavaScript: Defer non-critical JavaScript, delay third-party tracking pixels (Hotjar, Meta Pixel, Google Tag Manager) until user interaction, and inline critical CSS.
  5. Lack of a Global CDN: Cloudflare’s free edge network caches static assets across hundreds of global points of presence, slashing server response time (TTFB).

Part 4: Shopify Problems, Checkout Failures & Operational Fixes

While Shopify handles server infrastructure, database clustering, and security patches automatically, store owners face a distinct set of operational and transactional challenges:

11. Custom Domain Not Working / “This Shop Is Unavailable”

  • The Root Cause: Your domain’s DNS zone does not have the mandatory Shopify records, or secondary domains are not properly redirected to the primary domain.
  • The Exact Fix:
    1. In your domain registrar (GoDaddy, Namecheap, Cloudflare), set an A Record pointing @ to 23.227.38.65.
    2. Set a CNAME Record pointing www to shops.myshopify.com.
    3. Ensure no competing A records exist on your root domain.
    4. In Shopify Admin, navigate to Settings → Domains and set your custom domain as the Primary Domain. SSL certificates take 4 to 24 hours to generate automatically.

12. Payment & Checkout Failures (“Your Payment Could Not Be Processed”)

  • The Root Cause: Particularly acute for Indian D2C merchants because Shopify Payments is not natively supported in India.
  • The Exact Fix:
    1. Gateway KYC Verification: Log into your payment gateway dashboard (Razorpay, Cashfree, or PayU). Ensure business KYC, bank verification, and live API keys are fully operational.
    2. Test Mode Check: In Shopify Admin, go to Settings → Payments. Ensure your third-party payment gateway is not stuck in “Test Mode”.
    3. Currency Mismatch: Verify that your store’s primary currency matches your payment gateway’s settlement currency (INR ₹).

13. Shopify Payouts Held / Frozen

  • The Root Cause: Automated fraud algorithms detect sudden sales spikes, high chargeback volume, or unverified business tax information.
  • The Exact Fix: Check the notification banner in your Shopify Admin and your registered business email. Prepare your GST certificate, PAN card, recent company bank statements, and tracking numbers for delivered orders. Submit documentation immediately through the official support ticket.

14. Broken Theme Layout After Editing Liquid Code

  • The Root Cause: A syntax error introduced while editing .liquid templates or pasting tracking snippets.
  • The Exact Fix: Shopify features built-in file version control. Go to Online Store → Themes → Actions → Edit Code. Select the modified file (e.g., theme.liquid), click “Older versions”, and roll back to the timestamp before your edit. Rule of thumb: Always click “Actions → Duplicate” before touching theme code.

15. Apps Leaving “Ghost Code” That Cripples Store Speed

  • The Root Cause: When you uninstall a Shopify app from the dashboard, many apps leave orphaned JavaScript files and Liquid snippets behind inside your theme files.
  • The Exact Fix: Inspect theme.liquid and the snippets/ folder for files carrying the uninstalled app’s name. Remove lingering script tags or restore your theme from a clean duplicate created prior to installing the app.

16. Meta Pixel / Google Analytics 4 (GA4) Tracking Discrepancies

  • The Root Cause: Double-tracking caused by pasting raw tracking code in theme.liquid while simultaneously enabling Shopify’s native Google & YouTube or Facebook & Instagram channels.
  • The Exact Fix: Use Shopify’s native app channels (Settings → Apps and sales channels) or Customer Events Web Pixels. Delete manual tracking scripts from theme files to eliminate duplicated purchase counts.

17. Multi-Location Inventory Desync & Accidental Overselling

  • The Root Cause: Enabling multiple warehouse locations without assigning dedicated stock levels to each fulfillment center.
  • The Exact Fix: Navigate to Products, select variants, and confirm which location fulfills the order. If you operate both a physical retail store and an online storefront, unify your stock using Shopify POS to synchronize inventory in real time.

18. Storefront Exposing your-store.myshopify.com Instead of Custom Domain

  • The Exact Fix: Go to Settings → Domains, click your custom domain, and select “Set as primary domain”. Check Settings → Store details to ensure customer-facing emails and notification templates display your branded sender address.

19. Transactional & Order Confirmation Emails Landing in Spam

  • The Exact Fix: Add Shopify’s SPF authentication record to your domain’s DNS:
v=spf1 include:shops.shopify.com ~all

Configure DKIM records inside Settings → Notifications → Sender email to authorize Shopify to send authenticated emails from your custom domain. For Indian shoppers, integrate automated WhatsApp order confirmation notifications.

20. Locked Out of Shopify Store Admin Due to Two-Factor Authentication (2FA)

  • The Exact Fix: Locate the 10 emergency recovery codes generated when you first activated 2FA. If unavailable, account recovery requires submitting business registration documents through Shopify official support. Crucial preventative step: Always ensure the account owner email belongs to the business founder, not a former agency or freelancer.

21. Search Engine Indexing “Duplicate Content” via Collection URLs

  • The Root Cause: Shopify natively creates duplicate product URLs (e.g., /collections/mens-shoes/products/sneaker and /products/sneaker).
  • The Exact Fix: Edit snippets/product-grid-item.liquid to ensure all internal product cards link directly to /products/handle rather than the collection-nested path.

22. Customers Unable to Apply Multiple Discount Codes

  • The Exact Fix: Shopify allows discount combinations only if explicitly configured. In Discounts, edit your promo code and check the boxes under “Combines with” (Product discounts, Order discounts, or Shipping discounts).

23. Abandoned Cart Emails Not Firing

  • The Exact Fix: Check Settings → Checkout → Abandoned checkouts. Verify that automated emails are set to send after 10 hours (the recommended industry window) and verify that your transactional email quota is not suspended.

24. Unwanted Currency Conversion Glitches on Multi-Currency Stores

  • The Exact Fix: If using Shopify Markets, ensure exchange rate roundings are enabled and disable automatic geolocator popups that confuse returning domestic shoppers.

25. Broken Mobile Checkout Experience

  • The Exact Fix: Audit your checkout page on low-bandwidth mobile connections. Ensure address fields are streamlined (Pincode auto-fills State/City) and single-click payment options (UPI / Google Pay / Paytm) are positioned prominently at the top of the payment selection list.

Quick-Reference Website Troubleshooting Matrix

Problem / Error MessagePlatformPrimary SuspectFirst Diagnostic ActionThreat Level
White Screen of Death (WSOD)WordPressPlugin conflict / MemoryRename /plugins folder via FTPHigh 🔴
Error Establishing DatabaseWordPressBad credentials / MySQL crashCheck wp-config.php, run repair scriptCritical 🚨
404 on Inner PagesWordPressBroken .htaccess rewritesResave Settings → PermalinksMedium 🟡
403 ForbiddenWordPressFile permissions / WAF blockReset to 755/644, check IP blacklistHigh 🔴
DNS_PROBE_FINISHED_NXDOMAINBothExpired domain / bad A-recordVerify WHOIS, flush local DNSCritical 🚨
Malware / Japanese SpamWordPressNulled plugin / backdoorReplace core files, reset saltsCritical 🚨
Slow Mobile Load (>4s)BothGiant images / app bloatCompress WebP, audit uninstalled appsMedium 🟡
“This Shop Is Unavailable”ShopifyBroken DNS A-recordPoint A-record to 23.227.38.65Critical 🚨
Checkout Payment FailureShopifyGateway KYC / test modeVerify Razorpay status & live keysCritical 🚨
Layout Exploded Post-EditShopifyBroken Liquid templateRoll back to “Older version” in editorHigh 🔴

When to Stop DIY-ing and Call a Professional Developer

There is a clear, pragmatic boundary between simple operational maintenance and high-risk technical repair.

If you run an e-commerce store generating revenue or a service website handling live customer leads, every hour of downtime costs more than a professional service fee:

┌───────────────────────────────────────┬────────────────────────────────────────────────────────┐
│ Type of Website Intervention          │ Typical Cost in India (Professional Engineer)          │
├───────────────────────────────────────┼────────────────────────────────────────────────────────┤
│ Emergency Incident Triage (WSOD / 404)│ ₹2,000 to ₹10,000 per incident                         │
│ Complete Malware Sanitization & GSC   │ ₹5,000 to ₹25,000 one-time                             │
│ Speed & Core Web Vitals Optimization  │ ₹8,000 to ₹30,000 one-time                             │
│ Shopify Liquid / Custom Checkout Fix  │ ₹5,000 to ₹20,000 per task                             │
│ Ongoing Monthly Maintenance & Security│ ₹3,000 to ₹15,000 / month                              │
└───────────────────────────────────────┴────────────────────────────────────────────────────────┘

The “Never Broken Again” Prevention Checklist

Print this checklist or save it to your team’s Notion workspace:

  • Automated Off-Site Backups: Backups stored on the same server as your website are useless if the server crashes or gets compromised. Store encrypted backups on Google Drive, AWS S3, or Dropbox via UpdraftPlus.
  • Zero Nulled Software: Never, under any circumstances, install cracked or nulled themes or plugins. Buy legitimate licenses.
  • Staging Environment for Updates: Never update major plugins (WooCommerce, Elementor, core updates) directly on a live production site during business hours. Test on a staging subdomain first.
  • Strict Two-Factor Authentication (2FA): Enforce 2FA on hosting control panels, WordPress admin accounts, and Shopify logins.
  • Proactive Uptime Monitoring: Configure free external monitoring via UptimeRobot or Better Stack to ping your site every 60 seconds and alert you via SMS/WhatsApp before customers complain.

Get Expert Emergency Help from RoasBodhi™

Is your website currently hacked, throwing fatal database errors, or failing to process payments?

Don’t let downtime bleed your ad spend or ruin your search rankings. Check out our dedicated WordPress & Shopify Expert Services for emergency 2-hour bug fixes, custom web development, and 24/7 maintenance retainers:

Frequently Asked Questions

My WordPress site shows a blank white page. What should I do first?

Connect to your server via SFTP or your hosting File Manager, navigate to wp-content/, and rename the plugins folder to plugins-off. If the site immediately reloads, a plugin conflict caused the crash. You can then rename individual plugin folders inside to identify the exact offender. If that fails, raise your PHP memory limit to 256M in wp-config.php.

What does DNS_PROBE_FINISHED_NXDOMAIN mean?

It means the browser’s DNS resolver could not find any IP address corresponding to your domain name. This is almost always caused by an expired domain registration, incorrect nameservers configured at your registrar, missing A records in your DNS zone, or local ISP DNS caching issues.

My WordPress site got hacked with Japanese spam. Can it be saved without losing content?

Yes, absolutely. By replacing all core WordPress files (/wp-admin and /wp-includes) with fresh copies from WordPress.org, scrubbing /wp-content/uploads/ of unauthorized .php files, regenerating database salts, updating all passwords, and requesting a review in Google Search Console, your site and its original content can be completely restored.

Why did all my WordPress pages suddenly start showing 404 errors?

This is typically caused by broken server rewrite rules in .htaccess. Navigate to Settings → Permalinks in your WordPress admin dashboard and click the blue “Save Changes” button without altering anything. This triggers WordPress to rebuild the rewrite rules.

Why is my Shopify store returning “This shop is unavailable”?

This error almost always means your custom domain’s DNS is not properly pointing to Shopify. Verify that your root domain’s A record points to 23.227.38.65 and the www CNAME points to shops.myshopify.com. Also ensure the domain is marked as the “Primary Domain” in Settings → Domains.

Why are payments failing on my Indian Shopify store?

Because Shopify Payments does not operate in India, payments rely on third-party gateways (Razorpay, Cashfree, PayU). Verify that your gateway account has completed merchant KYC, check that “Test Mode” is deactivated in Settings → Payments, and confirm your store’s currency is set to INR.

How often should I update WordPress plugins and themes?

Update plugins and themes weekly or bi-weekly. Always take an automated backup before running updates, and test major e-commerce or page builder updates in a staging environment before pushing to live production.

FAQPage Schema (JSON-LD)

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "My WordPress site shows a blank white page. What should I do first?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Connect to your server via SFTP or File Manager, navigate to wp-content/, and rename the plugins folder to plugins-off. If the site reloads, a plugin caused the issue. If not, switch to a default theme and raise the PHP memory limit in wp-config.php to 256M."
      }
    },
    {
      "@type": "Question",
      "name": "What does DNS_PROBE_FINISHED_NXDOMAIN mean?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "It means the browser could not find any IP address corresponding to your domain name. This is typically caused by an expired domain registration, incorrect nameservers, missing A records, or stale local DNS cache."
      }
    },
    {
      "@type": "Question",
      "name": "My WordPress site got hacked with Japanese spam. Can it be saved without losing content?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. By replacing all core WordPress files with clean copies from WordPress.org, removing unauthorized PHP files from uploads, regenerating database security salts, resetting credentials, and requesting a review in Google Search Console, the site can be fully restored."
      }
    },
    {
      "@type": "Question",
      "name": "Why is my Shopify store returning This shop is unavailable?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "This error means your custom domain's DNS is not pointing to Shopify. Verify that your root domain A record points to 23.227.38.65 and the www CNAME points to shops.myshopify.com, and ensure it is designated as Primary Domain in Settings > Domains."
      }
    },
    {
      "@type": "Question",
      "name": "Why are payments failing on my Indian Shopify store?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Because Shopify Payments is not available in India, stores use third-party gateways like Razorpay, Cashfree, or PayU. Failures usually occur due to pending KYC verification, active test mode in Settings > Payments, or store currency mismatches."
      }
    }
  ]
}