[lee group]1150$! The group buy of hosted bitmain S7 @4.73T online on 27th Jan!!

[superbull]

4 x S7@4.73 were dead, other 3 are working good, any one has the same issue?

[smn68]

4 x S7@4.73 were dead, other 3 are working good, any one has the same issue?

All 4 of mine have been off and on for past 24 hours

running at around 9th at present

[superbull]

4 x S7@4.73 were dead, other 3 are working good, any one has the same issue?

All 4 of mine have been off and on for past 24 hours

running at around 9th at present

Is your miner IP 25.xx
Sent urgent email to Li so far got none response...

[mxnsch]

No, my two S7 are hashing fine now and have been in the past 24 hours.

[wlefever]

I haven't had any down time at all on f2pool or really any slow variances.  Maybe you need to evaluate the pool you are mining on?  I'm not saying that is the cause of the problem but from what I've read is pools like kano, etc drop fairly often here.

[superbull]

you don't need a proxy if you don't mine at nichhash, because (1) they run port 3334 for sha256, (2) you need to define a price
simply use CNAME for those 3333 pools
miner config pool1 [<your-hostname>.ddns.org:3333]   ->   DNS Alias (CNAME) map to sg.kano.is for example

sorry for sharing an unworkable idea, changing cname won't immediate switch pool unless there is a network failure occured thus break the current session and reconnect
run a CentOS 7 box as a Network Address Translation router 100% works that I've been tested for a week

miner pool1 config [<your-noip-hostname>.ddns.org:3333] -> your CentOS box ip

since my hosted S7's are runnning :3333 and :3334 i need to do 2 port translation rules, 139.162.5.112 is sg.kano.is, and assuming your firewalld is enabled active zone is "PUBLIC"

firewall-cmd --zone=public --add-masquerade   //enable NAT
firewall-cmd --zone=public --add-forward-port=port=3333:proto=tcp:toport=3333:toaddr=139.162.5.112
firewall-cmd --zone=public --add-forward-port=port=3334:proto=tcp:toport=3333:toaddr=139.162.5.112

to switch pool simply reboot CentOS box and configure the new "toaddr=x.x.x.x"

hash at nicehash you still need a proxy to set price

my 4 x S7@4.73 have been down for 13 hours

[Biffa]

I have one down for 5 hours so far.

[Biffa]

I have one down for 5 hours so far.

Emailed support and its back

[superbull]

miners down for 23+ hours where are my s702, s703, s704, s705?



i paid 2.705BTC hosting fees on Feb 22 then 10 days later i lost 4/7 of total hahrates and nobody care to look into my issue, for God's sake someone pls help

[smn68]

All back on but not hashing 100%, how is comp worked out now the site is still down?

[alienesb]

miners down for 23+ hours where are my s702, s703, s704, s705?



i paid 2.705BTC hosting fees on Feb 22 then 10 days later i lost 4/7 of total hahrates and nobody care to look into my issue, for God's sake someone pls help

You still didn't say what pool you're using.

[superbull]

Pool is Kano, there is nothing to do with mining pools, tried disable my CentOS box only 701 706 707 708 failover to pools2 BW.com, no sign on 702 703 704 705
I don't know but likely something gonna be happened soon.

[alienesb]

Pool is Kano, there is nothing to do with mining pools, tried disable my CentOS box only 701 706 707 708 failover to pools2 BW.com, no sign on 702 703 704 705
I don't know but likely something gonna be happened soon.

How can you rule out the pool and the china firewall? I know you don't want to hear it but everyone has said it before that if you're getting these miners you should point at F2pool or antpool or another Chinese pool. Pcfli should just say that too at this point.

[superbull]

Kano will not ripe off your hashrates, also CentOS will tell how many inbound and outbound connections with source port /addr,  dest port / addr info, i used to hve 8 inbound from Li hosting ip and 8 outbound after NAT'ed to Kano, now I have ony 4 inbound from Li Hosting and 4 outbound after NAT'ed to Kano
You look at the chart you'll see all reading normal

[wlefever]

All I know is I've had zero down time or even more than 2Th drop off on my 4 S7 pointed at f2pool. No matter what y'all want to say pointing it at Kano is part of he issue I'm afraid. Believe me I would like to mine there as well but it just isn't worth constantly having to monitor dropped hashrates to me.

[superbull]

You don't get the story it is not a matter of how much hashrate i'm running it is a matter of miner disappeared either someone powered off my miners or someone changed my miners config for some reasons, issue reported to Li yesterday and still no followup things.

[mxnsch]

issue reported to Li yesterday and still no followup things.

Did you also mail to 16905461@qq.com ?

[sky_g]

You don't get the story it is not a matter of how much hashrate i'm running it is a matter of miner disappeared either someone powered off my miners or someone changed my miners config for some reasons, issue reported to Li yesterday and still no followup things.

Same here . I suppose to get around more than 28 THS but getting around 24 THS. It seems some machine has been turned off ?

[superbull]

Did you also mail to 16905461@qq.com ?

peicaili@foxmail.com   16905461@qq.com   peicaili@gmail.com   leegroupsale.1@gmail.com

miners down for 40+ hours now, keep counting

[mxnsch]

My two S7 just went down.

EDIT: One seems to be somewhat (hashing slowly) alive again. Maybe some datacenter work ongoing now?
EDIT2: Second one coming up, too.