Some invoices return a Unexpected return code: 500 #23

astupidmoose · 2019-02-15T02:58:45Z

For context: I host BTCPay and Woocommerce on different machines, on different networks.

Sometimes, BTCPay generates an invoice for the customer, however it gets hit with:

Error while sending IPN (1001 invoice_created): Unexpected return code: 500

BTCPay continues to generate this error every 10 minutes until the invoice expires. BTCPay is never able to assign metadata to the woocommerce invoice. Once expired, the status is set to expired and generates another error 500:

Error while sending IPN (1004 invoice_expired): Unexpected return code: 500

This cycles 3 times every 10 minutes for 1 hour.

I know that error 500 indicates a server error, but it seems completely random at the moment and only happens to some invoices.

astupidmoose · 2019-02-15T03:02:38Z

I just checked my woocommerce "fatal-errors.log" file and found the following error on each attempt:

2019-02-14T15:33:49+00:00 CRITICAL Uncaught Exception: Received IPN for order 72724 with BTCPay invoice id72724 while expected BTCPay invoice is in /var/www/html/wp-content/plugins/btcpay-for-woocommerce/class-wc-gateway-btcpay.php:1001
Stack trace:
#0 /var/www/html/wp-includes/class-wp-hook.php(286): WC_Gateway_BtcPay->ipn_callback('')
#1 /var/www/html/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters('', Array)
#2 /var/www/html/wp-includes/plugin.php(453): WP_Hook->do_action(Array)
#3 /var/www/html/wp-content/plugins/woocommerce/includes/class-wc-api.php(97): do_action('woocommerce_api...')
#4 /var/www/html/wp-includes/class-wp-hook.php(286): WC_API->handle_api_requests(Object(WP))
#5 /var/www/html/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(NULL, Array)
#6 /var/www/html/wp-includes/plugin.php(515): WP_Hook->do_action(Array)
#7 /var/www/html/wp-includes/class-wp.php(375): do_action_ref_array('parse_request', Array)
#8 /var/www/html/wp-includes/class-wp.php(715): WP->parse_request('')
#9 /var/www/html/wp-includes/func in /var/www/html/wp-content/plugins/btcpay-for-woocommerce/class-wc-gateway-btcpay.php on line 1001

NicolasDorier · 2019-02-17T03:47:40Z

When did it start appearing? which plugin version?

astupidmoose · 2019-02-17T21:11:35Z

I'm currently on Version 3.0.3.

This has been going for a few weeks. I think it might be the same issue as before, which hangfire was getting held up but not that hangfire is no longer existing it simply shows this in the logs.

I will upgrade to 3.0.6 to see if this helps, but I suspect its been like this for a while.

NicolasDorier · 2019-02-18T02:40:03Z

@Kukks any memory about this?

Kukks · 2019-02-18T06:03:47Z

No clue what could be wrong here

pavlenex · 2019-02-18T08:25:29Z

I can confirm that I'm seeing this error sometimes on expired invoices as well. It's been going on for ages, I just have no idea how to troubleshoot it.

2/16/2019 8:14:20 PM | Creation of invoice starting
2/16/2019 8:14:21 PM | BTC_USD: The rating rule is coinaverage(BTC_USD)
2/16/2019 8:14:21 PM | BTC_USD: The evaluated rating rule is 3612.17840304482
2/16/2019 8:14:25 PM | Invoice 3PaGaD72UcSPkBQsPKw984 new event: invoice_created (1001)
2/16/2019 8:14:27 PM | Error while sending IPN (1001 invoice_created): Unexpected return code: 500
2/16/2019 8:24:28 PM | Error while sending IPN (1001 invoice_created): Unexpected return code: 500
2/16/2019 8:34:29 PM | Error while sending IPN (1001 invoice_created): Unexpected return code: 500
2/16/2019 8:44:22 PM | Invoice status is expired
2/16/2019 8:44:22 PM | Invoice 3PaGaD72UcSPkBQsPKw984 new event: invoice_expired (1004)
2/16/2019 8:44:24 PM | Error while sending IPN (1004 invoice_expired): Unexpected return code: 500
2/16/2019 8:44:25 PM | Error while sending IPN (1004 invoice_expired): Unexpected return code: 500
2/16/2019 8:44:30 PM | Error while sending IPN (1001 invoice_created): Unexpected return code: 500
2/16/2019 8:54:25 PM | Error while sending IPN (1004 invoice_expired): Unexpected return code: 500
2/16/2019 8:54:26 PM | Error while sending IPN (1004 invoice_expired): Unexpected return code: 500
2/16/2019 8:54:31 PM | Error while sending IPN (1001 invoice_created): Unexpected return code: 500
2/16/2019 9:04:26 PM | Error while sending IPN (1004 invoice_expired): Unexpected return code: 500
2/16/2019 9:04:27 PM | Error while sending IPN (1004 invoice_expired): Unexpected return code: 500
2/16/2019 9:04:33 PM | Error while sending IPN (1001 invoice_created): Unexpected return code: 500
2/16/2019 9:14:28 PM | Error while sending IPN (1004 invoice_expired): Unexpected return code: 500
2/16/2019 9:14:28 PM | Error while sending IPN (1004 invoice_expired): Unexpected return code: 500
2/16/2019 9:24:29 PM | Error while sending IPN (1004 invoice_expired): Unexpected return code: 500
2/16/2019 9:24:30 PM | Error while sending IPN (1004 invoice_expired): Unexpected return code: 500
2/16/2019 9:34:30 PM | Error while sending IPN (1004 invoice_expired): Unexpected return code: 500
2/16/2019 9:34:31 PM | Error while sending IPN (1004 invoice_expired): Unexpected return code: 500
2/17/2019 4:14:22 AM | Invoice 3PaGaD72UcSPkBQsPKw984 is not monitored anymore.

