ZClassic mining pool down?

Please read this: https://feedback.coinfoundry.org/communities/1/topics/677-clarification-on-shares-not-updating

Let me clarify,

I was not talking about shares not updating.. the miner itself (which is the miner downloaded through the setup generator) says it cannot connect to the coinfoundry server, then will automatically close itself.

Sorry if I didn't make that clear in the original post. 

I'm just another miner using this ZClassic pool; but, I've been using it the past few hours.  It hasn't been down as far as I know.

Thats good for you! Ive tried with the zm miner through the setup generator and the bminer and both for me kick back saying connection failed.

Not sure what to do, want to mine and push this pool to finding the block..

I had to switch anti-virus programs.  McAfee's whitelisting of the program wasn't working, for some reason; but it still appeared as if bminer was running.  I tested it by disabling McAfee altogether for a few minutes, it took a while, like 20 to 30 minutes to see the results on coinfoundry.  However I could tell immediately if bminer was working properly two other ways: whether the local site opened ( 127.0.0.1:1880 by default), and the console displaying many many more "Receiving new job" lines compared with previously. I then used Microsoft's Defender a/v, and it worked with that but I prefer a more robust security program so I switched to Bitdefender, and it's been running fine ever since.  That was just three or four hours ago.

Thanks for the helpful advice and replying!

I’m currently using Windows Defender and have mined on the pool for a few days no problem. It’s just randomly done it where it says failed to connect, I’ll try some more trouble shooting when I’m back home.

Let me know how it goes, I look forward to the help with finding blocks!

Yeah im not sure what to try now.. i've added exceptions through the firewall and defender and neither program will connect to the server. I'm at a loss as what to do now...

Somebody joined; it was at 4 miners and 2.2 KSols/s when I wrote last.  Now it's at 5 / 2.44 KSols/s.  I was hoping you'd managed to get on!  I'm not sure what else to suggest, aside from possibly disabling the firewall and Defender altogether for a short time.  First see if you can get to 127.0.0.1:1880 and then try again after disabling, because that's a way to know immediately - plus the change I mentioned in the number of "Receiving new job" lines.

Even with Firewall and Defender turned completely off it displays this message from the bminer:

"Connection failed due to A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond., retrying in 5 seconds"

I've tried countless other miners also, and they just wont connect.

Oh, man; that sucks.  I hope Coinfoundry support steps in to assist!

For the coinfoundry support, here is what my miners .bat file looks like (I originally connected to port 3124 but the other ports won't connect either):

bminer: 

@echo OFF

REM Change the following address to your Zcash taddr.

SET ADDRESS=t1db2oUE7DN9Vg7UZKRQU6E2sCUqY2FL2js
SET USERNAME=%ADDRESS%.w
SET POOL=zcl.coinfoundry.org:3123
SET SCHEME=stratum

START "Bminer: When Crypto-mining Made Fast" Bminer.exe -uri %SCHEME%://%USERNAME%@%POOL% -api 127.0.0.1:1880

zm_0.5.8_win (downloaded from the setup generator):

zm.exe --server ssl://zcl.coinfoundry.org --port 3123 --user t1db2oUE7DN9Vg7UZKRQU6E2sCUqY2FL2js.RB

@echo off
REM Usage:
REM  zm --server hostname --port port_nr --user user_name
REM     [--pass password] [options]...
REM
REM  Stratum:
REM     --server         Stratum server hostname
REM                      prefix hostname with 'ssl://' for encrypted
REM                      connections - e.g. ssl://mypool.com
REM     --port           Stratum server port number
REM     --user           Username / Workername
REM     --pass           Worker password
REM
REM  Options:
REM     --help           Print this help
REM     --dev            Space separated list of cuda devices
REM     --list-devices   List available cuda devices
REM     --time           Enable output of timestamps
REM     --logfile        [=path] Append logs to the file named by 'path'
REM                      If 'path' is not given append to 'zm.log' in
REM                      current working directory.
REM     --noreconnect    Disable automatic reconnection on network errors.
REM
REM     --temp-target    In C - If set, enables temperature controller.
REM                      The workload of each GPU will be continuously
REM                      adjusted such that the temperature stays around
REM                      this value. It is recommended to set your fan speed
REM                      to 100% when using this setting.
REM
REM     --telemetry      [=ip:port]. Starts telemetry server. Telemetry data
REM                      can be accessed using a web browser(http) or by json-rpc.
REM                      If no arguments are given the server listens on
REM                      127.0.0.1:2222 - Example: --telemetry=0.0.0.0:2222
REM                      Valid port range [1025-65535]
REM  Example:
REM     zm --server servername.com --port 1234 --user username

Hopefully this helps the next time you are able to look at this.

Thank you for your time and efforts.

Try port 3122! I'm using 3122.

UPDATE:

As of right now using the bminer, the ports 3122 & 3123 has decided to start working for me... I tested it on 2 of my machines and they both started receiving jobs. I'm going to leave it running on 1 of my smaller machines to test it over night before I apply it to the rest.

Still don't understand why port 3124 still isn't working but this is a start atleast.

Another update, these are the kind of errors I get from mining.. Ive been mining all day and then it will run errors for awhile then connect itself back to the pool sometimes, and other times it never does. So until I can figure out something more stable, i'll have to wait on moving my hash power back over to this pool.

It seems it's been working perfectly again for me the past few hours.

Even after working for me for awhile, it will lose connection with these kind of errors. I just don't wanna risk any of the downtime.

This seems like something on the CoinFoundry end, every machine running the zm miner (bminer wouldn't work) stopped at the same time saying "server closed the connection r:2" and now won't connect to any of the ports...

I know you are busy Oliver but hopefully you can check into this recurring problem. Thanks.

Weird I see shares coming in and I'm able to connect using my test miner.

Yeah just tried again and the zm miner atleast established a connection again..I can't for the life of me figure out these connection issues.