Revive Social Docs

Appearance

Revive Social Troubleshooting Guide ​

To troubleshoot issues related to product releases or specific circumstances, follow these steps. This document will guide both you and us in collecting the necessary data for effective troubleshooting.

🔁 Initial Checks and Updates ​

Update Software ​

  • Ensure you are using the latest versions of Revive Social Free and Pro. More details about updating to the latest version can be found here.
  • Make sure you have installed a recent version of PHP.

Active Sharing ​

  • Go to Revive Social > Dashboard and make sure Sharing is active.

Identify Plugin Conflicts ​

🛠 Plugin and Configuration Checks ​

Verify the Sharing Logs ​

  • Go to Revive Social > Dashboard > Sharing Logs.
  • Verify if there is any error displayed and check whether it appears in the knowledge base.
  • If it is not between them, please share a screenshot of the logs or export the logs using the dedicated channels - pro users/ free users.

Share More than Once ​

  • If Revive Social stopped posting, go to Revive Social > Dashboard > General Settings and enable the Share more than once option to restart sharing.

Instant Sharing ​

  • To see if there is a problem with the platform or the plugin, go to Revive Social > Dashboard > General Setting****s and enable Instant Sharing Feature (Post on Publish), then enable the Use True Instant Share feature.
  • Once done, go to Posts and share a new post.
  • Check if it’s been added to the social media platform and let us know the status.

📝 Note: More details can be found here.

🧰 Detailed monitoring ​

Sharing Queue ​

  • Go to Revive Social > Dashboard > Sharing Queue.
  • Verify if posts are still displayed in the sharing queue and share a screenshot.

Cron Issues ​

  • Check if there are issues with the WordPress Cron. More details can be found here.

Install Query Monitor ​

  • If you cannot find errors, install the Query Monitor plugin and check if something appears when performing certain actions, like adding a product to the cart or saving fields.

Posts leave the queue but are not published: check for admin-ajax 403 errors ​

If posts disappear from the Sharing Queue but never appear on X (formerly Twitter) or another social account, and the Sharing Logs show no specific API error, a security plugin or firewall may be blocking Revive Social's requests to wp-admin/admin-ajax.php with a 403 Forbidden response. Because the block happens at the server level before the request reaches WordPress, Revive Social cannot log a meaningful error.

Symptoms

  • Posts move through the Sharing Queue but do not appear on X or another social account.
  • The Sharing Logs are empty or show no social API error (no "credentials wrong," "Credits Depleted," or Twitter/X error 185).
  • The issue affects scheduled sharing and is not limited to a single post.

📝 Note: If the Sharing Logs do show a credential or API error such as "Credits Depleted" or Twitter/X error 185, the cause is different. See the X-specific articles in the knowledge base for those errors.

How to check for a 403 block

  1. Open your WordPress site in a browser and log in as an administrator.
  2. Open the browser developer tools (press F12 or right-click the page and choose Inspect), then switch to the Network tab.
  3. Trigger a share using Instant Sharing (go to Revive Social > Dashboard > General Settings, enable Instant Sharing Feature and Use True Instant Share, then publish or update a post).
  4. In the Network tab, filter by admin-ajax and look for any request to wp-admin/admin-ajax.php that returns a 403 status code.
  5. Also check the logs of any active security plugin or firewall:
    • Wordfence: go to Wordfence > Firewall > Blocking or the Wordfence activity log.
    • Cloudflare: check Security > Events in your Cloudflare dashboard for blocked requests to wp-admin/admin-ajax.php.
    • Host-level WAF or firewall: contact your hosting provider or check their control panel for a web application firewall (WAF) log.

How to fix it

Whitelist or allowlist the wp-admin/admin-ajax.php endpoint in the security plugin, WAF, or firewall that is blocking it:

  • Wordfence: add a firewall rule exception or allowlist rule for requests to wp-admin/admin-ajax.php.
  • Cloudflare: create a WAF exception (bypass rule) for requests to your site's wp-admin/admin-ajax.php path, or for the specific Revive Social AJAX action if identifiable in the blocked request details.
  • Host-level WAF: ask your hosting provider to whitelist wp-admin/admin-ajax.php for your site.

After making the change, allow a few minutes and then test again using Instant Sharing or wait for the next scheduled queue run.

How to confirm the fix

  1. Go to Revive Social > Dashboard > General Settings and enable Instant Sharing Feature and Use True Instant Share if not already enabled.
  2. Publish or update a post to trigger an immediate share.
  3. Check your social account (X or the relevant platform) to confirm the post appeared.
  4. Go to Revive Social > Dashboard > Sharing Logs and verify that the share is recorded without errors.
  5. Once confirmed, you can disable Instant Sharing if you do not want posts shared on every publish.

By following these steps, you can help us diagnose and resolve issues effectively. If you encounter any difficulties, refer to this document to ensure we have the necessary information to assist you.

Contact us on the dedicated channels - pro users or free users.

Copyright (c) 2026 Revive Social