New version (3.0.0) crashed backend

  • Hello.

    I just updated to the new version of the plugin and it crashed the wp-admin of the site so I can’t access my backend.
    It returns a 520 Error.

    What’s wrong and how do I fix this as soon as possible?

    Please let me know.
    Thanks.

    [moderator note: Please don’t multi-post in rapid succession. The system flags you as a spammer. Breathe, compose, read, breathe, think, edit, post. If you forgot something, you can edit your original post for (I think) up to 15 minutes.]

Viewing 15 replies - 1 through 15 (of 17 total)

  • Hi,

    Generally when you see a CloudFlare 502 we’re showing that because thats what we received from your origin: https://support.cloudflare.com/hc/en-us/articles/218378978-What-should-I-do-after-seeing-a-502-or-504-gateway-error-on-my-site-

    Are there any errors in your error log?

    Thanks,
    John

    OMG something is wrong with this update. It took all my websites down on update!

    @jwineman Same here, ngnix error 520.

    @kilmanagh Using FTP (or a file manager) delete or rename the plugin folder. This will disable the plugin and your website will work again.

    You all realize that your plugin went from 14K compressed to over 4 meg? That’s a massive beast of a plugin

    Can you guys answer the following questions please:
    Do you have SSL Enabled on CloudFlare? If so what is it set to?
    Do you have an SSL certificate installed on your origin server?

    • This reply was modified 8 years, 5 months ago by jwineman.

    1) No SSL is not enabled
    2) Yes but SSL is not active. Strictly HTTP.
    Error log posted at new thread.

    • This reply was modified 8 years, 5 months ago by Kilmanagh.

    Same issue here, nginx error 502: https://i.imgur.com/3UQCZmx.png . If I disable the Cloudflare plugin (using ftp) it starts working again.

    I have an SSL certificate (Let’s Encrypt) on my server. I get the same error if I bypass Cloudflare (by changing the hosts file).

    Bryan

    (@bryan-bittner)

    Definitely seems to be something wrong with this update. I’m getting a 502 error after updating also. Works fine after disabling the plugin via SFTP.

    I have an SSL cert on my server and SSL enabled on cloudflare set to “FULL”

    Thread Starter catmaniax

    (@catmaniax)

    It’s a 520 error, not 502.

    Thread Starter catmaniax

    (@catmaniax)

    Kilmanagh, delete it through FTP to get your site back, that’s what I did.
    I will not be updating it until it gets fixed.

    Thread Starter catmaniax

    (@catmaniax)

    I’m using the free Cloudflare SSL set to Flexible.

    Thread Starter catmaniax

    (@catmaniax)

    Actually it’s about 13MB unzipped, but that’s ok by me if they introduce new features.
    The thing is that too many people already are experiencing broken sites after the update and that needs to be fixed asap.

    Hi,

    We disabled HTTP2/Server Push in 3.0.2 does upgrading to this version fix your errors?

    Thanks,
    John

    Thread Starter catmaniax

    (@catmaniax)

    Hello, 3.0.2. seems to be working but I’m getting Connection Not Secured although I have the SSL ON.
    The HTTPS Protocol Rewriting is missing so I suppose that’s the issue here.
    I need it to display secure (green padlock) like the old version, please fix or advice.

    Thanks!

    Hi,

    We removed protocol rewrite in 3.x because we’re in the process of rewriting it and its not ready yet. We plan on adding it back in the next few weeks once our rewrite is stable.

    Thanks,
    John

Viewing 15 replies - 1 through 15 (of 17 total)
  • The topic ‘New version (3.0.0) crashed backend’ is closed to new replies.

Tags