willkidger

Okay, thanks!

No problem, to me it made sense to go to Stripe first and they weren’t too helpful this morning. I’ve gone back again though and been quite insistent, and they are still sending me back your way. Sorry to just dump the whole transcript but it will give you full context:

(07:49:29 PM) Kimberly M.: Ah ok - I do see in the logs here, it's showing there was an internal server error. What the error is exactly I am not sure as this would be an error with the WooCommerce plugin you're using.
For more information on this error - you'll need to reach out to WooCommerce directly
(07:50:01 PM) Kimberly M.: The contact information I have for WooCommerce is: https://woocommerce.com/contact-us/
(07:50:41 PM) Me : I asked the plugin developers
(07:50:45 PM) Me : https://ww.wp.xz.cn/support/topic/klarna-payment-canceled-internal_server_errorinternal-error/
(07:51:04 PM) Me : "That error message is actually coming directly from Stripe’s API. I would imagine they could review a log entry that might provide some additional info on why that error was thrown on their end.
I hate to send you in the other direction but the error log you see is what the plugin has access to. To get a better understanding of why an internal error was encountered in Stripe, we would need them to dig a little deeper."
(07:52:32 PM) Kimberly M.: Hmm - that is very strange, as this is a 402 error code, which would indicate that it's a server error. 500 error codes are Stripes server errors.
(07:52:37 PM) Kimberly M.: Let me dig a little further.
(07:53:01 PM) Kimberly M.: You can see the difference on the codes here: https://stripe.com/docs/error-codes
(07:53:30 PM) Kimberly M.: As you can see 500 error codes indicate there is an issue with Stripe serves. 400 codes (which this code is 402) indicate there is an issue with the information being sent over - which indicates there's an issue with the plugin you're using.
(07:54:10 PM) Me : Right, but that link says "4xx error status codes indicate an error because of the information provided (e.g. a required parameter was omitted)"
(07:54:22 PM) Me : Surely you can at least tell me what parameter was omitted?
(07:54:31 PM) Me : Or what was the detailed cause for the error?
(07:55:22 PM) Kimberly M.: The error that it's returning is that there is an internal server error. The example you're seeing on the 400 code, is an example. This particular code is 402- Internal_server_error.
(07:55:35 PM) Me : Well, it also says "invalid_request_error"
(07:55:41 PM) Kimberly M.: I am not able to see any more than what is viewable in the logs. The developers for the plugin will need to look over the plugin and the way it's sending the information from their server end.
(07:56:16 PM) Me : Okay, which way is this request going? Is it going from the plugin to Stripe, or Stripe to the plugin?
(07:56:25 PM) Kimberly M.: I would go back to WooCommerce - with the link https://stripe.com/docs/error-codes, and the log to the error showing them that it's an internal server issue (meaning their plugin)
(07:56:32 PM) Kimberly M.: The request is coming from your plugin to Stripe to process
(07:57:12 PM) Me : Right, so surely if there was an internal server issue, the request wouldn't be sent at all?
(07:57:41 PM) Me : The error is being thrown when the request is received, no?
(07:57:48 PM) Kimberly M.: It was sent - and an error was thrown, advising there was an internal server error.
(07:58:25 PM) Kimberly M.: No - the error that is on the logs is saying there is an internal server error with your plugin, as indicated by the 402 code.
(07:58:39 PM) Kimberly M.: If it was a server error in processing the request - it would show a 500 code, not 400.

I figured it out. Somehow the checkout shortcode had been converted at some point within the page to the full expanded code.

@kamola I just used the WP Rollback plugin to roll back this particular plugin update. Personally I did not do a database backup, but I wouldn’t want to advise you on whether you should or not! 😀

Hi @capuderg, thanks for the info.

Changing the ‘to’ address to a normal @gmail.com address worked.

Yes, the team@ email is a Google Group within G Suite. It’s used for other stuff and emails are received fine, whether from within the domain or external people – so I think it’s already configured to allow emails to the group?