I also get that error many times, you need to keep increasing the Fee, this need to be done automatically, manually is almost impossible to send a TX.
I did increase the fees via script... One of my TX examples:
010000000120e57c9717271536b9623703c14ed29b40c98c3c28f2667935f3d63897fae33e000000006a47304402201af96f3e52586885a5d14bbeb6d9a2951c7eabfbb7d8ab8a41cd3d2574976b78022020496a09878cf87704e47617731f551f201f9364c6cb4b904b48fd5e3ff3dd570121029fd3d2479a37f40d03975cb51ce0fa18cbb709cc46b47caeaa1722cfd3683583ffffffff0138840700000000001976a9148f4da084ec14ed710b96b6a086bbeb06d571faf988ac00000000
#ver. 01000000
txins 01 20e57c9717271536b9623703c14ed29b40c98c3c28f2667935f3d63897fae33e 00000000
SIG 6b 48 30 45
r 02 21 00963de23d2d3057f45927956f354384ba23a502b9574f100151121d356fa826a4
s 02 20 51b0ee4f84be544ffe8e2f9c31e9d2536554d8901f49c45771f42563ce34e341
PUB.X 01 21 029fd3d2479a37f40d03975cb51ce0fa18cbb709cc46b47caeaa1722cfd3683583
seq ffffffff
out # 01
value 98fd050000000000
script. 19 76a9148f4da084ec14ed710b96b6a086bbeb06d571faf988ac
lock 00000000
this has a fee of 100.000 (well above your winning TX) and it wasn't accepted by the mempool because of "mempool-txn-conflict". So something else happened, or you used some other trick when you broadcast your TX.