• Resolved Ryan Townley

    (@ryantown)


    I have at least a couple clients having trouble saving Web Stories, via the Web Stories plugin by Google, due to false positive blocks by Wordfence.

    Learning mode does not help and they are not showing up in Live Traffic. Only deactivating Wordfence solves the problem. I would like to figure out what to add for the parameters in Allowlisted URLs.

    The action URL is: /wp-json/web-stories/v1/web-story/149706/?_fields=status%2Cslug%2Clink%2Cpreview_link%2Cedit_link%2C_links%2Cembed_post_link%2Cstory_poster%2Cdate%2Cmodified&_embed=wp%3Alock%2Cauthor%2Cwp%3Apublisherlogo%2Cwp%3Aterm&_locale=user

    The error when saving a web story is: Failed to save the story. Response is not a valid JSON response.

    The header response is: {“code”:”rest_forbidden”,”message”:”Sorry, you are not allowed to do that.”,”data”:{“status”:401}}

    Happy to provide any other details needed. Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @ryantown, thanks for reaching out!

    Whilst Learning Mode might not be effective in some cases, the absence of any block in Live Traffic suggests that this might not be a false-positive.

    I would deactivate?“Prevent discovery of usernames through ‘/?author=N’ scans, the oEmbed API, the WordPress REST API, and WordPress XML Sitemaps”?in Wordfence > All Options > Brute Force Protection > Additional Options and try saving Web Stories again.

    Let me know how you get on!
    Peter.

    Thread Starter Ryan Townley

    (@ryantown)

    Thanks @wfpeter, that solved it!

    I’ll reach out to the Web Stories team since it would be ideal to be able to keep that option enabled.

    Thread Starter Ryan Townley

    (@ryantown)

    Just following up with some thoughts from the Web Stories team. They think it’s a bug in Wordfence…

    First of all, the “Response is not a valid JSON response.” error message does not really match the “rest_forbidden” response, as that looks like valid JSON. So that’s a bit confusing.

    Second, this WordFence option does not seem to be doing what it’s supposed to do. It should not interfere with these /wp-json/web-stories/v1/web-story requests which are simply required for saving stories to the database. So this is clearly a bug in WordFence. Please report this to WordFence, as this is not a bug in the Web Stories plugin.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Web Story saving blocked’ is closed to new replies.