I'm unable to connect the events happening with any error WooCommerce/WordPress or server side logs.

Eskyee · 2019-02-18T08:32:49Z

I'm running the latest version, 3.0.6, I`m not seeing any problems, with any expired invoices, just so you know!!

Kukks · 2019-02-18T09:14:50Z

Can any of you experiencing the issue see if there is a fatal errors log file in woocommerce and if there is anything corresponding to the ipn error time in btcpay

…

On Mon, Feb 18, 2019, 09:32 Esky33 ***@***.*** wrote: [image: screenshot 2019-02-18 at 08 28 56] <https://user-images.githubusercontent.com/30862925/52937553-530c5800-3357-11e9-9639-6c721ca8c394.png> I'm running the latest version, 3.0.6, I`m not seeing any problems, with any expired invoices, just so you know!! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#23 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABu-_iKAFZk3X4eL4S55f38OC7pN_Fwtks5vOmUxgaJpZM4a81y7> .

NicolasDorier · 2019-02-18T09:22:49Z

@Kukks I think I remember this issue. I think I fixed it in the old version, you may have thrown the fix away when migrated.

Basically it is a race condition if somebody click twice on the checkout button too fast.

NicolasDorier · 2019-02-18T09:28:40Z

@astupidmoose can you check that for your order, BTCPay created 2 different BTCPay invoices?

NicolasDorier · 2019-02-18T09:30:16Z

@astupidmoose can you also confirm that the customer does not have any issue and you did not had to manually fix anything?

astupidmoose · 2019-02-18T19:17:37Z

@astupidmoose can you check that for your order, BTCPay created 2 different BTCPay invoices?

No, for this example, 72724 is only generated once in BTCPay.

@astupidmoose can you also confirm that the customer does not have any issue and you did not had to manually fix anything?

Customers never pay these invoices when this happens. I am thinking they are presented an Error that BTCPAY is not working and abandon the cart. Unfortunately, this is happening to customers who do not inform us of an issue and simply leave.

astupidmoose · 2019-02-18T19:24:00Z

Customers never pay these invoices when this happens. I am thinking they are presented an Error that BTCPAY is not working and abandon the cart. Unfortunately, this is happening to customers who do not inform us of an issue and simply leave.

OK this could be wrong....

I found an invoice where the error happened on creation, however was paid by the customer and then fixed itself.

On creation, the fatal-errors log shows:

2019-02-15T19:15:00+00:00 CRITICAL Uncaught Exception: Received IPN for order 72954 with BTCPay invoice id72954 while expected BTCPay invoice is in /var/www/html/wp-content/plugins/btcpay-for-woocommerce/class-wc-gateway-btcpay.php:1001
Stack trace:
#0 /var/www/html/wp-includes/class-wp-hook.php(286): WC_Gateway_BtcPay->ipn_callback('')
#1 /var/www/html/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters('', Array)
#2 /var/www/html/wp-includes/plugin.php(453): WP_Hook->do_action(Array)
#3 /var/www/html/wp-content/plugins/woocommerce/includes/class-wc-api.php(97): do_action('woocommerce_api...')
#4 /var/www/html/wp-includes/class-wp-hook.php(286): WC_API->handle_api_requests(Object(WP))
#5 /var/www/html/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(NULL, Array)
#6 /var/www/html/wp-includes/plugin.php(515): WP_Hook->do_action(Array)
#7 /var/www/html/wp-includes/class-wp.php(375): do_action_ref_array('parse_request', Array)
#8 /var/www/html/wp-includes/class-wp.php(715): WP->parse_request('')
#9 /var/www/html/wp-includes/func in /var/www/html/wp-content/plugins/btcpay-for-woocommerce/class-wc-gateway-btcpay.php on line 1001

