X11 Worker Not Displaying In Earnings Page

Encounter a problem related to the pool or have a request for a feature? Post your issue here and we will help you out.
Forum rules
Welcome to the System Support forum! Encounter a problem related to the pool? Post your issue here and we will help you out.

Keep in mind that the forums are monitored by PROHASHING less closely than the official support channels, so if you have a pressing issue, please submit an official support ticket so that our Support Analyst can look into your issue in a timely manner.

We cannot answer financial questions related to your account on a public forum, so those questions should always be submitted through the orange Support button on prohashing.com/about.

For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
Post Reply
locohammerhead
Posts: 5
Joined: Wed Apr 26, 2017 8:55 pm

X11 Worker Not Displaying In Earnings Page

Post by locohammerhead » Wed Apr 26, 2017 9:02 pm

Hello,

Been mining scrypt with prohashing for a little while now. Very happy with it. I'm glad to see you added X11 but I seem to be having a problem getting the site to display that the worker is even connected, let alone hashing. The site shows shows my scrypt miner. My mining software shows connected and hashing at around 9 mhs. Any suggestions?

Thanks
locohammerhead
User avatar
Chris Sokolowski
Site Admin
Posts: 945
Joined: Wed Aug 27, 2014 12:47 pm
Location: State College, PA

Re: X11 Worker Not Displaying In Earnings Page

Post by Chris Sokolowski » Thu Apr 27, 2017 2:07 am

I'll be glad to help. To diagnose the issue, I have a few questions. Are you actually earning money with the worker? Also, do you see the other live elements on the site like live balances?
locohammerhead
Posts: 5
Joined: Wed Apr 26, 2017 8:55 pm

Re: X11 Worker Not Displaying In Earnings Page

Post by locohammerhead » Thu Apr 27, 2017 9:53 am

I am for scrypt. I do see two connections but they are both showing as scrypt and I only have 1 worker set to scrypt. I dont see anything on the earnings page that would constitute a connection. I see the live balances and everything else for scrypt but X11 is entirely missing, not even showing shares for X11. Below is a log from my mining software. I created a new account in which my scrypt miner isn't connected. It shows as mining scrypt instead of X11 but can't calculate hashrate.

image of the x11 worker showing as mining scrypt
http://imgur.com/a/SR38f

