This happens when you make a change to your contract (typically add a new method) but fail to deploy the contract to the network.
In my case I failed to do so because of truffle. truffle migrate does not deploy the new contract code you have to explicitly tell truffle to deploy the new contract by truffle migrate --all
My guess is that Remix is trying to ...
ChainId can be considered to be derived from the signature of a transaction, as described in EIP 155 - in the case of all of these transactions, they have the previous transaction format, where chainId is not present, which you can verify by checking the v value of these transactions (they are all 27 or 28, 0x1c or 0x1b).
You can use the parity_set module to manage a reserved peer pool: https://wiki.parity.io/JSONRPC-parity_set-module.
You can call [parity_dropNonReservedPeers] to get your node to drop all peers. Then add reserved peers with [parity_addReservedPeer]. Call [parity_acceptNonReservedPeers] to revert to normal operation.
You may want to take note of ...
You can run miner.start() on your Geth node, if you enable this rpc module at geth's start.
geth --networkid=3 --rpc --rpcapi "eth,net,web3,admin,personal,miner,debug" --etherbase 0xe78150FaCD36E8EB00291e251424a0515AA1FF05
This "miner" module is not available in Parity as there is not embedded miner for it (unless you configure an external GPU ...