BTCPay logs show as:

`

2/15/2019 11:14:58 AM	Invoice 6ayYoquW8SNo21PfKLTny3 new event: invoice_created (1001)
2/15/2019 11:15:00 AM	Error while sending IPN (1001 invoice_created): Unexpected return code: 500
2/15/2019 11:15:54 AM	Invoice 6ayYoquW8SNo21PfKLTny3 new event: invoice_receivedPayment (1002)
2/15/2019 11:15:55 AM	Invoice status is paid
2/15/2019 11:15:55 AM	Invoice 6ayYoquW8SNo21PfKLTny3 new event: invoice_paidInFull (1003)
2/15/2019 11:15:55 AM	IPN (1002 invoice_receivedPayment) sent for invoice 6ayYoquW8SNo21PfKLTny3
2/15/2019 11:15:57 AM	IPN (1003 invoice_paidInFull) sent for invoice 6ayYoquW8SNo21PfKLTny3
2/15/2019 11:15:58 AM	IPN (1003 invoice_paidInFull) sent for invoice 6ayYoquW8SNo21PfKLTny3
2/15/2019 11:17:37 AM	Invoice status is confirmed
2/15/2019 11:17:37 AM	Invoice 6ayYoquW8SNo21PfKLTny3 new event: invoice_confirmed (1005)
2/15/2019 11:17:39 AM	IPN (1005 invoice_confirmed) sent for invoice 6ayYoquW8SNo21PfKLTny3
2/15/2019 11:17:39 AM	IPN (1005 invoice_confirmed) sent for invoice 6ayYoquW8SNo21PfKLTny3
2/15/2019 11:25:00 AM	IPN (1001 invoice_created) sent for invoice 6ayYoquW8SNo21PfKLTny3
2/15/2019 11:49:01 AM	Invoice status is complete
2/15/2019 11:49:02 AM	Invoice 6ayYoquW8SNo21PfKLTny3 new event: invoice_completed (1006)
2/15/2019 11:49:02 AM	Invoice 6ayYoquW8SNo21PfKLTny3 is not monitored anymore.
2/15/2019 11:49:02 AM	IPN (1006 invoice_completed) sent for invoice 6ayYoquW8SNo21PfKLTny3
2/15/2019 11:49:03 AM	IPN (1006 invoice_completed) sent for invoice 6ayYoquW8SNo21PfKLTny3

`

astupidmoose · 2019-03-03T20:06:40Z

Still having the same issue. I'm running 3.0.6 now.

For some reason, woocommerce and btcpay stop talking to each other. BTCPay just starts throwing up Error 500 on every invoice creation request.

2019-03-03 02:57:52.958 -08:00 [INF] Invoice MFqPtE28CUvwbiSDFbSkWu new event: invoice_created (1001)
2019-03-03 02:57:53.655 -08:00 [INF] Error while sending IPN (1001 invoice_created): Unexpected return code: 500
2019-03-03 02:58:20.054 -08:00 [INF] Invoice TdPXSp7dgLu8bjGHmmTyZS new event: invoice_created (1001)
2019-03-03 02:58:20.850 -08:00 [INF] Error while sending IPN (1001 invoice_created): Unexpected return code: 500
2019-03-03 02:59:57.432 -08:00 [INF] Invoice 5w9sH7Gr7sKt5G1bVg8QgZ new event: invoice_created (1001)
2019-03-03 02:59:58.388 -08:00 [INF] Error while sending IPN (1001 invoice_created): Unexpected return code: 500

The only way to fix this is completely restarting btcpay which allows it to start generating invoices again. That leads me to beleive its a BTCPay issue more then a plugin one.

NicolasDorier · 2019-03-04T10:03:48Z

I know the issue. invoice_created IPN is sent before php saved the invoice in the DB.
This should not impact anything though. The rest of notification should works fine right?

cryptofuture · 2019-04-22T17:11:20Z

