Troubleshooting "Whoops! Buffer's servers couldn't be reached" error

Seeing an error when opening Buffer, saving or scheduling a post, or uploading media? This article covers issues where Buffer does not load or respond as expected.

You may see one of the error messages below, or experience a blank, black, frozen, or endlessly loading screen; a page that will not load past login; media stuck on "Finishing up"; or an unresponsive composer that will not save or schedule your post.

"Whoops, Buffer's servers couldn't be reached to save the update, sorry about that. Would you be up for trying again?"

"Sorry. It looks like something unexpected happened. Please click here to report this to our team so we can get this fixed up."

"An unknown error has occurred, please get in touch if this persists."

"Well, this is embarrassing…"

"Failed to fetch (graph.buffer.com)"

Most of these issues can be resolved quickly. Start by checking whether Buffer is experiencing an outage. If everything is operational, work through the browser troubleshooting steps below and stop when the issue is resolved.

In this article:

  1. First, check whether Buffer is down
  2. What these errors mean
  3. Ad blockers and pop-up blockers
  4. Browser privacy and tracking settings
  1. Clear your cache and cookies, then hard refresh
  2. Update your browser, or try a different one
  3. Turn off your VPN, antivirus, or security software
  4. Images or videos are stuck on “Finishing up” or will not upload

First, check whether Buffer is down

Before troubleshooting on your device, check our status page to see whether Buffer is experiencing an outage.

  • If an incident is listed, such as servers being unreachable, pages not loading, channels failing to load, or a blank calendar or dashboard, the issue is on our side. You do not need to change anything on your device. Wait until the incident is resolved, then refresh Buffer. Posts already in your queue will resume sending once service is restored.
  • If no incident is listed, the issue is likely related to your browser, network, or device. Continue with the troubleshooting steps below.

What these errors mean

Buffer displays a general error message when something interrupts the app before it can finish loading, saving, or publishing. Because the same message can have several causes, the right fix depends on what is affected.

Common causes include:

  • A temporary issue on Buffer's side: This may be an outage or a brief service hiccup. Check our status page first, then try again once the issue is resolved.
  • A browser, network, or device issue: Ad blockers, privacy or security extensions, VPNs, outdated browsers, or cached data can interfere with Buffer. The troubleshooting steps in this article cover these issues.
  • A post, channel, or social network issue: If only one post or channel is affected and the rest of Buffer works normally, the issue is more likely related to that post, connection, or channel.

💡 Tip: If a message like "An unknown error has occurred, please get in touch if this persists" appears once and the action works after you refresh or retry, it was almost certainly a temporary hiccup, rather than an issue with your account.

Ad blockers and pop-up blockers

Ad blockers and pop-up blockers are a common cause of “servers couldn’t be reached” and “unknown error” messages. They can block the requests Buffer needs to load or save your work.

To test this, open Buffer in an incognito or private window and try again. If the error does not appear, an ad blocker or pop-up blocker is likely causing the issue. Common examples include:

    • Disconnect.me
    • uBlock Origin
    • AdBlock Plus
    • Ghostery
    • Privacy Badger

To fix it, add Buffer to the allowed sites (the "allowlist" or "exceptions") for that extension, then reload Buffer and try again.

Browser privacy and tracking settings

If a private window does not resolve the issue, your browser’s built-in privacy or tracking protection may be blocking Buffer. Add Buffer as an exception using the instructions for your browser below, then reload the page and try again.

Firefox

Firefox's Enhanced Tracking Protection can interfere with Buffer. To add an exception:

  1. In Firefox, open the browser menu and choose Options.
  2. Select Privacy & Security.
  3. Under Enhanced Tracking Protection, click the Manage Exceptions button.
  4. Add the exception "www.buffer.com".

Chrome

If you use Chrome, Enhanced Safe Browsing may interfere with Buffer, especially the Buffer browser extension. To turn it off:

  1. Enter this into your Chrome URL or address bar: chrome://settings/security
  2. Scroll down to Safe Browsing.
  3. If Enhanced protection is on, turn it off.

