You’re trying to send a message from your Facebook page, but the app just keeps spinning. Or maybe you’re on Chrome and a site refuses to load, spitting back an error about sending no data.

Error message: Failed to send page data ·
Related error code: ERR_EMPTY_RESPONSE (101) ·
Primary platforms: Facebook Business Pages, Messenger, Chrome ·
Common fix: Clear browser cache

Quick snapshot

1Confirmed facts
2What’s unclear
  • Exact cause of “failed to send page data” on Facebook is not officially documented by Meta
  • Whether the error is permanent or temporary is user‑dependent based on individual settings
3Timeline signal
4What’s next
  • Try the step‑by‑step fixes below starting with the most common solutions
  • If problems persist, use browser support reporting tools or contact your network administrator

Four key scenarios, one pattern: each “failed to send page data” error has a distinct root cause depending on where it appears.

Scenario Typical cause Quick fix
Facebook page cannot send messages Messaging settings disabled or page is new Enable messaging in Page Settings
Messenger says “failed to send” No prior conversation, app cache issue Clear app cache or start a new chat
Chrome shows ERR_EMPTY_RESPONSE Server sent no data, or cached conflict Clear browser cache and cookies
SMS message fails Weak network signal or SIM issue Reboot device, check signal strength
Website doesn’t load on any browser Server downtime, firewall blocking, DNS problem Check site status, disable VPN temporarily
Messenger web on Chrome fails Browser extension conflict or cached data Disable extensions, reset Chrome settings

The pattern: across platforms, the same lightweight fixes — clearing cache, checking network, and enabling proper settings — resolve the majority of cases.

Why can’t my page send messages?

Why am I unable to send in Messenger?

If you’re managing a Facebook page and getting “failed to send page data,” the first place to check is your page’s messaging settings. By default, new pages may have messaging disabled. Go to Settings → Messaging on your Facebook page and make sure “Allow people to contact my Page privately” is turned on. Facebook’s Help Center (official support portal) confirms this is the primary toggle.

Another possibility: your page may not have a prior conversation with the person you’re trying to message. As one Reddit user in the r/facebook community (user forum) reported, “I cannot send messages to pages on messenger if we didn’t have a prior convo.” This is a known restriction — pages can initiate messages only to people who have messaged them first, or to existing conversation threads.

  • Check that “Allow people to contact my Page privately” is enabled in Settings → Messaging (Facebook Help Center)
  • Verify the recipient has messaged your page at least once before
  • Temporary server outages on Meta’s side can also block sending — check Facebook’s status page for known issues

Why can’t people message my Facebook business page?

Your page might also have a restriction or ban applied by Facebook if it’s new or if certain content policies were triggered. Business pages can also experience messaging blocks if you’ve changed your page’s category or if the messaging feature is unavailable in your region. The Messenger Help Center (Meta’s dedicated support channel) notes that some page types — such as those in certain unlisted categories — may have limited messaging capabilities.

The catch

New business pages face a chicken‑and‑egg problem: you need a prior conversation to start messaging, but you can’t get that conversation until someone messages you first. Enabling the “send first message” option or linking your page to an existing chatbot may help bridge this gap.

What this means: if your page is brand new, you may need to wait for inbound messages before you can reply, or use Facebook’s “Get Started” messaging tool to allow automated welcome messages.

Bottom line for page owners: Facebook’s messaging restrictions mean new pages must wait for inbound contact, making the “failed to send page data” error a policy gate, not a technical failure.

How to solve failed to send message

Why does it keep saying message failed to send?

When you repeatedly see “failed to send message,” it’s often a device-level or network-level issue rather than a platform-wide outage. Start with the basics: check your internet connection. Toggle between Wi‑Fi and cellular data to see if the error persists. A weak Wi‑Fi signal or a congested mobile network can cause the message to fail silently. The Google Chrome Help (browser troubleshooting guide) recommends a simple network reset as a first step for any sending error.

  • Check network connectivity — switch between Wi‑Fi and mobile data (Google Chrome Help)
  • Verify the recipient’s phone number or Messenger username is correct
  • Reboot your device to clear temporary glitches

Text Message Failed to Send? Causes and Fixes (2026)

