Complianz Privacy Suite

Fatal Error: This website is experiencing technical difficulties…

Aert Hulsebos

Aert Hulsebos


Popular articles

Creating the Legal Hub

Have you seen our new Legal Hub? If not, have a look before reading this instruction article. We created the legal hub to centralize our

Read More

Placeholders for iFrames

From 4.6.11 onwards, you can also use consent shortcode wrappers. An instruction can be found here. You’re able to block iFrames with Complianz with the

Read More
Share on facebook
Share on twitter
Share on linkedin

Sometimes the Complianz scan or generating documents might cause an issue, whereby WordPress will give an error, for example:

This website is experiencing technical difficulties…

To fix this issue…

This could be quickly resolved by changing the folder name of Complianz with FTP.

  1. Login to your FTP client, and search for your WordPress installation root.
  2. Go to /wp-content/plugins/ and change the name of the Complianz folder. This will deactivate Complianz, and all features.
  3. Read our the below section on “To troubleshoot this issue…” to debug the issue and contact support.

If you’re hosting company provides you with cPanel or similar, you can use file manager as well.

To troubleshoot this issue…

we can do the following. You should check if your memory limit, the memory needed to complete a task, is sufficient. To increase your memory, please add or change the following line in your wp-config.php file. This file is located in the root folder of your website and can be accessed via (S)FTP or your hosting file manager.


define(‘WP_MEMORY_LIMIT’, ‘256M’);

If this does not solve the issue, it might be caused by numerous things. To check the underlying cause of the error, or at least get a more detailed hint of the issue. We will need to know what happened during these “technical difficulties.”

For this, we need debug information from a debug log, which is a WordPress feature and can be enabled by editing the following line in your wp-config.php file

define(‘WP_DEBUG’, false);

*/ Should be changed to below /*

define(“WP_DEBUG”, true);
define(“WP_DEBUG_DISPLAY”, false); //prevents errors from showing on the front-end
define(“WP_DEBUG_LOG”,     true);

Recreating the issue

To log the issue, you will need to recreate the problem so it can be logged by your new WordPress feature. When you have recreated the issue, please go to the folder:

root/wp-content/ and find the new file “debug.log”.

You can send the file with the below support form to our team so they can have a look. Please describe your issue clearly, with added screenshots if possible.

NB. After debugging is done, please revert back to the previous state as debugging can affect your website performance.

Recent articles