📝 Notes:

  • If Enhanced Safe Browsing is enabled in your Google Account, it is also enabled in Chrome when you are signed in and when the sync is turned on without a custom passphrase.
  • After you turn it off, the change may take up to 24 hours to apply.
  • Standard Safe Browsing will continue protecting you from dangerous websites, downloads, and extensions.

For more information, see Chrome’s documentation.

Safari

Safari's cross-site tracking prevention can block features in Buffer. To turn it off:

  1. In Safari, click Safari, then Settings.
  2. Select the Privacy tab and uncheck the "Prevent cross-site tracking" box.

Opera

Opera's tracker blocking can interfere with Buffer. To adjust it:

  1. In Opera, click Opera, then Settings.
  2. Select the Basic tab, then under Privacy Protection, either toggle Block Trackers off or click Manage Exceptions and add buffer.com as an exception.

Clear your cache and cookies, then hard refresh

If Buffer loads but appears broken, keeps showing errors, or does not update, outdated cached files may be the cause. Start with a hard refresh, then clear your browser’s cache and cookies if needed. Clearing cookies will sign you out of most websites, so have your Buffer login details ready.

  1. Do a hard refresh to reload the page from scratch: press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac).
  2. If that does not help, clear your browser's cache and cookies for the last 24 hours, then close and reopen the browser and sign in to Buffer again.

Update your browser, or try a different one

An outdated browser can prevent Buffer from loading correctly, resulting in a blank or black screen, broken layout, or other display issues. Buffer works best on the latest version of Chrome, Firefox, Safari, Edge, or Opera.

  • Update your browser: Install the latest version, then reload Buffer. Older browser versions may not support the current app.
  • Try another browser: If Buffer works elsewhere, the issue is likely related to the original browser’s version, extensions, or settings.
  • Try another device or network: If Buffer works on another device or Wi-Fi connection, the original device or network is likely causing the issue.

Turn off your VPN, antivirus, or security software

A VPN, corporate firewall, or security software can block Buffer's connection to its servers, which shows up as "servers couldn't be reached," a page that will not load, or uploads that fail. To test this:

  1. Temporarily disconnect any VPN, then reload Buffer and try again.
  2. Temporarily pause security or antivirus software and browser security extensions (for example, McAfee WebAdvisor or Bitdefender), then try again.
  3. If you are on a work or school network, try the same action on a different network, such as a personal hotspot, to see whether a firewall is the cause.

If turning one of these off fixes the problem, add Buffer to that tool's list of allowed or trusted sites so you do not have to disable it each time.

Images or videos are stuck on “Finishing up” or will not upload

If media remains on "Finishing up" or "being processed", stalls during upload, or a post stays on "will be sent shortly", Buffer has not finished processing or sending the file.

You may see the following error messages:

“Upload stalled for 60 seconds, aborting.”

“Upload failed for [filename]. This looks like a network error. The endpoint might be blocked by an internet provider or firewall.”

“Media not ready to share yet.”

Try these steps in order:

  1. Wait a few minutes, then try again. Large files can take longer to process, and temporary interruptions often clear on the next attempt. If a post is stuck sending, wait a few minutes before retrying it from your queue.
  2. Check the file format and size. Large files or videos encoded in formats such as HEVC (H.265) may not process correctly on some devices or browsers. Re-export the video as an MP4 using H.264, or the image as a JPG or PNG, then upload it again. See Attaching images, videos, and other media to your posts.
  3. Rule out network or security restrictions. A network or firewall error usually indicates that something is blocking the upload. Turn off your VPN, try another network, and temporarily disable security software or browser extensions before trying again.
  4. Try a hard refresh or a different browser. If the upload remains at 0%, try a hard refresh or upload from another browser.

📝 Still need help? Send us an email at hello@buffer.com, and our Advocacy team will be standing by to assist!

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.