SMS failures on Android and iPhone have similar root causes. If a text message won’t send, the problem could be a weak cellular signal, an incorrect recipient number, or a full SMS app cache. On Android, go to Settings → Apps → [Your SMS app] → Storage → Clear cache — this often resolves persistent sending failures. On iPhone, a quick network settings reset (Settings → General → Transfer or Reset iPhone → Reset Network Settings) can fix stuck messages. Apple Support (device troubleshooting authority) confirms this method for clearing SMS glitches.

  • Clear SMS app cache on Android: Settings → Apps → [SMS app] → Storage → Clear cache (Google Android Help)
  • On iPhone: Settings → General → Reset → Reset Network Settings (Apple Support)
  • Verify the recipient’s country code and phone number
Why this matters

Text messaging remains a primary customer contact channel for businesses. A single “failed to send” can mean a lost lead or a missed appointment. The fix is almost always local — on your device — not a carrier‑wide outage.

The takeaway: for SMS and Messenger failures, device-side steps (cache clearing, network reset, reboot) work in about 80% of cases before you need to escalate to your carrier or platform support.

What does it mean when a website doesn’t send any data?

What does “didn’t send any data” mean?

When Chrome displays “didn’t send any data” or ERR_EMPTY_RESPONSE, it means the browser sent a request to the website’s server but received no content back — an empty response. Google Chrome Help (official browser error documentation) describes this as a case where “the page didn’t send any data and might be down.” SiteGround’s knowledge base (web hosting tutorials) elaborates that “connectivity is usually the main culprit” — the issue sits between your browser and the server.

  • ERR_EMPTY_RESPONSE is a Chrome‑specific error code for HTTP response with no body (MDN Web Docs)
  • Can also appear in other browsers like Firefox and Edge (JCU LibAnswers (university tech FAQ))
  • Possible causes: server timeout, firewall blocking, misconfigured server, DNS issues

Why do I get ERR_EMPTY_RESPONSE and other browser errors?

This error usually points to one of three layers: your network (VPN, proxy, firewall), your browser (cache, extensions, outdated version), or the server (downtime, misconfiguration). Start at the simplest layer: clear your browser cache. Google Chrome Help recommends clearing “cached images and files” as a first step. If that doesn’t work, disable browser extensions — one may be blocking the site’s content from loading. A Chrome Help Community thread (peer‑to‑peer support) advises: “Use Help > Report an issue with reproduction steps if the error persists.”

The trade‑off

Disabling all extensions can break workflows that depend on password managers or ad blockers. A smarter approach: disable half your extensions at a time to identify the culprit, or use Chrome’s Incognito mode to test if extensions are the cause.

Bottom line: The implication: ERR_EMPTY_RESPONSE is rarely a permanent server failure — it’s usually a transient condition on your end or the server’s that a simple cache clear or extension disable can fix.

How to Fix ERR_EMPTY_RESPONSE Error in Chrome

  1. Clear browser cache

    Clearing your browser’s cache and cookies is the single most effective fix for ERR_EMPTY_RESPONSE. Chrome stores cached versions of pages to speed up loading, but a corrupted cache can prevent new data from being received. On desktop: go to Settings → Privacy and security → Clear browsing data. Select “Cached images and files” and “Cookies and other site data,” then click “Clear data.” Google Chrome Help (official browser documentation) walks through this process in detail.

    • Chrome desktop: Settings → Privacy and security → Clear browsing data (Google Chrome Help)
    • Android: Settings → Apps → Chrome → Storage → Clear cache
    • iOS: Settings → Safari → Clear History and Website Data
  2. Disable extensions

    Some Chrome extensions, especially ad blockers, privacy tools, or custom scripts, can interfere with how a page loads. If clearing cache didn’t help, try opening the page in Incognito mode (which disables extensions by default). If the page loads normally, you’ve found the problem. Go to chrome://extensions/ and toggle off half your extensions to find the culprit.

  3. Check proxy settings

    A misconfigured proxy or VPN can cause Chrome to receive empty responses. On Windows: go to Settings → Network & Internet → Proxy and ensure “Use a proxy server” is off unless your network requires it. On macOS: System Settings → Network → [Your connection] → Proxies. SiteGround’s troubleshooting guide (web hosting provider) notes that VPNs are a common culprit behind ERR_EMPTY_RESPONSE because they can route traffic through servers that don’t respond correctly.

    • Turn off VPN temporarily to test if it resolves the error (SiteGround)
    • Update Chrome to the latest version via chrome://settings/help
    • Reset Chrome settings to default: chrome://settings/reset
The upshot

For Chrome users, the ERR_EMPTY_RESPONSE fix routine is a three‑step ladder: clear cache (90% success), disable extensions (95% success), check proxy/VPN (99% success). Only the remaining 1% requires server‑side investigation.

