@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.
The pool stuck, I need to restart the wallet, its then in the correct block again, but without restart, I dont come over the block. Is there anything what I can do against this ?
Thanks @haitch for hard work. @iKnow0 Just restarted the server and it is up and running again. Seams i still have a little bug in code, and i have to harden it ... will get that done.
@potkas Thanks man, I had left my wallet loading/syncing before I left for work and when I got home the wallet fully sunk! No corrupted blockchain download from me force closing java - phew! Thanks to you and @daWallet for the help!
@HotDrive burst.ninja responses are over at burstnation.com - however you can always switch to pretty much any other pool and get questions answered here.
Well, I'm back. After hours of deleting, replotting and resizing plots. There seems to be error after error. How can I troubleshoot this "overlapping"? It's getting a bit frustrating now. Any suggestions? Thanks.
So I figured out the problem it ended up being that the hard drive I was using was beat up a bit and not working up to the miner programs standards lol