I would request to check the server error log to know the detail of this error. If You don’t access of server error log, ask your hosting provider to get error log detail. I need this server error log to find the cause of this error. After that I would suggest solution to resolve this issue.
Tina
(@sunflowermom)
I am having the same problem. I had to rename my plugins directory to deactivate all plugins to be able to get back into my site. Then reactivated the plugins one by one to discover it was WooCommerce that broke my site. I cannot reactivate it at this point because it breaks my site every time. 500 internal server error as well.
I found the error logs in my Host Gator account and there’s nothing there. It’s blank.
-
This reply was modified 6 years, 1 month ago by
Tina.
-
This reply was modified 6 years, 1 month ago by Tina.
500 internal server error as well.
This for sure means there is an error happening at the server level and it should be logged. Ask the web hosts, as they must have some that are actually be populated.
hi, you means to say that I have to talk to web host to resolve this issue?
Yes, You should contact to web host to know the detail of the error. We will check and suggest the exact solution to resolve the issue.
I am also having the exact same problem. I checked with my web host and they were unable to identify anything on the hosting end.
Exact same problem (on two separate wordpress installations on different servers), narrrowed down to Woocommerce upgraded yesterday.
Both sites are throwing this error:
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@mydomain.net to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
Error logs show nothing relating to this plugin, though there are chron errors like this in the access logs on my second site (not the first):
from the SSL access log
72.29.90.27 – – [26/Mar/2018:11:51:05 -0400] “POST /wp-cron.php?doing_wp_cron=1522079465.4028739929199218750000 HTTP/1.1” 500 – “https://mydomain.net/wp-cron.php?doing_wp_cron=1522079465.4028739929199218750000” “WordPress/4.9.4; https://mydomain.net”
From the ordinary access log
72.29.90.27 – – [26/Mar/2018:21:08:04 -0400] “POST /wp-cron.php?doing_wp_cron=1522112884.6917870044708251953125 HTTP/1.1” 500 – “http://mydomain.net/wp-cron.php?doing_wp_cron=1522112884.6917870044708251953125” “WordPress/4.9.4; http://mydomain.net”
171.25.193.25 – – [26/Mar/2018:21:08:23 -0400] “GET / HTTP/1.1” 500 – “-” “Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20100101 Firefox/7.0.1”
52.91.149.230 – – [26/Mar/2018:21:09:09 -0400] “GET / HTTP/1.1” 500 – “-” “crawler (crawler.feedback@gmail.com)”
72.29.90.27 – – [26/Mar/2018:21:09:18 -0400] “POST /wp-cron.php?doing_wp_cron=1522112958.0494990348815917968750 HTTP/1.1” 500 – “http://mydomain.net/wp-cron.php?doing_wp_cron=1522112958.0494990348815917968750” “WordPress/4.9.4; http://mydomain.net”
Both sites have a logged error similar this
[Mon Mar 26 23:17:03.264423 2018] [authz_core:error] [pid 10956] [client 72.29.90.27:51830] AH01630: client denied by server configuration: /home/****/public_html/mydomain/.user.ini, referer: http://mydomain.net/.user.ini
However, there is nothing in the user.ini or the .htaccess on either site that has been changed, and I have installed no new plugins (everything was playing nicely today until the Woocommerce upgrade to 3.3.4 yesterday)
Internal server errors (error 500) are often caused by plugin or theme function conflicts, so if you have access to your admin panel, try deactivating all plugins. If you don’t have access to your admin panel, try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.
If that does not resolve the issue, try switching to the default theme for your version of WordPress to rule-out a theme-specific issue. If you don’t have access to your admin panel, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue.
If that does not resolve the issue, it’s possible that a .htaccess rule could be the source of the problem. To check for this, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your SFTP or FTP client to view invisible files.
If you weren’t able to resolve the issue by either resetting your plugins and theme or renaming your .htaccess file, we may be able to help, but we’ll need a more detailed error message. Internal server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that time period. If you don’t have access to your server error log, ask your hosting provider to look for you.
@mdshak
I have literally done all of this, including giving you the error messages I have had on both the affected sites.
I have categorically narrowed the error down to the 3.3.4 version of Woocommerce in two ways – (a) removing it from the plugin files immediately resolves the 500 internal error; and (b) reinstalling the 3.3.3 version does not cause the error.
Now, if you want error log dumps, I suggest you provide a way of emailing you so I can provide these. I am not a newbie at all this. I’ve been a website developer for over 10 years, and I’ve made and customised dozens of sites for pay and for play using the platform. I have full access to the control panels of both affected sites with access and user logs and everything else, and I’ve checked and reported on all of them in my comment.
The 3.3.4 upgrade causes an error which is not down to .htaccess, user.ini, themes, or other plugins. I’ll be waiting for 3.3.5 before I install another upgrade of this plugin.
@chrisbebetter – Please share the specific page URL to check the issue. Is your website down totally?
@mdshak as I said, i’ve re-installed Version 3.3.3 so the issue is dealt with. I’ve given you the error message in my first comment that I get with 3.3.4 installed. I can’t get into front or back end with 3.3.4, on either website.
Sorry for hijacking the thread, but chris described the issue so well that I might as well piggyback. Again, I’m experiencing everything he described. I have also gone through the various steps of troubleshooting.
Essentially, activating the 3.3.4 version of woocommerce generates the 500 error both on the frontend and backend. Removing/renaming the woocommerce folder via FTP resolves the error, so it’s clear the issue is with woocommerce.
My temporary url is: https://0180eff.netsolhost.com/wordpress2018/
I am leaving woocommerce activated for the next 24 hours so you can see the error for yourself.
I imagine you will get many more similar support requests as people update their woocommerce to 3.3.4.
yes same issue occurs in my side. i have to downgrade this to version 3.3.3.
I talk to the website host. he said to me that php version is 5.3. I upgrade it to 5.6. now error is fixed. 🙂
Had the same trouble. I rolled back after the update to 3.3.3 woocommerce plugin and it works again. Though all my customers orders are being cancelled on returning back to merchant from Paypal.
I have spent 3 days on it already but can’t work out what the problem is.
Very frustrating!
Any pointers would be welcomed please. 🙂
