daboo

Back again, after some more troubleshooting.

It turns out that the conflicting code I discovered was a false positive. In the days that followed, I would be able to buy and print labels for several different orders in a row, then encounter the same 500 Internal Server Error. No changes were made to the code during this time.

After a bit of digging, I actually called my bank to cross that possibility off the list. Apparently Mastercard had been flagging some charges from WooCommerce Services, and halting them for further review. After a day or so I would be able to use that card again. This process repeated a few times. I’ve submitted a request to whitelist the charges in the future, but we’ll have to wait and see. Apparently this wasn’t my local bank’s fraud prevention dept, but Mastercard itself.

Please consider this a request – if possible – to return a more detailed error when a payment problem arises. 500 Internal Server Error doesn’t really point to a payment issue, and it’s really only been luck/desperation that brought me to the solution.

Thanks again for making a great product,
John

The same error as above persists this morning. I’m not able to find any relevant errors anywhere else.

This error was with unmodified Storefront activated, and only 4 plugins activated (WooCommerce, WooCommerce Services, Jetpack, & a maintenance mode plugin). I can’t imagine there are any conflicts.

https://imgur.com/QiG363Q

https://imgur.com/EkNCgAS

09-05-2017 @ 09:23:06 - wcc_server_error_response Error: The WooCommerce Services server returned: Internal Server Error An internal server error occurred ( 500 ) (WC_REST_Connect_Shipping_Label_Controller)

Again, this is on a live site that has been working correctly with WooCommerce Services for two weeks. No significant changes have been made to the site since it last worked to print labels.

I haven’t been able to get far with the WooCommerce Services Error message. Definitely open to suggestions.

Thanks!

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

Follow up: turns out I’d left WooCommerce Services debug logging enabled! Yay!

09-04-2017 @ 15:12:00 - wcc_server_error_response Error: The WooCommerce Services server returned: Internal Server Error An internal server error occurred ( 500 ) (WC_REST_Connect_Shipping_Label_Controller)

Everything working properly with the following .htaccess file:

RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]

# uploaded files
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]

# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule  ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
RewriteRule  ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]

Thanks, but I actually already read that, and followed the instructions during uninstall. This is following all of those steps, where I am left with a wordpress install, and a .htaccess file that was modified to remove the SuperCache rules.

Leaving the file at that, homepages on my multisite install display fine, but /photographs/ (for example) returns a 404.

Using the rules I posted above (found via google), /photographs/ shows up, but attached images don’t load.

Well, thanks. I thought I had covered that base, but after your comment I re-checked. I had hit the “Delete Cache” button a few times, and even set it to serve admins cached files (I figured that would show if super cache was the problem or not), but I didn’t look at the super cache time stamp in the source until just now. And that was it. Fiddled with it for a bit and all is well.

Thanks notlaura!