ive got the same issue with my antminer s9 13.5 th/s
i tried upgrading the firmware, factory resetting it, i also tried to ping the Bitmain netword(6 packets transmitted, 6 packets received, 0% packet loss)
the lights on the ethernet port on the back of the miner seems to be normal
i also just realized that the small red light on the middle hash board is not on
Topic: ANT MINER S9 Socket connect failed: Connection refused (Read 12808 times)
My little contribution here..I think i may have found a new failure mode for this socket error..I was getting the same socket connection error on my D3.
Tried everything - flashed firmware, checked router, changed PSU's..then followed the Bitmain's Troubleshooting tree..the recommend to power only the control board and see if you still get this error - if you dont, then its the hash boards (which is worse) ...I was still getting the error after only powering the control board..so was getting ready to change that..my unit is outside warranty, hence was going to order a new control board..slid out the old board, as you know, the board slides smoothly on guide rails inside the metal cover..to install, you got to push it back till the side pins snap back and lock the board..so i slid the board back and noticed that the reset button was not all the way depressed..a slight play in the position was pressing the reset button..i think..after i set it in position, the socket error was gone...not sure if this helps, but whateva..
Tried everything - flashed firmware, checked router, changed PSU's..then followed the Bitmain's Troubleshooting tree..the recommend to power only the control board and see if you still get this error - if you dont, then its the hash boards (which is worse) ...I was still getting the error after only powering the control board..so was getting ready to change that..my unit is outside warranty, hence was going to order a new control board..slid out the old board, as you know, the board slides smoothly on guide rails inside the metal cover..to install, you got to push it back till the side pins snap back and lock the board..so i slid the board back and noticed that the reset button was not all the way depressed..a slight play in the position was pressing the reset button..i think..after i set it in position, the socket error was gone...not sure if this helps, but whateva..
Strangely on both L3+ and D3 I have corrected this by (while it is running) unplugging the cat5 and giving it a few moments then plugging it back in (Though my system is using dhcp it has set ip's that it gives to the mining machines so either that or static should be okay) don't ask me WHY it works, but SO FAR it works.. might need to do it a couple of times.. oh! must be done after the machine has been up a few minutes and still has the socket error.
My little contribution here..I think i may have found a new failure mode for this socket error..I was getting the same socket connection error on my D3.
Tried everything - flashed firmware, checked router, changed PSU's..then followed the Bitmain's Troubleshooting tree..the recommend to power only the control board and see if you still get this error - if you dont, then its the hash boards (which is worse) ...I was still getting the error after only powering the control board..so was getting ready to change that..my unit is outside warranty, hence was going to order a new control board..slid out the old board, as you know, the board slides smoothly on guide rails inside the metal cover..to install, you got to push it back till the side pins snap back and lock the board..so i slid the board back and noticed that the reset button was not all the way depressed..a slight play in the position was pressing the reset button..i think..after i set it in position, the socket error was gone...not sure if this helps, but whateva..
Tried everything - flashed firmware, checked router, changed PSU's..then followed the Bitmain's Troubleshooting tree..the recommend to power only the control board and see if you still get this error - if you dont, then its the hash boards (which is worse) ...I was still getting the error after only powering the control board..so was getting ready to change that..my unit is outside warranty, hence was going to order a new control board..slid out the old board, as you know, the board slides smoothly on guide rails inside the metal cover..to install, you got to push it back till the side pins snap back and lock the board..so i slid the board back and noticed that the reset button was not all the way depressed..a slight play in the position was pressing the reset button..i think..after i set it in position, the socket error was gone...not sure if this helps, but whateva..
Either at least one of the hash board, controller board and / or PSU is faulty.
I have a similar case whereby after testing 1 hash board at a time and still the same result. I've used a neighboring miner's hash board and tested for hash board and controller board for fault.
I finally came to know that it was my PSU was faulty when I tested it with a neighboring miner and PSU, which incidentally was working perfectly well.
I have a similar case whereby after testing 1 hash board at a time and still the same result. I've used a neighboring miner's hash board and tested for hash board and controller board for fault.
I finally came to know that it was my PSU was faulty when I tested it with a neighboring miner and PSU, which incidentally was working perfectly well.
bitmain told me that that message is because at least one of the board are degraded (chips burnt) o total damage, try with a single board at a time, eventually worked for me, you have to wait a good 15-20 minutes, but at the end worked. I will recommend NOT TO USE the firmware on bitmain's site, is awful, try to find the stock firmware.
What does the kernel log said ?
My batch 20 is doing the same thing. I went through all of the steps bitmain warranty suggested and it still will not hash. I've tried updating the firmware, nothing. I want to try every step possible before going through the process of sending it back. Has anyone tackled this head on?
Odd. S9 now ship with software that, on a cold start, tests each board for an "optimum" working frequency. This can take at least 20 minutes before it shows actual mining, sometimes longer hence why it's recommended to check it after an hour.
Was this a new machine or a used one?
Also, and I know it's a pretty hefty read, but there's lots of info in the actual S9 thread.
Was this a new machine or a used one?
Also, and I know it's a pretty hefty read, but there's lots of info in the actual S9 thread.
Batch 11 machines that had previously run with no issue until i had to restart due to a board acting up.
It's back online right now. 
If you use AntPool, can be normal as AntPool is currently down.
yes I use Antpool ..now How I can know if antpool server work again or still down ?
Point it at https://www.kano.is and see if it works....
If you use AntPool, can be normal as AntPool is currently down.
yes I use Antpool ..now How I can know if antpool server work again or still down ?
If you use AntPool, can be normal as AntPool is currently down.
Now I have same error : Socket connect failed: Connection refused
I had an S9 in hosting that would not hash at all if the one bad board was left in it. I don't recall if it gave this error or if cgminer just flatlined.
Try disconnecting the data cables and pci cables from hash boards, leaving only one board connected, power on and let run for 20 minutes to see if you can get any single board to hash. Power down and try next board. I have found on the R4 that one bad board will cause a "socket connect fail" and not allow the other good board to hash. Once I disconnect the bad board then the other will begin to hash fine.
I have not experienced this same effect on s9's with bad boards but all of mine are earlier Version 1 models, the R4 is Version 2 auto tune
I have not experienced this same effect on s9's with bad boards but all of mine are earlier Version 1 models, the R4 is Version 2 auto tune
OP You don't mention it but have you actually entered your mining pool details?
Odd. S9 now ship with software that, on a cold start, tests each board for an "optimum" working frequency. This can take at least 20 minutes before it shows actual mining, sometimes longer hence why it's recommended to check it after an hour.
Was this a new machine or a used one?
Also, and I know it's a pretty hefty read, but there's lots of info in the actual S9 thread.
Was this a new machine or a used one?
Also, and I know it's a pretty hefty read, but there's lots of info in the actual S9 thread.
Is it still auto-tuning? Turn it on, don't touch it for an hour, and then check how it's behaving.
Auto tuning? i powered it up and let it run for 4 hours and still nothing
Is it still auto-tuning? Turn it on, don't touch it for an hour, and then check how it's behaving.
not new to bitcoin but all of the "go to" remedies are not working...SMH
I power down the PSU. i use a EVGA SUPERnova 1600W G2.
Power on the PSU let it run for 20 or so min and ill get the Socket connect failed: Connection refused on the Overview page.
From there ill do a standard reset hold the power button down for 10 seconds. Nothing happens.
So i do a hard reset completely powering down the unit to then power back up with the same issue 20 or so min later.
Next i did a firmware update per Bitmain's Tech Support.
Used the current firmware listed on the website to update the firmware still nothing.
From there i was directed to Flash the "fix firmware" then flash the updated firmware again, still nothing.
All of the updates and fix firmware flashes are being done without restarts.
Any guidance on the matter would be of great help.
Thank you in advance.
I power down the PSU. i use a EVGA SUPERnova 1600W G2.
Power on the PSU let it run for 20 or so min and ill get the Socket connect failed: Connection refused on the Overview page.
From there ill do a standard reset hold the power button down for 10 seconds. Nothing happens.
So i do a hard reset completely powering down the unit to then power back up with the same issue 20 or so min later.
Next i did a firmware update per Bitmain's Tech Support.
Used the current firmware listed on the website to update the firmware still nothing.
From there i was directed to Flash the "fix firmware" then flash the updated firmware again, still nothing.
All of the updates and fix firmware flashes are being done without restarts.
Any guidance on the matter would be of great help.
Thank you in advance.
Jump to: