Pages:
Author

Topic: [DEAD] DeepBit.net PPS+Prop,instant payouts, we pay for INVALID BLOCKS too - page 67. (Read 1601405 times)

newbie
Activity: 31
Merit: 0
So sad that i have to mine somewhere else, i think my macId got blocked with the antiDDOs because my the site wont load or ping nor my GUIminer wont mine. i changed IP and nothing, it has to do with my macid, i guess :/

F4-6D-04-2C-5E-02

but right now im mining at slush, if you can get my rig to connect i'll will be happy!  Grin

my rig-(4x HD6990)

Thx
hero member
Activity: 742
Merit: 500
This server "antiddos" works very poorly, limiting the upstream traffic, I have a mine of 11.3 GH / s running at 9.2 MH / s generating 500 overflows by slow network traffic.
Please remove it.
Yes, I know that some users are unable to connect, but as the total hashrate shows, it works for most of our miners.
It's a very unpleasant situation for me, but this is better than being down during the DDoS.
I'll remove the filtering when possible.

EDIT: We have to keep connecting the mine to the port pit.deepbit.net:8332 or simply pit.deepbit.net?
Depends on your miner. Many mining programs will use this port anyway when it's not set explicitly. 8332 is the default and mostly used port for mining, so we use it too.
I recommend using pit.deepbit.net:8332
aTg
legendary
Activity: 1358
Merit: 1000
This server "antiddos" works very poorly, limiting the upstream traffic, I have a mine of 11.3 GH / s running at 9.2 MH / s generating 500 overflows by slow network traffic.
Please remove it.



EDIT: We have to keep connecting the mine to the port pit.deepbit.net:8332 or simply pit.deepbit.net?
newbie
Activity: 20
Merit: 0
did you try pit.deepbit.net??

Thanks
Pradeep

Yes, pit.deepbit.net works in the web browser, but once I try to log in, it will go back to deepbit.net/login.php and that's where it doesn't connect.
member
Activity: 86
Merit: 10
did you try pit.deepbit.net??

Thanks
Pradeep
newbie
Activity: 20
Merit: 0
Anyone know why I can connect to Deepbit.net from my work location but not at my home? I tried reseting the router/modem to flush any DNS conflict but that didn't work.
legendary
Activity: 952
Merit: 1000
Configuring failover might be a pain in the ass initially, but it really is the way to go in the end. The KEY to doing it right is to use all the available pools, or at least most of them. No sense in using only 2 or 3 pools in your config; if they all go down there are more to choose from and they should have been in your config right from the beginning.

Don't forget to add solomining as a last resort Wink
legendary
Activity: 2072
Merit: 1001
Please fix this vulnerability if you can.
There is no way to "fix" the possibility of a DDoS attack without investing millions of USD (literally).
Even the biggest sites are affected sometimes, may be except Google and Facebook Smiley

Add as many failover pools as you can, usually this helps.

Bah... Get that multiple 10g connections and 500,000 in hardware. We know u like toys and fat pipes. Making profit is for wussies.

Great pool. Keep up good work. I did not miss a single block and some payment.
hero member
Activity: 742
Merit: 500
Please fix this vulnerability if you can.
There is no way to "fix" the possibility of a DDoS attack without investing millions of USD (literally).
Even the biggest sites are affected sometimes, may be except Google and Facebook Smiley

Add as many failover pools as you can, usually this helps.
member
Activity: 96
Merit: 10
Yes, the certificate is expired for me too.

Otherwise:

All miners are now online but:

10 Aug 2012 00:44:12 2735883
09 Aug 2012 23:26:25 1825635
09 Aug 2012 22:31:26 190419
09 Aug 2012 22:26:02 1053816
09 Aug 2012 21:54:29 210 / 3423119 115.986 MH/s + 0.00297536 BTC
09 Aug 2012 19:45:56 1538 / 966303 2712.994 MH/s + 0.07719421 BTC

So, 25% off hashing power in the last 100h by your own stats.

Sorry, but I’d have to look into p2pool next week – solo (3rd failover) in such short time nets nothing so it is a pure loss, and frankly cannot be bothered to register my trust with any more pools – it is as good as playing solo lottery anyway.

Please fix this vulnerability if you can.
hero member
Activity: 742
Merit: 500
Currently we are at ~2.8 TH/s instead of ~3.5 TH/s, but I'm not sure exactly how many users are at the wrong address, how many are affected by the antiddos and who is just mining at their failover.
I tried removing the filter, but total hashrate didn't increased considerably, so I'm assuming that it's the minority who are accidentally "filtered".
Sorry again, but this is at least better that stopping the service at all.

I hope that some of you enjoyed those 24h of 30% better luck that we had.
legendary
Activity: 2072
Merit: 1001

  Anyone else getting certificate errors on Deepbit now?  If I reload the pool's page, I'm getting that.  A good chunk of the regular hasing seems to still be down atm. 
 
  My main system is still up but all my remote ones were having network issues.  Then again I think the router over there died so not the pool's fault there.

I am getting this too. I wont be logging in until this cert issue is cleaned up in case it is a phishing attack

Lock your payout addy and allow them to mine for you. :-)
Worst case is that they screw up your mining.

Plus phishing aint the right term. Dns poisining and fake site attack most likely event... If you ever run into what you are thinking.
hero member
Activity: 533
Merit: 500
Checking this now.
Possibly I launched one of backup loadbalancers with old cert. Wait a minute.

UPD: That loadbalancer is now removed from DNS list, should be fine in a few minutes.

Thanks.  Logged out, logged in and no problem now.  Just have to fix my machine connections tomorrow I suppose Wink
hero member
Activity: 742
Merit: 500
Checking this now.
Possibly I launched one of backup loadbalancers with old cert. Wait a minute.

UPD: That loadbalancer is now removed from DNS list, should be fine in a few minutes.
hero member
Activity: 560
Merit: 500

  Anyone else getting certificate errors on Deepbit now?  If I reload the pool's page, I'm getting that.  A good chunk of the regular hasing seems to still be down atm. 
 
  My main system is still up but all my remote ones were having network issues.  Then again I think the router over there died so not the pool's fault there.

I am getting this too. I wont be logging in until this cert issue is cleaned up in case it is a phishing attack
full member
Activity: 134
Merit: 100
is it an issue seeing this in firefox when i go to my account page?


        deepbit.net uses an invalid security certificate.

The certificate expired on 5/18/2012 2:01 AM. The current time is 8/9/2012 6:22 PM.

(Error code: sec_error_expired_certificate)
hero member
Activity: 533
Merit: 500

  Anyone else getting certificate errors on Deepbit now?  If I reload the pool's page, I'm getting that.  A good chunk of the regular hasing seems to still be down atm. 
 
  My main system is still up but all my remote ones were having network issues.  Then again I think the router over there died so not the pool's fault there.
hero member
Activity: 742
Merit: 500
By the way, are you sure that you use pit.deepbit.net instead of just deepbit.net for mining ?
rjk
sr. member
Activity: 448
Merit: 250
1ngldh
Configuring failover might be a pain in the ass initially, but it really is the way to go in the end. The KEY to doing it right is to use all the available pools, or at least most of them. No sense in using only 2 or 3 pools in your config; if they all go down there are more to choose from and they should have been in your config right from the beginning.
hero member
Activity: 742
Merit: 500
still nada for 4 gpus...
Yes, the problem is not solved yet.

But I suppose that only about 1-5% of miners by hashpower are experiencing connection problems, all others are possibly using their failover pools.

We are doing our best to resolve this issue.
Pages:
Jump to: