Your comments

I've been in pools that are scams. This isn't one. It just has low participation so it takes longer to see results. You should note that unlike some other pools, this one does not suffer from the last minute megahashrate user coming in and taking all the coin. That's because your hashes don't expire every 15 minutes like on some sites.If you stick with the pool for the long haul, you will get your share when it hits based on your accepted hashes the whole time. I made a bit of monero here and am looking forward to when ZEC hits again because the pool is so small my portion should be decent. ;)

The issue was resolved the same day for me. Several threads were opened on the issue. They replied to the most active one. 


Your english translation of whatever your native language is makes it difficult to understand exactly what you're saying but if you're saying you are still having an issue with DASH, you should start a new thread so it will get their attention. Try to word the title with a sentence that sums up the problem. Your single word title for this thread doesn't make it obvious that there is an issue.

My graph hasn't moved since the last update at 6am so my guess is that a program that updates info to the stats page is down but since my miners both say everything is normal, I believe their activity is still being tracked so everything should be fine. Hopefully someone at the foundry will restart whatever software relays the info to the stats page soon.

I'm mining Monero and Zec and both of those are the same. It happened within the last couple of hours but I'm not sure when. My miners are plugging away but they are not showing in my active miners field and my hashrate is at zero. Was there a site glitch? Has the foundry been hacked? A reset perhaps?

Your first post is ambiguous then. Were you asking for them to pay you out because you don't expect to be mining anytime in the near future?

I'm not sure what you mean. I got into the pool around 3 weeks ago and its found monero twice in that time.

And according to pool stats it found some 25 days ago as well.

Currently its been 16 days since the last one was found. How did you miss those if you've been in the pool almost a month?

Am I missing something?

Ok...Its fixed. My son opened a command prompt in the system32 directory and did something with netsh and winsock.

It reset my network requiring a restart and now everything is working again.

It took him 10 seconds then he said, "fixed", and returned to his room.

Damn kids. ;)

Issue still not resolved but it looks like Windows 10 did a cumulative update on both computers yesterday that is the likely culprit.

I'll see if I can figure out what happened and post here when its working again.

I'm having this same problem right now. Both of my rigs, one trying to connect to 3036 and the other to 3038, both fail. The one trying port 3036 says SSL_Connection failed: R:1 followed by error, lib, func and reason all being zeros.

The one trying to connect to 3038 says connection closed by server r:1.

They worked fine for the past few days and nothing changed. I just came home to them not working.

Thanks. That was helpful.