Author

Topic: S17 PRO - not hashing!? (Read 152 times)

legendary
Activity: 3374
Merit: 3095
BTC price road to $80k
October 31, 2022, 04:23:17 PM
#4
Thanks for your sharing, I have seen an article about socket connect failed in zeusbtc, but it said "The troubleshooting step is applicable to A3, B3, D3, L3+, L3++, fixed frequency S9, V9, X3, Z9, Z9 mini", But these methods seem to work on the S17 pro as well.
Actually it works in all of the Bitmain units not just on selected units I experienced this many times when setting up the pool config misspellings/extra spaces are a common issue.

Maybe Zeusbtc posted it long time ago when no s17 pro units yet but it should be still work to all Bitmain units not just s17 pro.
jr. member
Activity: 46
Merit: 14
October 31, 2022, 12:52:57 AM
#3
Thanks for your sharing, I have seen an article about socket connect failed in zeusbtc, but it said "The troubleshooting step is applicable to A3, B3, D3, L3+, L3++, fixed frequency S9, V9, X3, Z9, Z9 mini", But these methods seem to work on the S17 pro as well.
legendary
Activity: 3374
Merit: 3095
BTC price road to $80k
October 27, 2022, 04:27:53 PM
#2
That's the common issue for Bitmain units even old units like s9 can experience this issue sometimes the issue is due to an internet connection or the pool you use is currently down/misspelled or sometimes you need to let run it first for hours before it runs normally.
jr. member
Activity: 62
Merit: 5
October 27, 2022, 11:00:31 AM
#1
Hi!

Last time this forum was to big help so let see if someone know what my problem are.

The miner starts up and but doesn`t start to hash. I will post pictures and logs.

What I see is that on the System, overview page. For hardware version it says: Socket connect failed: Connection refused

Does it says something to you guys?


I found myself the problem, I change the pool address and now it`s working.

Jump to: