Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author John Godley

    (@johnny5)

    You will need to look in your server error log to see what is causing the 500 error.

    Thread Starter tlozano

    (@tlozano)

    I can′t see any relevant info. Only a timeout but nothing else…

    2020/01/07 09:33:52 [error] 1312#1312: *5646 upstream timed out (110: Connection timed out) while reading response header from upstream, client: xx.xx.xx.xx, server: https://www.domain.es, request: “GET /wp-admin/admin.php?page=wc-status HTTP/1.1”, upstream: “fastcgi://unix:/var/run/php-www.domain.sock”, host: “www.domain.es”, referrer: “https://www.domain.es/wp-admin/admin.php?page=wc-status”

    If I return to old version, 4.5.1 and disable it and then re-enable it works fine, but 4.6.1 fails.

    Thank you

    Plugin Author John Godley

    (@johnny5)

    Your version numbers are all mixed up there. You first said it worked in 4.6.1, then that it only works in 4.5.1 and not 4.6.1

    Thread Starter tlozano

    (@tlozano)

    oh, yes, I’m sorry, but I was in a mistake… I think.
    I was in ver. 4.5.1 and all works fine. I updated it to 4.6.2 and I get the error 500 in woocommerce menu, status menu.

    I was thinking that I was in 4.6.1, but it was 4.5.1. I have not the 4.6.1 version, this is my error. I’m sorry.

    But this is the problem. With 4.5.1 it works fine, but version 4.6.2 (last one) it fails. If I restore the old versión from backup (4.5.1) it works again.

    Thank you.

    Thread Starter tlozano

    (@tlozano)

    I can try the 4.6 and 4.6.1 if works, but I have not link to those versions…
    Do you want I try 4.6 and 4.6.1 before?.
    Can you give me a link to this versions?
    Now, the last versión I have in backup is the 4.5.1.

    Thank you again.

    Plugin Author John Godley

    (@johnny5)

    I cannot reproduce the problem with WooCommerce 3.8.1. I suspect this is specific to your site, maybe because of some particular combination of plugins, or maybe even a lack of server memory.

    Your above log message suggests that something is timing out, and you may have other log files that could show exactly what the problem is.

    There is nothing in Redirection itself that would cause a particular page to return a 500.

    Thread Starter tlozano

    (@tlozano)

    Thank you for your help. I was doing some test in a clone page for test and I see that the problem was when I have a big number of pluging actives. Curiosly, with the same number of pluins active and old version or redirection plugin, 4.5.1 it works fine, but with 4.6.2 fails.

    I install a new plugin, to clean the database and it marks the table “redirection_logs” as “can be optimized”. I optimized this table and all works again with the 4.6.2 and near 40 active plugins (initial situation).

    Thank you, now all is working.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Woocommerce –> Status –> Error 500’ is closed to new replies.