Support » Plugin: Complianz - GDPR/CCPA Cookie Consent » Every scan results in 502 Bad Gateway

  • Resolved puregraphx

    (@puregraphx)


    We are building another site for one of our clients and we always use the Complianz plugin, mostly without any issues.
    We have been working on this site a few days now without any errors, but as soon as we let the plugin do a scan, immediately we get a 502 Bad Gateway. When we refresh, it’s gone, but when we start another scan, again 502 error.
    We are on the latest Complianz plugin version.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Contributor jarnovos

    (@jarnovos)

    Hi @puregraphx,

    I suspect that there is a conflict with one of your other active plugins/custom scripts. Do you have any other plugins/JavaScript active on the site that you suspect might be able to cause this?

    Disabling the other plugins one-by-one would likely be the best course of action here.

    Kind regards,
    Jarno

    Thread Starter puregraphx

    (@puregraphx)

    Hi @jarnovos
    When we disable all plugins except Complianz, then we can do 5 consecutive scans without a 502 error, but as soon as we enable any other plugin, the problems occur, doesn’t matter which plugin.
    We first tried with the Elementor combo, 502, then with only Duplicate Page or Enable Image Replace which are rather small plugins, again 502.

    Plugin Contributor jarnovos

    (@jarnovos)

    Hi @puregraphx,

    You can add the following lines to your wp-config.php file to generate a debug log & enable script debugging.

    define( 'WP_DEBUG', true ); 
    define( 'WP_DEBUG_LOG', true ); 
    define( 'SCRIPT_DEBUG', true );

    We can have a look at the server logs. In any case, our Cookie Scan works by turning the scanned pages into iFrames and checking which Cookies are detected. As a result, this functionality should not really be able to break anything.

    Kind regards,
    Jarno

    Thread Starter puregraphx

    (@puregraphx)

    I have enabled logging, but there is absolutely no debug.log to be found.

    Plugin Contributor jarnovos

    (@jarnovos)

    Hello @puregraphx,

    The default location of the logfile is usually “/wp-content/debug.log/”. You could also change the WP_DEBUG_LOG line I mentioned earlier to set the desired location to save the file instead, example below:

    define( 'WP_DEBUG_LOG', '/tmp/wp-errors.log' );

    Let me know if you have any updates.
    Kind regards,
    Jarno

    Thread Starter puregraphx

    (@puregraphx)

    Yesterday, we disabled Varnish cache on our VPS, after that we were unable to reproduce the error. We have enabled Varnish, but still don’t see the issue. Maybe Varnish was not the cause? Maybe disabling Varnish fixed it/something, can’t be sure.

    Plugin Contributor jarnovos

    (@jarnovos)

    Hi @puregraphx,

    Thank you for the update.

    If this happens again and Varnish cache clearing/disabling seems to help, just let us know and we can have a closer look at what the exact cause could be. I’ll mark this thread as resolved for now.

    Kind regards,
    Jarno

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Every scan results in 502 Bad Gateway’ is closed to new replies.