• Resolved billyudi

    (@billyudi)


    It appears WordFence is blocking a POST action I need to take to update and close tickets on the uCare Support plugin. I’ve tried learning mode and whitelisting the query parameters (granted I might not be setting that up correctly).

    If I disable WordFence the support plugin the functionality works. Any help on setting this up correctly?

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

    (@wfpeter)

    Hi @billyudi, thanks for getting in touch.

    I’d definitely have expected Learning Mode to resolve this one for you, as it’s quite common for actions like updates on content managers or support/forums to have their requests blocked as false-positives. Did you attempt to close tickets during the period the firewall was in Learning Mode? Did they fail then too, or work and then go back to failing once the firewall had been returned to Enabled and Protecting?

    To create an allowlisted URL manually in Wordfence > All Options, your input has to match exactly the request(s) made when uCare Support is performing GET/POST requests. The “network” tab in the Browser Console usually needs to be inspected during an attempted form/button submission to see which type of request is made, what the parameters are, and whether it’s actually a “Query String”, “POST Body” or ”Header” that needs to be picked from the dropdown list.

    Let me know what you find out.

    Thanks,

    Peter.

    Thread Starter billyudi

    (@billyudi)

    Thanks for the reply. It is still in learning mode and they now seem to be hit or miss. Sometimes they work, sometimes they don’t.

    It says it is a POST in the network tab in the browser console. Here are the parameters:
    wp-admin/admin-ajax.php?action=support_update_ticket&agent=3&status=closed&priority=0&id=68594&ticket-properties=

    Do I add those parameters to the whitelist individually like request.body[action] and request.body[agent] etc. or is there a way to add them all like request.body[action,agent,status,priority,id,ticket-properties]?

    Thanks again!

    Plugin Support wfpeter

    (@wfpeter)

    Hi @billyudi,

    You will have to specify each parameter individually but there may be one in particular that’s triggering the false-positive, hence why you’re seeing hit and miss results. In this case, adding that one specific query string parameter should be enough although requires slightly more testing to identify to identify.

    Thanks,

    Peter.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘500 Error admin-ajax.php’ is closed to new replies.