Support » Plugin: eWAY Payment Gateway » HTTP/2.0 500 Checkout Error on Safari

  • Resolved liam22



    I’m getting the following woocommerce error notice on Safari (desktop, not sure about mobile). HTTP/2.0 500

    Chrome and Firefox are perfectly fine!

    This issue has popped up over the last few days. We have upgraded to WooCommerce 3.23 but since downgraded to WooCommerce 3.19 with the same issue.

    The console logs:
    [Error] Failed to load resource: the server responded with a status of 500 (HTTP/2.0 500) (, line 0)

    The order submits and the payment is received from eWay but the customer does not get to the checkout-success page and is submitting the order multiple times.

    Since the last update to this plugin was 4 weeks ago. We think it may be a setting change on Cloudways or a recent WooCommerce update which we tried to rectify by downgrading/rolling back.

    If anyone knows what is happening, I would appreciate the help.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author webaware


    G’day Liam,

    If the whole eWAY transaction is completing, then the transaction component was successful and it’s likely something else within the checkout page that is failing. And error 500 is a server-side error, so check your server logs to see what they say.

    You can find your website error log through your hosting control panel, usually under a button called Logs. If you’re not sure where to find it, you can tell WordPress to write errors to the file wp-content/debug.log by editing your wp-config.php file. Find the line that says:

    define('WP_DEBUG', false);

    And replace it with this:

    define('WP_DEBUG', true);
    define('WP_DEBUG_LOG', true);
    define('WP_DEBUG_DISPLAY', false);

    NB: you should change it back when you’re finished, because debug mode slows your website down a bit!




    Hi Ross,

    Looks like the below AfterShip plugin is the culprit:

    I disabled/enabled some plugins one by one and Aftership being disabled turned out to be the winning combo.

    debug.log didn’t log anything meaningful and I also turned logging on inline. I greped ‘aftership’ over the debug.log but found nothing.

    Cheers Ross. You know your plugin is much better than the official one on WooCommerce?

    Plugin Author webaware


    Excellent, well done. I figured it would be a plugin and suspected it might be shipping related. Good work.

    Thanks for the nice comments. Note that the WooCommerce plugin has some big advantages over this little one, specifically it handles refunds and recurring payments. But for basic sales, I reckon this one does a good job too!


Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘HTTP/2.0 500 Checkout Error on Safari’ is closed to new replies.