Quote from: gorkemulusoy on November 07, 2018, 04:48:41 PM

Both SRBMiner 1.6.8 and 1.6.9 are always stop mining because of devfee connection. I'm mining XMR on nanopool.Problem started few days ago and I didn't change anything or any settings. But my miners are stop after 4-10 hours after start mining. I check the log and the reason is can't connect to srbminer servers because of devfee. I'm not using any firewall /antivirus or i didn't change any settings in windows. Please help me...

Log:

Code:

[2018-11-05 23:18:03] miner_result: Pool accepted result 0x0000477E
[2018-11-05 23:18:10] hashrate: GPU0: 1949 H/s [BUS:3]
[2018-11-05 23:18:10] hashrate: GPU1: 1794 H/s [BUS:6]
[2018-11-05 23:18:10] hashrate: GPU2: 1797 H/s [BUS:10]
[2018-11-05 23:18:10] hashrate: GPU3: 1787 H/s [BUS:13]
[2018-11-05 23:18:10] hashrate: GPU4: 1950 H/s [BUS:16]
[2018-11-05 23:18:10] hashrate: Total: 9277 H/s
[2018-11-05 23:18:13] DFP online load: FAIL
[2018-11-05 23:18:13] devfee: Tried to contact http://srbminer.com a few times, but couldn't! Please check you firewall/antivirus is not blocking connections!
[2018-11-05 23:18:13] GPU devices disabled!
[2018-11-05 23:18:38] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"09099ccb82df052000470b275e855f7fc0bddec6e66d85d332ef5587d123ecae79497ca82d2d8d000000007fdbf809f7f1c393372b235952fa9d5d065ef55f6b85cfe44b5d16379478aa8f11","job_id":"26959","target":"cf8b0000"}}
[2018-11-05 23:18:38] pool_have_job: Pool sent a new job (ID: 26959)
[2018-11-05 23:19:38] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0909d9cb82df052000470b275e855f7fc0bddec6e66d85d332ef5587d123ecae79497ca82d2d8d000000002128e76038ebc5877de5d30ef6ce777fee1a164e92609904ae3291b08804a89013","job_id":"26960","target":"cf8b0000"}}
[2018-11-05 23:19:38] pool_have_job: Pool sent a new job (ID: 26960)
[2018-11-05 23:19:52] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0909e7cb82df05adb0ec44c0fa30bd4880834613a4d1ced482636a905455a1e9dffda32d5fe0ff00000000695abbfdff3108a5545ebbfccfceb75e8c897b7c7cd5af7054ba84cbbbd3cbc50c","job_id":"26961","target":"cf8b0000"}}
[2018-11-05 23:19:52] pool_have_job: Pool sent a new job (ID: 26961)
[2018-11-05 23:20:10] hashrate: GPU0: 0 H/s [BUS:3]
[2018-11-05 23:20:10] hashrate: GPU1: 0 H/s [BUS:6]
[2018-11-05 23:20:10] hashrate: GPU2: 0 H/s [BUS:10]
[2018-11-05 23:20:10] hashrate: GPU3: 0 H/s [BUS:13]
[2018-11-05 23:20:10] hashrate: GPU4: 0 H/s [BUS:16]
[2018-11-05 23:20:10] hashrate: Total: 0 H/s
[2018-11-05 23:20:52] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0909a3cc82df05adb0ec44c0fa30bd4880834613a4d1ced482636a905455a1e9dffda32d5fe0ff0000000079cfa3f7ca31dce5a65e237a3c4799ea723a48d3e7a4bdb4c67343d9e763070d0f","job_id":"26962","target":"cf8b0000"}}
[2018-11-05 23:20:52] pool_have_job: Pool sent a new job (ID: 26962)
[2018-11-05 23:21:52] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0909dfcc82df05adb0ec44c0fa30bd4880834613a4d1ced482636a905455a1e9dffda32d5fe0ff00000000462277818a7213d95dd8a7a1613d1589b973545b939dffa2d08f3016b142c00312","job_id":"26963","target":"cf8b0000"}}
[2018-11-05 23:21:52] pool_have_job: Pool sent a new job (ID: 26963)
[2018-11-05 23:22:01] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0909e8cc82df05add27b1f85c9f24682b3e2961a325e35424050d1e0403355f27a174b3c8a3d5f00000000a444d6ef9957489461d33bc2d04591b60714cf193204d96f184c12807b6fe1ff07","job_id":"26964","target":"cf8b0000"}}
[2018-11-05 23:22:01] pool_have_job: Pool sent a new job (ID: 26964)
[2018-11-05 23:22:10] hashrate: GPU0: 0 H/s [BUS:3]
[2018-11-05 23:22:10] hashrate: GPU1: 0 H/s [BUS:6]
[2018-11-05 23:22:10] hashrate: GPU2: 0 H/s [BUS:10]
[2018-11-05 23:22:10] hashrate: GPU3: 0 H/s [BUS:13]
[2018-11-05 23:22:10] hashrate: GPU4: 0 H/s [BUS:16]
[2018-11-05 23:22:10] hashrate: Total: 0 H/s

If it started a few days ago, and you did not have this problem before, it really looks to me that something did change there on your computer/rig.
I checked the srbminer.com was not down for a looooooong time, so that wasn't the issue.
Anyways, i will loosen on this check a little bit in the next version.