Failed to check for transaction receipt when deploying a contract to Parity light node

[spalladino]

When deploying a contract using web3.js beta 37, connected via an http provider to a Parity light client node (version v2.2.7-stable-b00a21f-20190115/x86_64-linux-gnu/rustc1.31.1), the deployment fails with the following error:

C = new web3.eth.Contract(abi)
C.deploy({ data }).send({ from, gas, gasPrice: 21e9 })
Error: Failed to check for transaction receipt:
{}
    at Object._fireError (.../node_modules/truffle/build/webpack:/~/web3-utils/src/index.js:56:1)

Versions:

node --version
v10.13.0
npm --version
6.4.1
web3.version
'1.0.0-beta.37'

[spalladino]

@nivida let me know what kind of further clarification is needed! I found the code of the contract to be irrelevant to this bug, but I can provide it anyway if it helps.

[nivida]

I will test it asap with the latest version of web3.js and give you further details. Sorry for the late response.

[mschristensen]

I'm also experiencing this issue but when sending a signed transaction like:

        logger.info(`[WRITE] Sending signed transaction...`);
        const signedTransaction = await ownerAccount.signTransaction({
            data: tx.encodeABI(),
            from: ...,
            to: ...,
            gas: gas.toString(),
            gasPrice: price.toString(),
        });
        const receipt = await web3MainNet.eth.sendSignedTransaction(signedTransaction.rawTransaction);

gives:

info: [WRITE] Sending signed transaction...
(node:22491) UnhandledPromiseRejectionWarning: Error: Failed to check for transaction receipt:
{}
    at Object._fireError (/home/ubuntu/<project>/node_modules/web3-utils/src/index.js:56:17)
    at /home/ubuntu/<project>/node_modules/web3-core-method/src/index.js:260:23
    at <anonymous>

node version: v8.12.0
npm version: 6.4.1
web3 version: ^1.0.0-beta.30

[nivida]

Does this error still occur with the latest version of Web3?

[nivida]

Closed because of the missing answer of the creator of this issue.

[d10r]

As I've reported in #1423 (comment), it still happens 1.2.1. In my case while connected to a full node.

[MoMannn]

Same is happening to me on parity (works with geth).

[kael-shipman]

This appears to still be happening for me.

• Web3: v0.20.6 and also v1.2.4
• Parity: v2.5.11-stable light node

Would love some clarity on why this is happening, although I believe it's likely Parity's fault.