@Kukks
Have the same with 3.0.6 and woocommerce 3.6.1
Basically I could see a call to /wc-api/WC_Gateway_BtcPay/ from btcpayserver with all json data, but reply from a server is 500.
In plugin log:
[Error] The BTCPay payment plugin was called to process an IPN message but could not obtain the order ID from the invoice.
If I try to log . $order_id or . $responseData those are empty
Btcpayserver constantly tries to send IPN, but all its receiving is 500.

astupidmoose · 2019-04-22T17:18:19Z

@cryptofuture are you running on an SSD?

The solution for me ended up switching to an SSD setup as I was running on sata before. The issue was that the invoice was taking too long to create for woocommerce with sata

cryptofuture · 2019-04-22T17:25:33Z

@cryptofuture are you running on an SSD?

The solution for me ended up switching to an SSD setup as I was running on sata before. The issue was that the invoice was taking too long to create for woocommerce with sata

On SSD RAID10

NicolasDorier · 2019-04-23T03:34:13Z

@cryptofuture it does that for every invoice or only once in a while?

cryptofuture · 2019-04-23T04:37:41Z

@cryptofuture it does that for every invoice or only once in a while?

For an every invoice. Error in the log says:

[Error] The BTCPay payment plugin was called to process an IPN message but could not obtain the order ID from the invoice.

But from what i think there is an issue with $invoice = $client->getInvoice($json['id']); but it passes the check: [Info] The IPN check appears to be valid.

As i said if I try to log . $responseData its empty

But what I could say 100% is that btcpayserver sending data on /wc-api/WC_Gateway_BtcPay/ correctly

NicolasDorier · 2019-04-23T05:42:18Z

@cryptofuture can you see, in the order metadata if you have BTCPay_id or BTCPay_rate or something like this?

NicolasDorier · 2019-04-23T05:43:42Z

do you have a orderId field in your btcpay invoice?

NicolasDorier · 2019-04-23T05:45:24Z

When you go inside btcpay's invoice details do you see an order id?

cryptofuture · 2019-04-23T06:00:57Z

When you go inside btcpay's invoice details do you see an order id?

Yes, it also has hyperlink to the woocommerce order-received (redirectUrl) on it in the interface
But, in the data that is send to /wc-api/WC_Gateway_BtcPay/ I didn't found orderId. It should be there, right?

NicolasDorier · 2019-04-23T06:05:49Z

@cryptofuture see

cryptofuture · 2019-04-23T06:06:14Z

Yes, I have it

NicolasDorier · 2019-04-23T06:08:34Z

Damn, I don't know how this can happen...

look https://github.com/btcpayserver/woocommerce-plugin/blob/master/src/class-wc-gateway-btcpay.php#L964

This is where we get the orderId after querying the API.
If you have the orderId this should not be empty or null.... Do you have a way to poke around this code to find what happen?

NicolasDorier · 2019-04-23T06:09:48Z

For example, you can try to print

$client->getResponse()->getBody() if you can

cryptofuture · 2019-04-23T06:13:02Z

$client->getResponse()->getBody()

Trying now.
That is full data that is btcpayserver sending to the /wc-api/WC_Gateway_BtcPay/ btw

{
  "id": "JiNQgy89Cyf8fmuGsPKbuA",
  "url": "https://mybtcpayserver/invoice?id=JiNQgy89Cyf8fmuGsPKbuA",
  "posData": null,
  "status": "confirmed",
  "btcPrice": "0.00155163",
  "price": 8.0,
  "currency": "USD",
  "invoiceTime": 1555329871000,
  "expirationTime": 1555330771000,
  "currentTime": 1555330028152,
  "btcPaid": "0.00155163",
  "btcDue": "0.00000000",
  "rate": 5155.88959990332,
  "exceptionStatus": false,
  "buyerFields": {
    "buyerEmail": "[email protected]"
  },
  "transactionCurrency": null,
  "paymentSubtotals": {
    "btc": 155163
  },
  "paymentTotals": {
    "btc": 155163
  },
  "amountPaid": "0.00000000",
  "exchangeRates": {
    "btc": {
      "usd": 0.0
    }
  }
}

NicolasDorier · 2019-04-23T06:14:59Z

No orderId...

can you go to https://your.btcpayserver.example.org/invoices/JiNQgy89Cyf8fmuGsPKbuA and tell me your Order Id?

cryptofuture · 2019-04-23T07:34:19Z

If I tried to pair with proxified version of btcpayserver and it would stop even earlier on invoice generation here:

$this->log(' [Info] Call to generate invoice was successful: ' . $client->getResponse()->getBody()); with the same Client is: Status Code: 401; Unauthorized

