Docs    Facebook    Troubleshooting

Facebook API Error Message Reference

A reference table of Facebook API error messages and how to fix each one, including PPCA and access token errors.

Would you like to find out what a Facebook feed error message means and how to fix it?

In this guide, we’ll walk you through the error messages Custom Facebook Feed can show and the steps that fix each one. All you need is the text of the error from your feed or your WordPress dashboard. To find it quickly, press Ctrl+F (Cmd+F on a Mac) and search for part of the message or its error number.

Before you get started, make sure Custom Facebook Feed is installed and activated on your site. The steps below apply to the free and paid versions. Some error titles can differ between plugin versions.

Here is what we will cover.

Where Do Error Messages Appear?

When Custom Facebook Feed can’t get your posts from Facebook, it shows the error in a few places. Visitors never see these messages.

  • On your site, an admin who is logged in sees a box above the feed that says This message is only visible to admins. To read the full text, click the Click to show error link. The text includes a link to this guide.
  • In your WordPress dashboard, a notice can appear with a short title such as Error 190: Invalid Access Token. To reach the matching entry here, click Learn More in the notice. When reconnecting your account would help, the notice also has a Reconnect Account button.
  • In Tools » Site Health, the Custom Facebook Feed check moves to the critical issues and says Your Custom Facebook Feed is experiencing an error. For details, see our guide on checking Facebook Feed errors in WordPress Site Health.
  • In the feed settings, a source that has a problem is marked Source Invalid.

Each error heading below is the text of an error message, so you can match it to what you see. Where the error text includes an ID, it is shown here as a row of underscores.

If your error isn’t listed below, or the steps don’t fix it, contact support and include the full text of the error.

Facebook Feed Error Messages

PPCA Error: Due to Facebook API changes it is no longer possible to display a feed from a Facebook Page you are not an admin of.

This error means the Access Token your feed uses doesn’t come from an admin of the Facebook Page. It can also mean the token is for the right Page but is missing some permissions. While the problem lasts, your feed stops updating and shows its saved posts. In your WordPress dashboard, the notice for this error is titled PPCA Error: Page not managed by you.

The fix is to connect the Page again, using a Facebook account that has a role on it.

If you have a role on the Page, or can ask someone who does

You may still get this error with a role on the Page, such as admin or editor. In that case the source was set up with an Access Token for a different Page, or with some permissions left out. To fix it, follow these steps.

  1. Go to Facebook Feed » All Feeds and click Edit for the feed with the error.
  2. Click Settings, then Sources, then Change.
  3. In the Update Source panel, click Add New and go through the connection process.
  4. When you’re sent to Facebook, follow the prompts to approve the connection.
  5. Back in the plugin, select the Page as the source and save your feed.

If a Page or permission is missing

If your Page isn’t listed, or the error stays, the Smash Balloon app may only have access to some of your Pages or permissions. You change this on Facebook, not during the connection.

  1. While you’re logged in to Facebook as your personal profile, go to Business integrations in your Facebook settings.
  2. Find the Smash Balloon WordPress app and click View and Edit.
  3. For each permission that has a list of Pages, select the Pages you want to connect, or select all of them. Do this for Read content posted on the Page, Read user content on your Page and Show a list of the Pages you manage.
  4. Click Save.
  5. In WordPress, go to Facebook Feed » Settings and click Add Source. You can now select the missing Pages.

For more on this, see our guide on Pages that aren’t listed after authorizing the plugin.

The connection between the Smash Balloon app and your Facebook account is a single connection. If you manage more than one Page, select all the Pages you want to display each time you connect. This applies even when they are for different websites. You choose the Page for each feed in the last step.

If you are building the site for a client

Someone with a role on the Page has to make the connection. If you manage the website for a client, ask them to give you a role on the Page. Then add the Page as a new source with your own Facebook profile. For the other options, see our guide on connecting a Facebook Page for a client.

There is no limit on how many Facebook Pages you can connect to the plugin.

Error 4: Rate Limit Reached

This error means your feed has made too many requests to Facebook in a short period. Facebook is temporarily limiting requests from your site.

You don’t need to reconnect your account, because a rate limit doesn’t break the connection. The feed tries again on its own and keeps showing its saved posts in the meantime. To make this less likely, ask for new posts less often by increasing the caching time.

  1. Go to Facebook Feed » Settings and click the Feeds tab.
  2. In the Caching section, increase the time between checks for new posts to one hour or more.
  3. Click Save Changes.

