Solvedmetamask extension Newer version of matamask throws errors when sending transaction.

I have two versions of metamask chrome extensions. 3.5.2 and 3.9.11.
I'm currently running private geth node Version: 1.6.7-stable

I can process transactions with older version of metamask, but when I switch to newer I get this error.
The message comes instantaneously, every time.

[ethjs-rpc] rpc error with payload {"id":7663982154336,"jsonrpc":"2.0","params":["0xf86b808504a817c800833d090094001a4039eed5a5099b2bd25085b48ef137902be38084be9a65558207f2a0aff9e56abb6bbeee508bf3fc3918176df97ae118b24bf78d90a9edb762900c1fa0649f391910b82dc97f3259f0d781dde56bf1ed710d5723eeea8fc63bb351a48d"],"method":"eth_sendRawTransaction"} Error: invalid sender

You need to make sure you specify both networkId and chainId and they are the same values.

Using an older MetaMask works because we lacked the EIP155 security feature back then.

I've had the same issue, but specifying config.eip155block and networkId that is equal to config.chainId actually helped, thanks @danfinlay!

I've created a repo containing a pre-initialized dev chain that works with MetaMask, just in case it would save someone time configuring this.

However, it seems that, for some reason, truffle-contract in my Dapp doesn't resolve promises of transactions when pointed to MetaMask's provider, even though MetaMask shows these transactions as completed and I can see them recorded to the blockchain. This reproduces both on my local dev net and on Ropsten test net. But this is a different issue, I guess (probably related to #2426).