@croydan1 It's not the server that's being overrun, it's the firewall. During normal operations it averages about 850 connections per second. During one of the DDoS I saw it hit 14,500 connections/second, before connection timed out.
If you noticed, during the most recent attack, pools were not reachable, but the forums which are on the same servers were available. I've changed how they accessed so it's not coming through that firewall anymore. daWallet needed access to the beta web page, but couldn't reach it - so I changed the access mode and it was immediately available. I'm working on getting the rest of the websites accessed the other way, but there's a lot of them so it takes time. The wallets will also be moved. All of this will be protected by CloudFlare, so should be safe from attack.
I'm also working on getting the pools protected, but so far they do not work properly this way.
@socal Thanks, I gave up on the boot order. Ran over to buddies and grabbed his windows 10 reboot cd. Im just going to run the Windows cd on each hard drive and erase the windows7 that way. Pain stakingly slow but its the only way I can figure out how to do it. So now when I hook the other three drives to the rigged pc each drive will have my windows 10 lol. Then that should get me somewhere.
If the wallet is synchronized, then open the "online wallet".
Sometimes you may need to click refresh to get to the box to come up, where you can enter your passphrase.
Once the "online wallet" is open, go to the bottom just right of center and click "Start mining".
~a popup appears~
In the scroll box, scroll to and select the pool you want, then to the left side, click the "Change" button.
That automatically copies the pools Burst address to your browser.
after clicking "OK" a form will appear (sometimes takes a minute).
Paste the pools Burst address in the bottom box (Recipient), then copy and paste your wallet passphrase in the next box above that and click ok.
It takes about 16 minutes, or 4 rounds for the pool to be setup with your info, so either wait it out or don't be surprised when you see that very same error message for about 4 rounds.
Yeah in my case, and hopefully yours, the error was harmless and went away after I got things straight.
Hopefully this helps, if not 'haitch' will help you get things straightened out.
Welcome to Burst!
I'm guessing it's an old phone? We use the DOM v3 model with is supported in Android 4.4 or greater. If you have an older phone it can't extract the numericID from the wallet. Sorry about that, it is on my list but with all the recent evolutions of the wallet and some other burst projects I'm working on it's been tough.
Not appropriate for this thread but here's sneak peak of an analytics tool.
@ripStarfola like haitch said, all looks ok ... you configured faucet to run at port 5454, so you need to access it under that port ... within the server you should be able to access faucet e.g. at 127.0.0.1:5454 ... not sure how you configured your domain.
burstcoin.faucet.walletServer=https://wallet4.burstnation.com:81255 <- guess it should be 8125
btw. i suggest not use online wallet faucet will commit the secretPhrase
@rnahlawi Yes, there are no overlaps. I encountered many unsynchronized mining (one started but other did not get the signal from the pool to start)due to network issues with the two pc which lead to higher dl.