Support » Plugin: AWS for WordPress » Causing error 500 with UM

  • Resolved rrradiogirrrl



    Just wanted to let you know that in my setup on

    WPENGINE Php 7


    WP Rocket (plugin js excluded) and Ultimate Member running, the Polly plugin caused the UM plugin to malfunction. Specifically, UM was no longer able to reach its own API resources because of a 500 network error.

    Disabling the Polly plugin fixed it…

Viewing 3 replies - 1 through 3 (of 3 total)
  • This was the request path:



    :status: 500
    Content-Type: text/html; charset=UTF-8
    Pragma: no-cache
    Date: Tue, 24 Jul 2018 13:28:04 GMT
    Cache-Control: no-cache, must-revalidate, max-age=0
    Server: cloudflare
    Expires: Wed, 11 Jan 1984 05:00:00 GMT

    Other processes also stopped working:

    XMLHttpRequest cannot load /um-api/route/um_ext!um_notifications!core!Notifications_Main_API/ajax_check_update/a6543339e2 due to access control checks.

    Plugin Contributor tstachlewski


    Hi rrradiogirrrl,
    I will look into it after the release of next version. Thx for the info.


    Plugin Contributor tstachlewski


    This should be fixed now. If not, please let me know.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Causing error 500 with UM’ is closed to new replies.