New version released (0.8.0): https://github.com/Stratehm/stratum-proxy/releasesChanges since 0.7.1-SNAPSHOT: -Fix the uptime when a pool is down. -Enable Kick Connection, Kick IP and Ban IP in the GUI. -Add worker version in the connection page and forward show_message from pool to clients -Try to fix a Getwork issue. Workers are not immediatly notified with job reset. -Add the apiReadOnlyAccessEnabled. If an apiUser is set and this option is present, the read-only API methods are publicly accessible. The displayed GUI will be read-only and login will be required to access to admin features (modify/create/delete pools, ban users...) -Starting pool is now done asynchronously to not delay the proxy startup if a pool is down. -Restore the GUI compatibility with Internet Explorer -Generate SSL certificate with SHA256 instead of sha-1 for GUI (remove stratum-proxy-keystore.jks from the database directory to generate a new certificate) -Add the share validation on Stratum Worker connections if the validateGetworkShares option is enabled. -Add the number of accepted/rejected shares in the user/list API method and in the users page. Changes since 0.7.0: -Allow the value 1 for the workerNumberLimit option. Thank you Pfool! Is it possible yet to connect to a wallet and solo mine with your proxy? |
|
|
|
Seems makefile.unix is no longer a thing, how do we compile the latest version in ubuntu? cd
git clone https://github.com/litecoin-project/litecoin.git
cd litecoin/src
make -f makefile.unix USE_UPNP=- Results in: make: *** No rule to make target `makefile.unix'. Stop. Using ls, I've realized that makefile.unix no longer exists. There is Makefile.am, Makefile.qt.include, Makefile.qttest.include, and Makefile.test.include but I can't figure out how to use them. Please help! |
|
|
|
Hi Emdje, Would it be possible for you to upload the latest image with 1200-1220-1240-1260-1280-1300-1320-1340-1360-1380-1400 available? |
|
|
|
|
Please elaborate on SSPs.
|
|
|
|
Can take orders for PSU's with 36" cables again. They are scheduled to arrive early-mid next week.
If anyone who has purchased from me is willing to, I would greatly appreciate trust being left. I have had quite a few successful sales, and like to think that I provide good service to my customers. Any problems are dealt with accordingly, and I would like to build some positive trust to prevent any wrong-doers from dragging it down. Thanks,
Finksy
Trust left.  Sorry I forgot to leave it when I should have! Side note, might need some more hardware soon. Will drop you a line! |
|
|
|
Is there a problem? Can't connect to either stratum+tcp://sha256.usa.nicehash.com:3334 or stratum+tcp://stratum.westhash.com:3334
we have the same issue with x15 on our end ... x15.usa stratum - no connect ... x15.eu stratum - is fine ... #crysx Confirmed, .eu works but .usa doesn't. Hmm this should work. Are you using the correct port? Can you please try these commands from Windows command prompt (or Linux shell): telnet 198.11.195.136 3339 telnet 192.155.218.242 3339 And copy paste output or make print-screen (you can send it to support@nicehash.com). Just got home and gave usa a try again, it's working now. Guess you guys fixed whatever was wrong? Let me know if you still need me to run the telnet. |
|
|
|
Is there a problem? Can't connect to either stratum+tcp://sha256.usa.nicehash.com:3334 or stratum+tcp://stratum.westhash.com:3334
we have the same issue with x15 on our end ... x15.usa stratum - no connect ... x15.eu stratum - is fine ... #crysx Confirmed, .eu works but .usa doesn't. Contact support@nicehash.com with your mining IP address. My IP isn't static, will this be an issue going forward? |
|
|
|
Is there a problem? Can't connect to either stratum+tcp://sha256.usa.nicehash.com:3334 or stratum+tcp://stratum.westhash.com:3334
we have the same issue with x15 on our end ... x15.usa stratum - no connect ... x15.eu stratum - is fine ... #crysx Confirmed, .eu works but .usa doesn't. |
|
|
|
|
Is there a problem? Can't connect to either stratum+tcp://sha256.usa.nicehash.com:3334 or stratum+tcp://stratum.westhash.com:3334
|
|
|
|
|
Really sucks to see this. Guess I was one of the few lucky ones who got what they paid for.
Good luck, Romanko!
|
|
|
|
Good to know you're using ckpool's code, can't go wrong with that. You must have had to make a few modifications to it, though? It only supports bitcoin mining by default doesn't it?
CK's pool code is certainly only BTC - I'm pretty sure Con would just erase all coins other than BTC if he could  . If the folks over at NH are indeed using ckpool and ckdb for pools other than their BTC solo mining operation, then they've absolutely made modifications to it . Exactly what I was thinking. LOL. |
|
|
|
|
I don't think that's the case, I can point my miners without issue to regular nice/westhash 3333/3334 servers and now solo 3333. I own the rigs though, maybe renting is a different story.
|
|
|
|
I had no idea they had a solo mining pool,
I'm aware of only stratum.nicehash.com and stratum.westhash.com
Also, we only support stratum+tcp, not http or https pools.
Besides this, there should not be any other compatibility issue,
Though nicehash does not follow standards for pools and is likely at fault for any change from the standard that might cause issues. I tend to agree with what they said as I've never found a pool that didn't work with MRR's service. We'll take a look at this ... anyway, we're running ckpool software on solo pools without any modifications, therefore we don't see any reason why this would not work with MRR. Can you please give us some more information: which coin are you mining on solo pool, Bitcoin/Litecoin/Dash? Do you get any error or simply can't connect? And if you can give us some time stamps (in UTC, if possible) when you did try it and it failed? Thanks! It seems to have started to work for some reason, when specifying a difficulty. Still have some testing to do, but so far so good. You can track the Titan here: https://solo.nicehash.com/litecoin/user/LULUoYgf1B1DXH769aFNaY7KpHVH2hH1Xj.htmWas previously connected to your solo pool directly, now through MRR. Previously, adding "stratum.solo.nicehash.com:3334" as a pool on MRR would result in a "pool not reachable" error. Good to know you're using ckpool's code, can't go wrong with that. You must have had to make a few modifications to it, though? It only supports bitcoin mining by default doesn't it? |
|
|
|
I had no idea they had a solo mining pool,
I'm aware of only stratum.nicehash.com and stratum.westhash.com
Also, we only support stratum+tcp, not http or https pools.
Besides this, there should not be any other compatibility issue,
Though nicehash does not follow standards for pools and is likely at fault for any change from the standard that might cause issues. I tend to agree with what they said as I've never found a pool that didn't work with MRR's service. |
|
|
|
Why is it impossible to connect to this pool (LTC in my case) through miningrigrentals.com? This is the only pool I've ever run into that won't work with it.
I can connect fine without MRR, but I need it to work with MRR.
Hmm, there are no limitations whatsoever. I suggest you ask MRR if they are using some filters. Thanks! OK, will do and I'll post what they have to say. Thanks! |
|
|
|
|
Why is it impossible to connect to this pool (LTC in my case) through miningrigrentals.com? This is the only pool I've ever run into that won't work with it.
I can connect fine without MRR, but I need it to work with MRR.
|
|
|
|
2 s-3's pull about 1200 watts at freq 250 your gear should do a good job running 3 s-3's
I would do a comparison to an evga 1300 running s-3's you should get better watts.
Being realistic, what can we actually test on a PSU without proper DC equipment? "Yes it turns on, yes it didn't explode, yes it powered some miners, yes it consumed this much power". We already know these things from the 100s and 100s of S4s its in. The circlejerk of made up stuff is what needs to change, and it probably will now the guy with 7 different accounts is banned. Basically. All we (most of us I'd imagine) can do is measure AC in and DC out and come to a very rough efficiency conclusion. Most of us won't be equipped to measure anything else. Dogie, can you ask someone at BITMAIN if they'll stand behind their product by sending a review unit to jonnyguru? I'll gladly put them in touch with Oklahoma Wolf, or even take care of making it happen myself if their English isn't up to snuff. |
|
|
|
|
Man, some of you guys are fucking annoying. Get off of Dogie's case, or start a thread dedicated to Dogie bashing so you folks can congregate there and circle jerk each other in privacy so we don't have to continually read your fucking useless drivel.
Since none of you geniuses actually have one of these, I'll comment on them. I've got 3 S4+, and so far they're running great. Not a single issue. They seem much better than what came with S4s, by a long shot. Will they die in 2 months? Who the fuck knows. If BITMAIN is serious about these PSUs, they should send a sample to Oklahoma Wolf over at jonnyguru.com. He'll reveal the truth about this PSU in short order. (BITMAIN: If you're interested in this, I can set it up... Just PM me)
About those 2 pictures posted earlier... The first has nothing to even do with the PSU, it's a heat sink fin loose in the main S4 case. BITMAIN QC failure for sure, things like that are hardware killers. The second picture is of a pinched 12V fan wire inside the PSU. Yep, another QC issue, but one that falls on the PSU OEM, not BITMAIN. BITMAIN can't be expected to open up every PSU to check them out for physical damage, in fact they'd probably cause more problems than they'd catch if they did. What that picture tells me, is that the short circuit protection works perfectly in that PSU, and it saved the PSU from failure. You'd be a fool to think this only happens to BITMAIN hardware. Pinched wires have happened with Delta PSUs, Flextronic PSUs, Seasonic PSUs, etc... Shit happens. It'll just happen much less with the big boys I just mentioned.
Now, this PSU is a no-go for me. 18AWG wires and unknown quality means I'll stick to used server hardware made by the likes of Delta.
|
|
|
|
|
Show Posts
