Wordfence alert

  • JB_Walton
    July 14, 2026 at 2:57 am

    Since approximately one week, all of my websites using GP Premium report the following error during Wordfence scans:

    “Attempt to assign property ‘plugin’ on false [gp-premium]”

    The normal WordPress update check works, all licenses are active, and GP Premium updates are detected normally. The error only occurs during the Wordfence update check.

    I found a support topic from June 2024 with the same error. At that time, GeneratePress explained that it was caused by a server migration and temporary API unavailability.

    Could there currently be an intermittent issue with the GP Premium update API? It also appears that the updater does not check whether the API response is false before assigning the plugin property.

    Kind regards,
    Jan

  • David
    July 15, 2026 at 1:50 am

    Hi Jan,

    we haven’t had any know outages that would replicate the issue experienced back in 2024. And we have not had any other reports of this ( as yet ).

    Could you confirm that the sites have a validated license key registered for the GP Premium plugin?
    If it it does, then it could be a badly cached option. If you’re familiar with the wp_options

    Then: search wp_options for a key matching edd_sl_failed_http_ and delete it.

    Then retry.

    Let me know

    regards

    David

  • JB_Walton
    July 15, 2026 at 4:59 am

    Hi David, I tried deleting the license and re-activating it.
    Unfortunately, that did not work and I’ve got a 403 error.

    Next things I tried:
    curl -I https://generatepress.com

    The reponse was a http/2 403
    This happens from my production and my staging server.

    The curl from my home-ip address gives: http/s 200.

    I think that my servers are blocked, perhaps by a firewall?
    I wil give some extra info in the private information.

    Regards,
    Jan

  • Alvind
    July 15, 2026 at 6:15 am

    Hi Jan,

    Could you try the Secondary API method outlined in this article and see if that resolves the issue?

    https://docs.generatepress.com/article/license-key-activation-issues/#403-forbidden-when-activating-license-key

  • JB_Walton
    July 15, 2026 at 7:01 am

    Hi,

    I tried the secondary API and that works.
    Thanks for that.
    Problem is, that I have to use this for every website!
    Are you working on a solutions for the default license key activation on this problem?

    Regards,
    Jan

  • Alvind
    July 15, 2026 at 7:01 pm

    I believe the team currently investigating the root cause of this issue, but for now, the Secondary API method is the only available workaround.

    What other issues are being caused by Wordfence flagging the error? Is it preventing the plugin update from completing successfully?

  • JB_Walton
    July 15, 2026 at 11:05 pm

    Hi Alvind,

    The regular activation of the license key is working now with the secondary API.
    However, the daily Wordfence Scan does still report this issue:

    An error occurred during the update check while scanning: Attempt to assign property “plugin” on false [gp-premium] Wordfence cannot detect whether this plugin/theme is up to date. This may be caused by a PHP compatibility issue within the plugin.

    Every website I’ve made is using GP-Premium and Wordfence free for security.
    This results in an e-mail report including the issue for the update check of GP-Premium.

    I logged some information on the call, that Wordfence actually made and received.
    See private info, at the bottom.

    Regards,
    Jan

  • Alvind
    July 16, 2026 at 5:16 pm

    Can you confirm whether you’ve already checked for the wp_options entry that David mentioned and removed it?

  • JB_Walton
    July 17, 2026 at 12:06 am

    Hi Alvind,

    The first website I checked the wp_options and removed the items with ‘edd_sl_failed_http_’ and found 2 of them.
    I removed both, but that did not change the Wordfence alert.

    I now removed the wp_options items from my second website and added the secondary api.
    Running the Wordfence scan did now finish without the gp-premium alert.

    So the secondary api / wp-options (edd_sl_failed_http_) removal seems to have solved it.
    The regular license activation and the wordfence scan alert.

    However, I did the same on my third website.
    The license activation works, but the wordfence scan results in the alert for gp-premium.

    Kind regards,

    Jan

Viewing 9 posts - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.