Fatal error locked out of back end

  • Resolved boatgalley

    (@boatgalley)


    2 years, 7 months ago

    Twice recently I have had a problem where I am locked out of the back end of my site. Front end, everything looks okay.

    When I check the error logs on my server, it’s a PopupMaker file that is causing the problem. The first time this happened, I restored a backup and disabled PopupMaker as I didn’t have time to troubleshoot.

    This afternoon, I finally had time. Once again, couldn’t get into the back end and had the same error message. Again, restored to overnight backup and all is well.

    All I can think is that PopupMaker auto-updated and put the corrupt file back in. HOWEVER, I don’t have ANY plugins set to auto-update! And definitely not PUM.

    I have now deleted the plugin so that it can’t try to auto update and go to a corrupt version.

    Since I can’t get into the back end once the problem occurs, I can’t tell you much about it, and unfortunately once I restored the site, the error logs are gone.

    Any ideas of what is happening? I like PUM, want to have it on the site, but I can’t have it where it keeps locking up.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter boatgalley

    (@boatgalley)

    Further investigation shows that PUM is NOT the culprit, although I am getting this warning, which I figured you’d want to know about:
    2022/04/24 17:16:25 [error] 5892#5892: *175 FastCGI sent in stderr: "PHP message: PHP Warning: Invalid argument supplied for foreach() in /www/theboatgalley_129/public/wp-content/plugins/pum-mailchimp-integration/classes/Provider.php on line 543" while reading response header from upstream, client: 34.69.65.166, server: staging-theboatgalley.kinsta.cloud, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php7.4-fpm-theboatgalley.sock:", host: "staging-theboatgalley.kinsta.cloud:22339", referrer: "https://staging-theboatgalley.kinsta.cloud/"

    Bel

    (@belimperial)

    Hi @boatgalley

    Thank you for getting in touch.

    We’re sorry that you can’t access the backend of your site.

    Popup Maker does not include code to prevent accessing the site or backend.

    On the other hand, WordPress handles auto-updating of a plugin.

    While the PHP warning indicates no merge fields were found for a list, and it uses the staging site instead of the live site.

    Can you try going into your Popup Maker settings > Mailchimp tab and click the refresh button? It may take a moment to complete.

    We also suggest updating the URLs of your live site to use the live URL instead of the staging URL – https://staging-theboatgalley.kinsta.cloud.

    Please, could you reach out to your hosting to assist you updating the URLs?

    We hope that helps. Please let us know how it goes.

    Thank you!

    Thread Starter boatgalley

    (@boatgalley)

    I spent several hours working with my hosting company today.

    We copied the live site to staging for testing and that is why you see the error from the staging.

    I finally totally deleted the plugin and add-ons, then downloaded and reinstalled new copies and got a new API code from MailChimp.

    So far, so good. I’ve done the same thing on the live site as well. We’ll see what happens.

    Bel

    (@belimperial)

    Hello @boatgalley

    Thank you for updating us.

    Please do let us know if the issue reoccurred.

    You may also send us a message at our website. Here’s how to:

    1. Go to https://wppopupmaker.com/support/#submit-a-support-ticket
    2. Click Other Support
    3. Fill in the form
    4. Click SUBMIT

    Here’s a screen capture for your reference: https://share.wppopupmaker.com/geudGzB4

    Thank you!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Fatal error locked out of back end’ is closed to new replies.