[2017-04-27 09:35:03] prohashing.com:3333 x11 block 3126178
[2017-04-27 09:35:03] prohashing.com:3333 x11 block 1650513
[2017-04-27 09:35:03] GPU #0: GeForce GTX 1060 6GB, 9038.93 kH/s
[2017-04-27 09:35:28] GPU #0: GeForce GTX 1060 6GB, 9039.29 kH/s
[2017-04-27 09:35:53] GPU #0: GeForce GTX 1060 6GB, 9048.00 kH/s
[2017-04-27 09:36:04] prohashing.com:3333 x11 block 1467203
[2017-04-27 09:36:04] GPU #0: GeForce GTX 1060 6GB, 9047.87 kH/s
[2017-04-27 09:36:05] prohashing.com:3333 x11 block 46547
[2017-04-27 09:36:05] GPU #0: GeForce GTX 1060 6GB, 9056.28 kH/s
[2017-04-27 09:36:10] prohashing.com:3333 x11 block 1650514
[2017-04-27 09:36:11] GPU #0: GeForce GTX 1060 6GB, 9042.05 kH/s
[2017-04-27 09:36:11] prohashing.com:3333 x11 block 1671973
[2017-04-27 09:36:11] GPU #0: GeForce GTX 1060 6GB, 9038.93 kH/s
[2017-04-27 09:36:12] prohashing.com:3333 x11 block 1650514
[2017-04-27 09:36:12] GPU #0: GeForce GTX 1060 6GB, 9064.98 kH/s
[2017-04-27 09:36:37] GPU #0: GeForce GTX 1060 6GB, 9038.57 kH/s
[2017-04-27 09:36:38] prohashing.com:3333 x11 block 1650515
[2017-04-27 09:36:38] GPU #0: GeForce GTX 1060 6GB, 9038.93 kH/s
[2017-04-27 09:37:03] GPU #0: GeForce GTX 1060 6GB, 9050.18 kH/s
[2017-04-27 09:37:21] prohashing.com:3333 x11 block 1650516
[2017-04-27 09:37:21] GPU #0: GeForce GTX 1060 6GB, 8972.70 kH/s
[2017-04-27 09:37:37] prohashing.com:3333 x11 block 1467204
[2017-04-27 09:37:38] GPU #0: GeForce GTX 1060 6GB, 8995.79 kH/s
[2017-04-27 09:37:39] prohashing.com:3333 x11 block 1650517
[2017-04-27 09:37:39] GPU #0: GeForce GTX 1060 6GB, 9023.37 kH/s
[2017-04-27 09:38:04] GPU #0: GeForce GTX 1060 6GB, 9033.14 kH/s
[2017-04-27 09:38:29] GPU #0: GeForce GTX 1060 6GB, 9002.83 kH/s
[2017-04-27 09:38:54] GPU #0: GeForce GTX 1060 6GB, 9026.93 kH/s
[2017-04-27 09:39:19] GPU #0: GeForce GTX 1060 6GB, 9023.37 kH/s
[2017-04-27 09:39:44] GPU #0: GeForce GTX 1060 6GB, 9003.19 kH/s
[2017-04-27 09:40:08] GPU #0: GeForce GTX 1060 6GB, 9025.12 kH/s
[2017-04-27 09:40:33] GPU #0: GeForce GTX 1060 6GB, 9028.79 kH/s
[2017-04-27 09:40:38] prohashing.com:3333 x11 block 514975
[2017-04-27 09:40:38] GPU #0: GeForce GTX 1060 6GB, 9032.78 kH/s
[2017-04-27 09:40:50] prohashing.com:3333 x11 block 514976
[2017-04-27 09:40:50] GPU #0: GeForce GTX 1060 6GB, 9030.85 kH/s
[2017-04-27 09:41:12] prohashing.com:3333 x11 block 1650517
[2017-04-27 09:41:12] GPU #0: GeForce GTX 1060 6GB, 9033.55 kH/s
[2017-04-27 09:41:13] prohashing.com:3333 x11 block 514977
[2017-04-27 09:41:13] GPU #0: GeForce GTX 1060 6GB, 8961.68 kH/s
[2017-04-27 09:41:18] prohashing.com:3333 x11 block 1650517
[2017-04-27 09:41:18] GPU #0: GeForce GTX 1060 6GB, 9007.87 kH/s
[2017-04-27 09:41:43] GPU #0: GeForce GTX 1060 6GB, 9020.04 kH/s
[2017-04-27 09:42:06] prohashing.com:3333 x11 block 1467206
[2017-04-27 09:42:06] GPU #0: GeForce GTX 1060 6GB, 9030.45 kH/s
[2017-04-27 09:42:09] prohashing.com:3333 x11 block 1650518
[2017-04-27 09:42:09] prohashing.com:3333 x11 block 1671977
[2017-04-27 09:42:09] GPU #0: GeForce GTX 1060 6GB, 9024.12 kH/s
[2017-04-27 09:42:09] prohashing.com:3333 x11 block 1650518
[2017-04-27 09:42:09] GPU #0: GeForce GTX 1060 6GB, 8972.63 kH/s
[2017-04-27 09:42:15] prohashing.com:3333 x11 block 1671977
[2017-04-27 09:42:15] prohashing.com:3333 x11 block 1650518
[2017-04-27 09:42:15] GPU #0: GeForce GTX 1060 6GB, 9032.01 kH/s
[2017-04-27 09:42:16] prohashing.com:3333 x11 block 1671977
[2017-04-27 09:42:17] GPU #0: GeForce GTX 1060 6GB, 9029.20 kH/s
[2017-04-27 09:42:18] prohashing.com:3333 x11 block 1650518
[2017-04-27 09:42:18] GPU #0: GeForce GTX 1060 6GB, 9038.93 kH/s
[2017-04-27 09:42:43] GPU #0: GeForce GTX 1060 6GB, 9028.43 kH/s
[2017-04-27 09:43:08] GPU #0: GeForce GTX 1060 6GB, 9017.60 kH/s
[2017-04-27 09:43:30] prohashing.com:3333 x11 block 1671979
[2017-04-27 09:43:30] GPU #0: GeForce GTX 1060 6GB, 9023.70 kH/s
[2017-04-27 09:43:34] prohashing.com:3333 x11 block 1650518
[2017-04-27 09:43:34] GPU #0: GeForce GTX 1060 6GB, 9018.47 kH/s
[2017-04-27 09:43:59] GPU #0: GeForce GTX 1060 6GB, 9018.68 kH/s
[2017-04-27 09:44:24] GPU #0: GeForce GTX 1060 6GB, 9015.43 kH/s
[2017-04-27 09:44:25] prohashing.com:3333 x11 block 1650519
[2017-04-27 09:44:25] GPU #0: GeForce GTX 1060 6GB, 9031.15 kH/s
JKDReaper
Posts: 99
Joined: Fri Mar 31, 2017 11:17 am

Re: X11 Worker Not Displaying In Earnings Page

Post by JKDReaper » Thu Apr 27, 2017 3:06 pm

If I connect 1 rig that hashes with 2 workers I have the same problem if I use "n=". Both workers will hash on my end, but only one will show on worker status and based on the rate of pay, only that one is credited. However, after some trial and error today I figured out that not naming eliminated the issue and both showed and were crediting. Just noticed this today
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Re: X11 Worker Not Displaying In Earnings Page

Post by Steve Sokolowski » Thu Apr 27, 2017 3:16 pm

JKDReaper wrote:If I connect 1 rig that hashes with 2 workers I have the same problem if I use "n=". Both workers will hash on my end, but only one will show on worker status and based on the rate of pay, only that one is credited. However, after some trial and error today I figured out that not naming eliminated the issue and both showed and were crediting. Just noticed this today
Are you using the same name for both workers, or is "n=" different for each of them?
locohammerhead
Posts: 5
Joined: Wed Apr 26, 2017 8:55 pm

Re: X11 Worker Not Displaying In Earnings Page

Post by locohammerhead » Thu Apr 27, 2017 6:51 pm

Thanks for your help everybody. This was user error on my end. Instead of using a=x11 for the password I was using my default.
Post Reply