Stuck on Website scan

  • shustus

    (@shustus)


    6 months, 3 weeks ago

    The website scan is stuck at 58% forever (couple of weeks now). Is there a way to restart the scan?

    Note: I’ve created a ticket via the Complianz support portal a week ago, but haven’t received an answer (not even a confirmation – so I have no idea if this is being looked at).

    • This topic was modified 6 months, 3 weeks ago by shustus.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Antonio Candela

    (@antoiub)

    6 months, 2 weeks ago

    Hello @shustus ,

    Thank you for reaching out.

    I’m sorry to hear that. Yes, it is possible to restart the scan, but if it’s not working it will probably get stuck again. You can disable the new scanner in Settings > APIs > Disable Website Scan, this will reset the scan.

    That said, we are currently testing some releases and are just a few steps away from publishing a branch on GitHub for testing, so affected users can try it out.

    Regarding your ticket, if you haven’t received a confirmation it means it was not submitted correctly, as we always send a confirmation and are on track with all support requests.

    I will update this thread with the GitHub branch soon. Thank you for your patience.

    Best regards,
    Antonio

    Thread Starter shustus

    (@shustus)

    6 months, 1 week ago

    Thanks for the info Antonio.

    I disabled the website san via the API menu. What I did not expect is that a little while the scan suddenly completed:

    So to me it looks like the scan was not disabled at all (even tho the API screen tells me it is). When I click “Clear Cookies” the scan repeats. With mixed results, sometimes if finds 100 cookies, sometimes 120, etc.

    And what’s weird also, it that is finding cookings of plugins I don’t have on my website (i.e., Elementor, Pixel your Site etc.). These cookies are not found when using online cookie scanner tools like https://cookie-script.com/ etc. Clearing the browser cache or using a private browser mode does not have an effect.

    • This reply was modified 6 months, 1 week ago by shustus.
    • This reply was modified 6 months, 1 week ago by shustus.
    Plugin Support Antonio Candela

    (@antoiub)

    6 months, 1 week ago

    Hello @shustus ,

    Thank you for your feedback.

    When the Website Scan is disabled via the API menu, Complianz automatically falls back to the local iframe scanner (the previous scanning method). This is expected behavior.

    Because the local scanner works by loading your site inside an iframe, its results can vary depending on factors like browser or server caching. That’s why you may sometimes see slightly different cookie counts (e.g., 100/120) or cookies from plugins you’ve previously used or that left cached assets behind.

    I hope this clears things up! When using the local scanner, it’s usually best to run the scan in an incognito window to get the most accurate results. That said, I’ll update you as soon as we have the branch ready with the possible fix. Thank you for your patience.

    Best regards,
    Antonio

    • This reply was modified 6 months, 1 week ago by Antonio Candela. Reason: typo
    Thread Starter shustus

    (@shustus)

    5 months, 1 week ago

    Hi @antoiub, just checking in to ask if a fix is underway,

    Thanks,
    Shustus

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.