Home > Docs > GDPR Cookie Consent > GDPR Cookie Consent Plugin (CCPA Ready) – Troubleshooting Guide

GDPR Cookie Consent Plugin (CCPA Ready) – Troubleshooting Guide

Last updated on June 14, 2023

Error 1 : Unable to load cookie scanner. Scanning will not work on local servers

Kindly make sure that you are not checking from localhost as the scanner does not work in the localhost environment.

In case you are getting this error message from a publicly hosted site, please save the below-given code snippet in .php file format (for eg: ipinfo.php) and host it on your site root directory.

Then enter the URL your domain/ipinfo.php in the browser and check what IP it’s returning (for eg: webtoffee.com/ipinfo.php)

Once you run that code, you will get your actual IP address and the name of the key in which it can be accessed. Then, copy the below code snippet to your active theme’s functions.php after modifying the code with the right key name as it appears in the output of the above code.

Error 2 : Unable to load cookie scanner

  1. Please make sure below database tables are created on the site. Go to phpmyadmin and verify the same.
    • wp_cli_cookie_scan_url
    • wp_cli_cookie_scan_cookies
    • wp_cli_cookie_scan
    • wp_cli_cookie_scan_categories
  2. Alternatively, you can check in the error logs to find if any table creation errors are logged. To check,
    • Add below line to wp-config.php.
      define( ‘WP_DEBUG’, true );
      define( ‘WP_DEBUG_LOG’, true )
    • Deactivate and activate the plugin once.
    • Look for any database table creation error messages logged in to wp-content/debug.log within your site’s filesystem.
    • If not created, please make sure that the user has table creation permissions.

Error 3 : 0 cookies found as result

Since the scanner accesses the site from a private window/incognito window, make sure that the cookies are present and set in your site from an incognito window. Open the site in a private window and open the developer console and check the following:

  1. Make sure that all the database tables mentioned below are created.
    • wp_cli_cookie_scan_url
    • wp_cli_cookie_scan_cookies
    • wp_cli_cookie_scan
    • wp_cli_cookie_scan_categories
  2. Ensure that your site is publicly accessible without any htaccess protection.
  3. If you are using any maintenance mode or coming soon mode plugins, please disable while scanning.
  4. Make sure that the user has database table write permission.

Error 4: Could not establish a connection with the scanner! please try again later

Some users have been experiencing the same error while using the scanner due to a curl error in WordPress. You can read all about it here. We have come up with a workaround until WordPress releases a fix for the error.
Please add the below-given code snippet to the functions.php of the active theme file to fix the issue until the next WordPress update.

If this did not fix the issue, kindly check with your hosting team and fix any curl errors in the site that could cause errors while connecting to the scanner server(Cookieyes.com).

Error 5: Doesn’t receive an email verification after creating CookieYes account.

  • Kindly check if the email address entered is valid if you are using the basic version. If using the pro version, kindly ensure that you have entered a valid email address while activating the license key. In pro, a license email is used to create an account.
  • And, yeah! please don’t forget to check your spam folder too.
  • If you have entered the wrong email address, then you will need to reset the scanner so that it asks for email address again or restart the process of account creation. In order to do so, please add this code to your active theme’s functions.php.
  • Then run the code by opening the URL “yoursite/wp-admin/?wt-reset-token”. Make sure to replace ‘yoursite’ with your site url.
  • Still, if you are facing difficulty, please contact our support team for further assistance.

Error 6: Says “Error” when clicking Connect & Scan

Kindly ensure that the plugin’s license key is active with your valid email address. If not, deactivate and activate again with same the API key and a valid email address. Preferably use the billing email address used during plugin purchase.