If the error keeps coming back, see Error: (#32) Page request limit reached below. It explains what decides how many requests your Access Token can make.

Error 10: Permission Missing

This error means your Access Token is still valid but it’s missing a permission the feed needs. It may also be titled Error 10: Permission Denied.

You don’t need to start over. To fix it, open the source for the feed and approve the missing permission.

  1. Go to Facebook Feed » All Feeds and click Edit for the feed with the error.
  2. Click Settings, then Sources, then Change.
  3. Click Add New and go through the connection process.
  4. When you’re sent to Facebook, approve every permission it asks for.
  5. Back in the plugin, select the Page as the source and save your feed.

If the error message mentions Public Content Access, it is the PPCA Error above.

Error 18: Request Throttled

This error means Facebook has temporarily throttled, or slowed down, requests from your account. Your feed tries again on its own, so you don’t need to do anything right now.

If the error doesn’t clear after a while, contact support.

Error: (#32) Page request limit reached. Type: OAuthException. Code: 32

Your Access Token is making too many requests. This happens when one Access Token is used for a lot of different feeds, on your own website or across several sites. For example, everything may be connected to your personal Facebook account. You don’t need to reconnect your account.

The best first step is to ask Facebook for new posts less often. To do this, increase the caching time so the plugin makes fewer requests.

  1. Go to Facebook Feed » Settings and click the Feeds tab.
  2. In the Caching section, increase the time between checks for new posts to one hour or more.
  3. Click Save Changes.

Once the Access Token works again, which is usually within a few hours, you can lower the caching time. Two things decide how low it can go.

  • How active your Facebook Page is. Facebook sets the request limit for an Access Token from how many engaged users the Page has. An engaged user is anyone who clicked on your Page or its content in the last 24 hours. For every engaged user, your Access Token gets a limit of 4,800 requests in a rolling 24 hours. A Page that isn’t very active likely has a low limit. To raise it, even for a short time, post something that gets clicks, likes, shares or comments.
  • How many feeds use the Access Token. Five feeds make far fewer requests than 20.

For more on how Facebook limits requests, see the Facebook rate limiting documentation.

Error: (#2) Service temporarily unavailable

This error means the Facebook API may be temporarily down. Wait a few minutes and try again. You can make the plugin check Facebook again right away by clearing its caches.

  1. Go to Facebook Feed » Settings and click the Feeds tab.
  2. Click Clear All Caches.

To clear the cache for one feed only, go to Facebook Feed » All Feeds and click Edit for the feed. Then click Settings and click Clear Feed Cache.

Error: Unsupported get request. Code 100. Type: GraphMethodException

This error means Facebook can’t find or read the Page or Group ID your feed uses. The plugin may show it as Error 100: Invalid Parameter. Check each cause in the sections that follow.

You may be using a Facebook ID from a personal profile

To check, look at your page on Facebook. Profiles have Friends, and Pages have Likes. If yours has Friends, it’s a personal profile, not a Page.

Because of Facebook’s privacy policy, posts on a personal profile are protected. Most of them can’t be displayed in a feed. You may have limited success with certain posts.

If you use the profile to represent a business, organization, product or public figure, we recommend converting your profile to a Page, as Facebook recommends. Facebook’s policies don’t allow using a profile to represent something other than yourself. Once you’ve converted it to a Page, the plugin can retrieve and display all of your posts.

To use the right ID, see our guide on finding your Facebook Page ID.

Your Facebook Page may have restrictions on it

The Page you want to display has to be public. If it has an age or country restriction, people have to sign in to Facebook to see it. That also means your Page can’t be crawled and indexed by search engines.

To check, sign out of Facebook and visit your Page. If Facebook makes you sign in to see it, the Page has a restriction.

To remove the restrictions, sign in to Facebook and open the settings for your Page. Then remove any Country Restrictions and Age Restrictions. Once they’re removed, the plugin can access and display your posts.

Your Facebook Page might not be published

A new Facebook Page isn’t public until you publish it. If it isn’t published, the plugin can’t get your posts. If Facebook still offers a Publish my page button or something similar for your Page, publish it there.

Your feed may include a sales post

A bug in the Facebook API can cause this error when a feed includes buy and sell posts. Facebook returns no information for these posts. The plugin has a setting that works around the bug. Your posts display. The pricing details are left out because the API doesn’t provide them.

  1. Go to Facebook Feed » All Feeds and click Edit for the feed with the error.
  2. Click Settings, then Advanced.
  3. In the API Bug Workarounds section, turn on Sales Posts Fix.
  4. Save your feed.
  5. Go to Facebook Feed » Settings and click the Feeds tab. Then click Clear All Caches. This makes the feed get its posts from Facebook again, with the fix on.

Error 190: Invalid Access Token

Error 190 is one of the most common reasons the plugin is unable to connect to the Facebook API. It means Facebook no longer accepts the Access Token your source uses. When Facebook gives a reason, the plugin can show a more specific title. Depending on your plugin version, it can be one of these.

  • Access Token Expired, for a session that has expired.
  • Password Changed, when the Facebook password was changed.
  • App Not Authorized, when the Smash Balloon app isn’t authorized for the account.
  • Security Checkpoint, when Facebook put a checkpoint on the account.
  • Account Unconfirmed, when the account isn’t confirmed.
  • Invalid Access Token, for any other cause.

For most of these, reconnecting your Page fixes it. If your title is Security Checkpoint or Account Unconfirmed, the account owner has to log in to Facebook first. They clear the checkpoint or confirm the account. Then reconnect.

If the title is Page Access Lost, reconnecting won’t help. This happens when the account lost its administrator, editor or moderator role on the Page. It also happens when the Page now requires Two Factor Authentication and the account hasn’t turned it on. To fix this, restore the role or turn on Two Factor Authentication. Then check the feed again.

To reconnect your Page, first update Custom Facebook Feed to its latest version. If you can’t update it, see our guide on updating a Pro plugin. Then follow these steps.

  1. Go to Facebook Feed » Settings and remove the connected account by clicking the red trash icon.
  2. Click Save Changes.
  3. Click Add Source. Then click the blue Connect button and go through the connection process again.
  4. When you’re sent to Facebook, approve every permission it asks for. If a Page or permission is missing, follow the steps for missing Pages and permissions in the PPCA entry.
  5. If a feed still shows the error, go to its Settings, then Sources. Next, select the newly connected source.
  6. Save your feed.

If you’re using your own Access Token, you can test it in the Facebook Access Token Debugger. Next, paste the token and click Debug. The token isn’t valid if you get an error, if the Page ID is missing, or if the pages_read_engagement permission is missing. In that case, reconnect.

Error: Error validating application. Application has been deleted. Type: OAuthException. Code: 190

Facebook may have made a platform change that stopped the plugin from connecting. The fix is to get a new Access Token of your own.

  1. Update Custom Facebook Feed to the latest version. If you can’t, see our guide on updating a Pro plugin.
  2. Go to Facebook Feed » All Feeds and click Edit for the feed with the error.
  3. Click Settings, then Sources, then Change.
  4. Follow the connection process. This gives you your own Access Token.

Error: Error validating access token: Session has expired on ____

The Access Token you use has expired, or wasn’t extended correctly. This is the same fix as Error 190 above. Your plugin needs to be on its latest version. You can check the latest versions in the Pro change log and the free plugin change log. Then update your source for the feed under Settings » Sources.

Error: Error validating Access Token. The session has been invalidated because the user changed their password or Facebook has changed the session for security reasons. Type: OAuthException. Code: 190

The password on your Facebook account was changed, so your Access Token is no longer valid. To refresh the source, reconnect your account.

  1. Go to Facebook Feed » All Feeds and click Edit for the feed.
  2. Click Settings, then Sources, then Change.
  3. Follow the connection process. This gives you a new Access Token.

Error: Invalid OAuth access token

The Access Token is incorrect, invalid or expired. If you use your own Access Token, test it in the Facebook Access Token Debugger. Next, paste the token and click Debug. The token isn’t valid if you get an error, if the Page ID is missing, or if the pages_read_engagement permission is missing.

To fix it, update the plugin to its latest version. Then update your source for the feed. The steps are the same as for Error 190 above.

Error 200: Permission Missing

This error means the Access Token doesn’t have the permissions this feed type needs. It may also be titled Error 200: Permissions Error. You don’t need a full reconnection. To fix it, approve the permissions again with the same steps as for Error 10 above.

Error: Unsupported get request. Object with ID ‘____’ does not exist, cannot be loaded due to missing permissions, or does not support this operation.

Your Access Token doesn’t have permission to read this data. This is often because the Page ID is wrong. For help, see our guide on finding your Facebook Page ID.

Error: No posts available for this Facebook ID

The feed connected, but there were no posts to show. There are three common causes.

  • Your Page has restrictions on it.
  • Your Page might not be published.
  • Your Page may not have any posts the plugin can display. If your Page is new, it may not have any. Notices such as “changed the cover photo” or “created a page” are filtered out. To fix this, create a new post on your Page and check the feed again.

Error: An unknown error occurred. Or, Error: An unexpected error has occurred.

Facebook sometimes sends back an “unknown error” for one of three reasons. The request may ask for too much data, its API may have a temporary problem, or its API may have a bug. Check each cause below.

You may be requesting too many posts

Facebook limits how much data one request can ask for. If your post limit is set very high, lower it. API Post Limit is set to Automatic by default, which lets the plugin choose how many posts to get from Facebook. Manual lets you set that number yourself.

  1. Go to Facebook Feed » All Feeds and click Edit for the feed.
  2. Click Settings, then Advanced.
  3. Next to API Post Limit, choose Manual and enter a lower number.
  4. Save your feed.

Facebook’s API may have a temporary issue

Wait a few minutes and try again. You can clear the plugin’s caches to make it check Facebook again. See Error: (#2) Service temporarily unavailable above for the steps.

A bug in Facebook’s API for comments

You may see Error: An unknown error has occurred. Type: OAuthException. This can come from a bug in Facebook’s API when comments are requested. By default, the plugin asks for comments in the same request as your posts. The Load Comments with JavaScript setting works around the bug by loading comments with JavaScript instead.

  1. Go to Facebook Feed » All Feeds and click Edit for the feed with the error.
  2. Click Settings, then Advanced.
  3. In the API Bug Workarounds section, turn on Load Comments with JavaScript.
  4. Save your feed.
  5. Go to Facebook Feed » Settings and click the Feeds tab. Then click Clear All Caches. This makes the feed get its posts from Facebook again, with the fix on.

Facebook’s API may fail on certain posts

Facebook’s API can also return an unknown error for certain posts. By default, the plugin asks for each post’s story tags along with the post. The Story Tags Fix setting leaves the story tags out of the request, which works around the error.

  1. Go to Facebook Feed » All Feeds and click Edit for the feed with the error.
  2. Click Settings, then Advanced.
  3. In the API Bug Workarounds section, turn on Story Tags Fix.
  4. Save your feed.
  5. Go to Facebook Feed » Settings and click the Feeds tab. Then click Clear All Caches. This makes the feed get its posts from Facebook again, with the fix on.

Error: Server configuration issue

The plugin needs a few basic PHP modules to get your posts from Facebook. Most servers have them turned on. If they are off, that may be the cause of this error. You can check them in the plugin.

  1. Go to Facebook Feed » Support.
  2. Scroll to System Info and click Expand.
  3. In the ## SITE/SERVER INFO: ## section, look at PHP allow_url_fopen, PHP cURL and JSON.
  • If JSON is No, JSON isn’t running on your server. Ask your web host to turn it on. The plugin needs it. So do many others.
  • If both PHP allow_url_fopen and PHP cURL are No, both are off in your server’s php.ini file. If you’re comfortable editing that file, you can turn on one or both. If not, ask your web host to turn them on.
  • If only one of them is No, the plugin still works. If PHP cURL is the one that’s off, image resizing and GDPR features will not work.

A server security setting may be blocking the connection

If the settings above are fine and your Page works in the demo, a server security setting may be the cause. It may stop your site from connecting to the Facebook API. Your hosting support team can fix this. Next, ask them to confirm api.facebook.com and graph.facebook.com aren’t blocked.

The request method may be failing

Because of your server’s setup or security settings, the method the plugin uses to get your posts can fail. It may fail every time or only once in a while. The plugin switches to another method. On rare occasions it doesn’t. Your host blocking access to api.facebook.com or graph.facebook.com is the first thing to rule out.

Also try lowering the API Post Limit.

See Please reduce the amount of data you’re asking for below for the steps.

Error: Unauthorized source IP address

This error means Facebook has blocked your web server’s IP address. It most likely happened because someone else on the same IP address broke Facebook’s Terms of Service. On a budget hosting plan, your server is probably shared with hundreds or thousands of other websites. They all share the same IP address. If Facebook blocks it, every site on the server is blocked.

The only way around this is to contact your web hosting company and ask them to change your IP address or move you to a different server.

Error: Please reduce the amount of data you’re asking for, then retry your request

The Facebook API doesn’t like it when too much data is requested at once. If the number of posts, or your post limit, is set to 100 or more, try lowering it to see whether posts appear.

  1. Go to Facebook Feed » All Feeds and click Edit for the feed.
  2. Click Settings, then Advanced.
  3. Next to API Post Limit, choose Manual and enter a lower number. The maximum is 100.
  4. Save your feed.

If you’re still having trouble displaying your posts after trying these steps, contact support for help.

That’s it! You now know how to match a Facebook feed error message to its fix and follow the steps that clear it. Next, see our guide on getting alerts when your Facebook feed stops updating.

support

Couldn’t find your answer in the docs?

Contact Support