So yes, for some reason when I use btcpayserver directly I could generate invoice, but couldn't get it.

How I could log all request data its sending to get invoice? So I could try to curl it directly on machine that is running btcpayserver.

NicolasDorier · 2019-04-23T07:53:40Z

@cryptofuture I think I know what is going on in your case.
You have a proxy in the between woocommerce and BTCPay that is not the docker?
If so, then the problem is probably that the proxy is rewriting the HOST header.

cryptofuture · 2019-04-23T08:44:20Z

Request to the /invoices/:invoiceId should be signed?

This is what I see in the tcpdump (I wonder where x-identity and x-signature had lost?)

GET /invoices/GMA6BLqBp7M5hfp1qH2STo HTTP/1.0
Host: 127.0.0.1
Connection: close
Accept-Encoding: gzip
CF-IPCountry: CA
X-Forwarded-For: x.x.x.x
CF-RAY: 4cbe58ed4a4ec5e6-EWR
X-Forwarded-Proto: https
CF-Visitor: {"scheme":"https"}
Accept: */*
Content-Type: application/json
X-BitPay-Plugin-Info: BitPay PHP-Client/2.2.20
User-Agent: BitPay PHP-Client/2.2.20 (PHP 7.2.15-0ubuntu0.18.04.2)
X-Accept-Version: 2.0.0
CF-Connecting-IP: x.x.x.x
CDN-Loop: cloudflare

But even if in btcpayserver machine, if I do something like

curl 'http://127.0.0.1:23001/invoices/GMA6BLqBp7M5hfp1qH2STo' -H 'Accept: */*' -H 'Content-Type: application/json' -H 'X-Accept-Version: 2.0.0'

It ends with Status Code: 401; Unauthorized

NicolasDorier · 2019-04-23T08:52:04Z

@cryptofuture this is interesting fact. Let me check.

NicolasDorier · 2019-04-23T08:53:28Z

same thing with the createInvoice? no signature?

cryptofuture · 2019-04-23T08:55:59Z

same thing with the createInvoice? no signature?

Checking now, I launched tcpdump little bit late

  public function getInvoice($invoiceId)
    {
        $this->request = $this->createNewRequest();
        $this->request->setMethod(Request::METHOD_GET);
        if ($this->token && $this->token->getFacade() === 'merchant') {
            $this->request->setPath(sprintf('invoices/%s?token=%s', $invoiceId, $this->token->getToken()));
            $this->addIdentityHeader($this->request);
            $this->addSignatureHeader($this->request);
        } else {
            $this->request->setPath(sprintf('invoices/%s', $invoiceId));
        }
        $this->response = $this->sendRequest($this->request);
        $body = json_decode($this->response->getBody(), true);

        if (isset($body['error'])) {
            throw new \Exception($body['error']);
        }

        $data = $body['data'];

        $invoice = new \Bitpay\Invoice();
        $invoice = $this->fillInvoiceData($invoice, $data);

        return $invoice;
    }

Based on this code it must have x-identity and x-signature

NicolasDorier · 2019-04-23T08:57:00Z

In your logs

$this->log('    [Info] $this->api_token          = ' . $this->api_token);

the api_token is just a string right, not JSON ?

cryptofuture · 2019-04-23T08:59:50Z

the api_token is just a string right, not JSON ?

In your logs
$this->log('    [Info] $this->api_token          = ' . $this->api_token);
the api_token is just a string right, not JSON ?

Its a long string that is looks like its base64 in the log. Ends with ==

NicolasDorier · 2019-04-23T09:01:18Z

Ok now I am wondering why all of this ever worked for anybody... one sec

NicolasDorier · 2019-04-23T09:04:25Z

@cryptofuture do you see something like this in the logs "[Info] API Token decrypted successfully."

NicolasDorier · 2019-04-23T09:06:16Z

I just checked actually this should work.... the api_token is set from what you get at pairing time.
Then serialized and encrypted.

When a new invoice need to be created, it is deserialized/decrypted.

NicolasDorier · 2019-04-23T09:07:09Z

So if ($this->token && $this->token->getFacade() === 'merchant') should definitvely be true.

NicolasDorier · 2019-04-23T09:08:51Z

have you BTCpay v1.0.3.94 ? I recently made some changes so all tokens are always merchant tokens.

cryptofuture · 2019-04-23T09:13:09Z

have you BTCpay v1.0.3.94 ? I recently made some changes so all tokens are always merchant tokens.

git rev-parse HEAD shows 3cce7b8b35705b2ed424964f03d3dd463f488f42