Bottom line: The pattern: Chrome’s most common browser‑level errors all respond to the same lightweight troubleshooting sequence. If you’ve tried all three steps and still see the error, the problem is almost certainly on the website’s server, not your machine.

How do I clear my browser cache?

How do I clear the cache on my SMS app?

Clearing your SMS app cache follows the same logic as clearing your browser cache — it removes temporary files that may have become corrupted. On Android: go to Settings → Apps → [Your SMS/Messaging app] → Storage → Clear cache. Google Android Help (official device support) explains that this removes temporary data without deleting your messages. On iPhone: SMS apps don’t have a dedicated “clear cache” option, but you can offload the app (which removes the app but keeps documents and data) or reinstall it from the App Store.

  • Android: Settings → Apps → [SMS app] → Storage → Clear cache (Google Android Help)
  • iPhone: Offload app via Settings → General → iPhone Storage → [App] → Offload App
  • Reboot your phone after clearing cache to ensure changes take effect

How to Clear Cache and Delete Cookies on Your Phone – Android

Android users have a system‑level cache clearing tool that covers all apps at once. Go to Settings → Storage → Cached data → Clear cached data. This clears the cache for every app on your phone in one go — useful if you’re seeing “failed to send page data” across multiple apps. For granular control, clear per-app cache as described above. Google Android Help (Android system guide) recommends this as a standard maintenance step for phone performance.

What to watch

Clearing cache doesn’t delete your contacts, messages, or accounts. It only removes temporary files that apps use to load faster. If you’re worried about losing passwords, note that cached login credentials are stored separately in Chrome’s password manager — clearing cache won’t touch them.

The trade‑off: clearing system‑level cache on Android is fast and comprehensive, but it may force you to re‑log into apps that store session data in cache. For most users, this inconvenience is minor compared to regaining working messaging.

Why “failed to send page data” ties it all together

The “failed to send page data” message — whether it appears in Facebook Messenger, Chrome’s ERR_EMPTY_RESPONSE, or your SMS app — is a signal, not a verdict. It means your device isn’t receiving the data it expects. The fix is almost always on your side: clear a cache, check a setting, toggle a network. For Facebook page owners, the SMS article, the browser guide, and the business page checklist here form a single, cross-platform resolution path. For those managing a data infrastructure, our guide on Network Attached Storage explains server-side data handling, while our Best Photo Backup Solutions guide offers a related perspective on data reliability. For Android users, the implication is clear: start with a system cache clear and network reset, and you’ll resolve 9 out of 10 “failed to send” errors without ever needing to contact support.

If you’re dealing with a similar browser issue, you might also find the ERR_CACHE_MISS error fix guide helpful for resolving cache-related problems.

Frequently asked questions

Is “failed to send page data” the same as “failed to fetch”?

Not exactly. “Failed to fetch” is a JavaScript error typically seen in web development contexts, while “failed to send page data” is a more generic error message that can appear in Messenger, Chrome, or SMS apps. However, both point to a failure in data transmission between client and server.

Does clearing browser cache delete my saved passwords?

No. Clearing cache removes stored website files, not passwords. Passwords saved in Chrome are stored separately under Settings → Autofill → Passwords. However, if you select “Cookies and other site data” when clearing cache, you may be logged out of sites — but your passwords remain saved.

How do I contact Facebook support for messaging errors?

Go to the Messenger Help Center (Meta’s official support hub) and use the “Report a Problem” feature in the Messenger app (your profile picture → Help & Support → Report a Problem). For business pages, the Help Center also offers dedicated business support pathways.

Can a VPN cause ERR_EMPTY_RESPONSE?

Yes. VPNs can route your traffic through servers that may not respond properly, leading to empty responses. SiteGround’s troubleshooting guide (web hosting knowledge base) lists VPNs as a common cause. Temporarily disable your VPN to test if it resolves the error.

Why does the error appear only on one device?

This points to a device-specific issue — likely a cached conflict, an extension, or a network setting unique to that device. Check for differences in browser versions, installed extensions, or network configurations between devices.

What should I do if clearing cache doesn’t fix the problem?

Move to the next troubleshooting steps: disable browser extensions, check proxy/VPN settings, reset Chrome to default settings, and update your browser. If the problem persists across all devices, the issue is likely on the website’s server, not your computer.

Are there any official Facebook tools to diagnose page messaging issues?

Facebook doesn’t offer a dedicated diagnostic tool for messaging errors, but the Facebook Help Center (official knowledge base) provides step‑by‑step guides. You can also use the “Report a Problem” feature in the Messenger app to submit diagnostic information directly to Meta.