I checked the post the invoices and it contains x-identity and x-signature, so the problem is only with get on /invoices/:invoiceId as its not signed for some reason

I recently made some changes so all tokens are always merchant tokens

Hmm, I use pos facade in some of my code, well would check later. But I wonder it would break older pos tokens, when I update?

POST /invoices HTTP/1.0
Host: 127.0.0.1
Connection: close
Content-Length: 572
Accept-Encoding: gzip
CF-IPCountry: CA
X-Forwarded-For: x.x.x.x
CF-RAY: 4cbea7151dd757c5-IAD
X-Forwarded-Proto: https
CF-Visitor: {"scheme":"https"}
Accept: */*
Content-Type: application/json
X-BitPay-Plugin-Info: BitPay PHP-Client/2.2.20
User-Agent: BitPay PHP-Client/2.2.20 (PHP 7.2.15-0ubuntu0.18.04.2)
X-Accept-Version: 2.0.0
x-identity: 030df3c2b139568020b2829exxce48f5290ad3ef44d0dxxdf158f1d89xx275e922
x-signature: 3045022100xx869c791cxx5947116bfe952cbb77076be4ed2a43428638486b0291687fb160022077cxxba0ca96916e38081f2b1d9c6b4cdd0e6xxc03a99a853bfe82a024dda391
CF-Connecting-IP: x.x.x.x
CDN-Loop: cloudflare

NicolasDorier · 2019-04-23T09:18:10Z

So that's why! Update to the latest stable (the latest branch)

In last versions, I removed the concept of facade. Now user facade input is ignored, and the API always returns merchant.

cryptofuture · 2019-04-23T09:23:11Z

So that's why! Update to the latest stable (the latest branch)

In last versions, I removed the concept of facade. Now user facade input is ignored, and the API always returns merchant.

I'll but how this would help to sign GET /invoices/:invoiceId in the plugin, it seems the problem is that GET /invoices/:invoiceId doesn't have x-identity and x-signature?

NicolasDorier · 2019-04-23T09:24:21Z

Because when you pair your store, you need to select merchant as facade. Your problem is that you are using pos.

I think in both case you need to repair and select merchant.

cryptofuture · 2019-04-23T09:26:52Z

Because when you pair your store, you need to select merchant as facade. Your problem is that you are using pos.

I think in both case you need to repair and select merchant.

OK would try. Could confirm facade is pos

NicolasDorier · 2019-04-23T09:31:39Z

New versions just removed the Facade option so people can't screw up.

cryptofuture · 2019-04-23T09:41:24Z

Same thing with merchant facade. GET on /invoices/:invoiceId is not signed. api_token is a string now.

cryptofuture · 2019-04-23T10:08:33Z

Works now after btcpayserver update, and another re-pairing also in webserver logs reply on /wc-api/WC_Gateway_BtcPay/ is 200 now.

04-23-2019 @ 10:00:48 -     [Info] Order ID is: 110
04-23-2019 @ 10:00:48 -     [Info] Order details retrieved successfully...
04-23-2019 @ 10:00:48 -     [Info] Receiving IPN for an order which has no expected invoice ID, ignoring the IPN...

And


4/23/2019 9:46:22 AM | Creation of invoice starting
-- | --
4/23/2019 9:46:22 AM | BTC_USD: The rating rule is coinaverage(BTC_USD)
4/23/2019 9:46:22 AM | BTC_USD: The evaluated rating rule is 5523.59814104374
4/23/2019 9:46:22 AM | LTC_USD: The rating rule is coinaverage(LTC_USD)
4/23/2019 9:46:22 AM | LTC_USD: The evaluated rating rule is 78.4035815867632
4/23/2019 9:46:22 AM | BTC (Off-Chain): Payment method details creation took 35 milliseconds
4/23/2019 9:46:22 AM | BTC (On-Chain): Payment method details creation took 158 milliseconds
4/23/2019 9:46:22 AM | LTC (On-Chain): Payment method details creation took 259 milliseconds
4/23/2019 9:46:22 AM | Saving invoice took 15 milliseconds
4/23/2019 9:46:22 AM | Invoice V85N2bavmaSa6sXPBjbEUC new event: invoice_created (1001)
4/23/2019 9:46:23 AM | IPN (1001 invoice_created) sent for invoice V85N2bavmaSa6sXPBjbEUC
4/23/2019 9:51:12 AM | Invoice V85N2bavmaSa6sXPBjbEUC new event: invoice_receivedPayment (1002)
4/23/2019 9:51:12 AM | Invoice status is paid
4/23/2019 9:51:12 AM | Invoice V85N2bavmaSa6sXPBjbEUC new event: invoice_paidInFull (1003)
4/23/2019 9:51:13 AM | IPN (1002 invoice_receivedPayment) sent for invoice V85N2bavmaSa6sXPBjbEUC
4/23/2019 9:51:14 AM | IPN (1003 invoice_paidInFull) sent for invoice V85N2bavmaSa6sXPBjbEUC
4/23/2019 9:51:15 AM | IPN (1003 invoice_paidInFull) sent for invoice V85N2bavmaSa6sXPBjbEUC
4/23/2019 9:52:22 AM | Invoice status is confirmed
4/23/2019 9:52:22 AM | Invoice V85N2bavmaSa6sXPBjbEUC new event: invoice_confirmed (1005)
4/23/2019 9:52:23 AM | IPN (1005 invoice_confirmed) sent for invoice V85N2bavmaSa6sXPBjbEUC
4/23/2019 9:52:23 AM | IPN (1005 invoice_confirmed) sent for invoice V85N2bavmaSa6sXPBjbEUC
4/23/2019 10:00:45 AM | Invoice status is complete
4/23/2019 10:00:45 AM | Invoice V85N2bavmaSa6sXPBjbEUC new event: invoice_completed (1006)
4/23/2019 10:00:45 AM | Invoice V85N2bavmaSa6sXPBjbEUC is not monitored anymore.
4/23/2019 10:00:48 AM | IPN (1006 invoice_completed) sent for invoice V85N2bavmaSa6sXPBjbEUC
4/23/2019 10:00:48 AM | IPN (1006 invoice_completed) sent for invoice V85N2bavmaSa6sXPBjbEUC

But in woocommerce Orders lists it still marked as Pending payment should I create new issue for that?

So if select wp-admin/post.php?post=110&action=edit there is nothing new there, and in the woocommerce interface the status is still Pending payment

NicolasDorier · 2019-04-23T11:44:52Z

@cryptofuture the default parameter should be good, but in the settings of the plugin you can map confirmed BTCPay state to any of the woocommerce state you want.

DNSTARS · 2019-06-09T21:29:57Z

We're having a similar issue currently. I've detached our self hosted BTCPay server and connected it to BTCPayJungle and we're looking at this:

Woo logs state:

06-09-2019 @ 19:56:53 - [Error] The BTCPay payment plugin was called to process an IPN message but could not retrieve the order details for order_id: "6808". If you use an alternative order numbering system, please see class-wc-gateway-btcpay.php to apply a search filter.

Removed and re-added the plug in / paired and added this snippet from the FAQ since it suggests it is the error:

This is happening on every invoice now.

NicolasDorier · 2019-06-10T03:52:11Z

@Kukks any idea?

astupidmoose · 2019-06-10T04:05:22Z

@DNSTARS are you using a custom numbering system in woocommerce?

DNSTARS · 2019-06-10T13:05:09Z

Sorry to waste your time, I've gone backwards through all the logs and it seems our X-Frame-Options in WP was changed, given the earlier comments I'll see what is going on there. I think this one is probably a silly issue my side. We went from X-Frame-Options DENY to Header always set X-Frame-Options ALLOW and possibly a few other bits at the exact time this all started.

Made a new WP and threw woo/plug in and BTCPayjungle toether and it works fine - sorry lads.

k3tan172 · 2019-06-12T12:32:49Z

@DNSTARS I'm getting the same issue as you've described. My 'payment pending' isn't turning to 'processing' because of this IPN issue. What did you do to fix?

DNSTARS · 2019-06-12T13:50:18Z

I didn't fix it per se, I just tried BTCPay on a fresh install of WP/Woo and it works, one thing I did notice was that we're on PHP7.0X on debian where it's not working and the test version where it is working is PHP7.2 on ubuntu, that may or may not be significant.

Incidentally our X-Frame options had been set to just "ALLOW" which apparently isn't a valid argument, deleting it out is the expected answer to "Allow", having done that though our issue remained.

Update: 12/06

WooCommerce Admin A new JavaScript-driven interface for managing your store. The plugin includes new and improved reports, and a dashboard to monitor all the important key metrics of your site. Version 0.12.0
By WooCommerce | View details_

This was the culprit - turn it off and see what errors you get your side @k3tan172 , turning this on and off directly matches the IPN 500 errors on BTCPay. The funny thing is I'd turned it back on previously since it had no effect on the issue whilst I was fixing other stuff. Live and learn.

k3tan172 · 2019-06-13T00:10:13Z

I can confirm this was 100% the culprit. Deactivate the Woocommerce Admin plugin and it works like a charm.
Thank you so much for this @DNSTARS
It was doing my head in!

pavlenex mentioned this issue Jun 13, 2019

[BUG] WooCommerce Admin Plugin blocks IPN calls to BTCPay for Woo #28

Closed

Some invoices return a Unexpected return code: 500 #23

Some invoices return a Unexpected return code: 500 #23

Comments

astupidmoose commented Feb 15, 2019

astupidmoose commented Feb 15, 2019

NicolasDorier commented Feb 17, 2019

astupidmoose commented Feb 17, 2019

NicolasDorier commented Feb 18, 2019

Kukks commented Feb 18, 2019

pavlenex commented Feb 18, 2019

Eskyee commented Feb 18, 2019

Kukks commented Feb 18, 2019 via email

NicolasDorier commented Feb 18, 2019 • edited Loading

NicolasDorier commented Feb 18, 2019

NicolasDorier commented Feb 18, 2019

astupidmoose commented Feb 18, 2019

astupidmoose commented Feb 18, 2019 • edited Loading

astupidmoose commented Mar 3, 2019 • edited Loading

NicolasDorier commented Mar 4, 2019

cryptofuture commented Apr 22, 2019 • edited Loading

astupidmoose commented Apr 22, 2019

cryptofuture commented Apr 22, 2019 • edited Loading

NicolasDorier commented Apr 23, 2019

cryptofuture commented Apr 23, 2019 • edited Loading

NicolasDorier commented Apr 23, 2019

NicolasDorier commented Apr 23, 2019 • edited Loading

NicolasDorier commented Apr 23, 2019

cryptofuture commented Apr 23, 2019 • edited Loading

NicolasDorier commented Apr 23, 2019

cryptofuture commented Apr 23, 2019

NicolasDorier commented Apr 23, 2019

NicolasDorier commented Apr 23, 2019

cryptofuture commented Apr 23, 2019

NicolasDorier commented Apr 23, 2019

cryptofuture commented Apr 23, 2019 • edited Loading

NicolasDorier commented Apr 23, 2019

cryptofuture commented Apr 23, 2019

NicolasDorier commented Apr 23, 2019

NicolasDorier commented Apr 23, 2019

cryptofuture commented Apr 23, 2019

NicolasDorier commented Apr 23, 2019

cryptofuture commented Apr 23, 2019

NicolasDorier commented Apr 23, 2019

NicolasDorier commented Apr 23, 2019

NicolasDorier commented Apr 23, 2019

NicolasDorier commented Apr 23, 2019

NicolasDorier commented Apr 23, 2019

cryptofuture commented Apr 23, 2019 • edited Loading

NicolasDorier commented Apr 23, 2019

cryptofuture commented Apr 23, 2019 • edited Loading

NicolasDorier commented Apr 23, 2019

cryptofuture commented Apr 23, 2019 • edited Loading

NicolasDorier commented Apr 23, 2019

cryptofuture commented Apr 23, 2019

cryptofuture commented Apr 23, 2019

NicolasDorier commented Apr 23, 2019

DNSTARS commented Jun 9, 2019 • edited Loading

NicolasDorier commented Jun 10, 2019

astupidmoose commented Jun 10, 2019

DNSTARS commented Jun 10, 2019 • edited Loading

k3tan172 commented Jun 12, 2019

DNSTARS commented Jun 12, 2019 • edited Loading

k3tan172 commented Jun 13, 2019

NicolasDorier commented Feb 18, 2019 •

edited

Loading

astupidmoose commented Feb 18, 2019 •

edited

Loading

astupidmoose commented Mar 3, 2019 •

edited

Loading

cryptofuture commented Apr 22, 2019 •

edited

Loading

cryptofuture commented Apr 22, 2019 •

edited

Loading

cryptofuture commented Apr 23, 2019 •

edited

Loading

NicolasDorier commented Apr 23, 2019 •

edited

Loading

cryptofuture commented Apr 23, 2019 •

edited

Loading

cryptofuture commented Apr 23, 2019 •

edited

Loading

cryptofuture commented Apr 23, 2019 •

edited

Loading

cryptofuture commented Apr 23, 2019 •

edited

Loading

cryptofuture commented Apr 23, 2019 •

edited

Loading

DNSTARS commented Jun 9, 2019 •

edited

Loading

DNSTARS commented Jun 10, 2019 •

edited

Loading

DNSTARS commented Jun 12, 2019 •

edited

Loading