[∞ YH] solo.ckpool.org 2% fee solo mining 256 blocks solved! - page 229.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: mikeywith on May 30, 2020, 03:51:49 PM

Quote from: -ck on May 28, 2020, 04:56:57 PM

The thing is that port 80 works just fine, HTTP requests go through just fine, when he managed to connect earlier I guess it was on

Code:

denode.ckpool.org:80

can you enable port 80 for testing?

Code:

stratum+tcp://solo.ckpool.org:80

if not, or if that doesn't work, setting up a relay in EU if other people agree to it will be worth it, I can only assume that a good number of miners reside in the east side of the world, so a relay pool will solve both ISP restrictions and latency.

No, when he connected the denode port 80 hadn't been enabled yet.
I can't enable port 80 on the pool since that's where the http server is. Connecting with http doesn't mean you'll be able to mine because there is probably a transparent proxy at his end which is proxying http traffic and would fail with stratum traffic.

bedla

newbie

Activity: 16

Merit: 58

@bache_plus can you try telnet, if one of 3333 or 443 is reachable for you? This is what you should see if target port is reachable

For port 3333:

Code:

telnet solo.ckpool.org 3333

Trying 2620:1e6:100:1605::2...
Trying 51.81.56.15...
Connected to solo.ckpool.org.
Escape character is '^]'.

For 443:

Code:

telnet solo.ckpool.org 443

Trying 2620:1e6:100:1605::2...
Trying 51.81.56.15...
Connected to solo.ckpool.org.
Escape character is '^]'.

If there is any issue with network route, you will see "Connection refused" and "Unable to connect to remote host".

Iy you are on windows, you may need to enable telnet command ( https://www.rootusers.com/how-to-enable-the-telnet-client-in-windows-10/ ). Also on windows there is no console output in case of successful connection, you are waiting for console to clear out, if telnet connects successfully.

mikeywith

legendary

Activity: 2394

Merit: 6581

be constructive or S.T.F.U

Quote from: -ck on May 28, 2020, 04:56:57 PM

If there's demand I could set up a relay in Germany with some of the funds given to me if that helps.

In regards to the issue member bache_plus is having, I remotely logged in to his PC and did some basic troubleshooting, pining the pool had very bad results, an average of 300ms, I tested a few other pools and they all seem to work just fine, so my guess is that his ISP is blocking the mining port to CK pool, however, the ISP would have blocked larger pools if they wanted to stop him from mining, this pool is relatively small and infamous, so I am not certain about this.

The thing is that port 80 works just fine, HTTP requests go through just fine, when he managed to connect earlier I guess it was on

Code:

denode.ckpool.org:80

can you enable port 80 for testing?

Code:

stratum+tcp://solo.ckpool.org:80

if not, or if that doesn't work, setting up a relay in EU if other people agree to it will be worth it, I can only assume that a good number of miners reside in the east side of the world, so a relay pool will solve both ISP restrictions and latency.

mikeywith

legendary

Activity: 2394

Merit: 6581

be constructive or S.T.F.U

Quote from: bache_plus on May 30, 2020, 12:10:55 PM

Unfortunately, CK didn't connect to me remotely, I don't know why.
Can you connect the remote and see where the problem is?

If Teamviewer isn't blocked in your country as well i don't mind helping you, send me your teamviewer id and password via a pm( please make sure they are temporary id and password )

bache_plus

newbie

Activity: 11

Merit: 0

Quote from: mikeywith on May 30, 2020, 05:30:53 AM

Quote from: bache_plus on May 28, 2020, 04:17:53 PM

I tested changing the DNS. It was useless!
http://s12.picofile.com/file/8398511576/ckpool.JPG

The traceroute means nothing, in fact, it does show that you the packet reached to ckpool.org , the request timed out at certain hops 12-15 and 20-23 only means that the router of that device is blocking the traceroute UDP packets on port 33434, actually, even if you managed to ping the pool it doesn't mean you will be able to mine to it, the way your ISP blocks your connection to the pool is different from what you think.

As I mentioned set the DNS on the MINER itself and see if it shows alive or not, try all different ports available from the pool

Unfortunately, CK didn't connect to me remotely, I don't know why.
Can you connect the remote and see where the problem is?

mikeywith

legendary

Activity: 2394

Merit: 6581

be constructive or S.T.F.U

Quote from: bache_plus on May 28, 2020, 04:17:53 PM

I tested changing the DNS. It was useless!

The traceroute means nothing, in fact, it does show that you the packet reached to ckpool.org , the request timed out at certain hops 12-15 and 20-23 only means that the router of that device is blocking the traceroute UDP packets on port 33434, actually, even if you managed to ping the pool it doesn't mean you will be able to mine to it, the way your ISP blocks your connection to the pool is different from what you think.

As I mentioned set the DNS on the MINER itself and see if it shows alive or not, try all different ports available from the pool

desertfox470

sr. member

Activity: 542

Merit: 251

Quote from: -ck on May 29, 2020, 04:09:42 PM

Quote from: desertfox470 on May 29, 2020, 09:06:12 AM

I believe CK said Iran is blocked from the pool. That could likely be your problem Grin

No, I'm not blocking anything at all.

Sorry, I meant Iran blocks connections to the server you said. Not you

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: desertfox470 on May 29, 2020, 09:06:12 AM

I believe CK said Iran is blocked from the pool. That could likely be your problem Grin

No, I'm not blocking anything at all.

desertfox470

sr. member

Activity: 542

Merit: 251

I believe CK said Iran is blocked from the pool. That could likely be your problem Grin

bache_plus

newbie

Activity: 11

Merit: 0

Quote from: o_solo_miner on May 29, 2020, 02:57:44 AM

Quote from: bache_plus on May 28, 2020, 06:12:45 PM

http://s12.picofile.com/file/8398511576/ckpool.JPG

According to your picture (please remove the exif data next time if you want to stay private),
you are located in france and not iran.

What miner do you use, what firmware is on it, wich pool works with your miner?

I'm not in France. I am in Iran.
I think the data is sent from Iran to France and then sent to the destination, France is just a bridge for Iran.

My devices in farm are t2t, but I have m3 at home, m3 is for testing only.
However, I tested with the same t2t, but the pool is dead.

I checked at home with m3 and the connection was made for a while but the pool died again.

the firmware is latest version.

All pools except btc.com and antpool work with my miner.
European servers have always been better for me.

o_solo_miner

legendary

Activity: 2483

Merit: 1482

-> morgen, ist heute, schon gestern <-

Quote from: bache_plus on May 28, 2020, 06:12:45 PM

quote]

According to your picture (please remove the exif data next time if you want to stay private),
you are located in france and not iran.

What miner do you use, what firmware is on it, wich pool works with your miner?

bache_plus

newbie

Activity: 11

Merit: 0

Quote from: -ck on May 28, 2020, 08:19:50 PM

Quote from: bache_plus on May 28, 2020, 08:16:43 PM

Of course, I think this time is 15 seconds. Not 15 minutes!

I was just checking different ports on solo.ckpool.org.
I don't know how it got connected for a moment!

But now I checked again a few times. But it doesn't work anymore!

Yes 15 seconds sorry.

How long are you waiting? Maybe you need to wait longer for it to connect? The ports that work on solo.ckpool.org are 3333, 443, and 4334

I waited about 5 minutes for each port.
I think it's connected to port 443 for a few seconds.

If this is possible for you, please give me your Telegram ID. Or send a message to my telegram, I will contact you tomorrow and provide you with remote access, you can check what the problem is.
Thanks.
my telegram ID: @no_moree

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: bache_plus on May 28, 2020, 08:16:43 PM

Of course, I think this time is 15 seconds. Not 15 minutes!

I was just checking different ports on solo.ckpool.org.
I don't know how it got connected for a moment!

But now I checked again a few times. But it doesn't work anymore!

Yes 15 seconds sorry.

How long are you waiting? Maybe you need to wait longer for it to connect? The ports that work on solo.ckpool.org are 3333, 443, and 4334

bache_plus

newbie

Activity: 11

Merit: 0

Quote from: -ck on May 28, 2020, 07:44:37 PM

Quote from: bache_plus on May 28, 2020, 07:39:18 PM

Quote from: -ck on May 28, 2020, 07:15:28 PM

Try each of the following:

Code:

denode.ckpool.org:3333
denode.ckpool.org:443
denode.ckpool.org:80

All is dead!

http://s12.picofile.com/file/8398520326/ckpool5.JPG

I saw you authorise on the pool at this time:
[2020-05-28 23:15:29.387] Authorised client 1085395 worker 39hL2zBfBZAjJKLkPvrR85crgbsKqW8sCR as user 39hL2zBfBZAjJKLkPvrR85crgbsKqW8sCR
and then drop at this time:
[2020-05-28 23:15:44.775] Dropped client 1085395 user 39hL2zBfBZAjJKLkPvrR85crgbsKqW8sCR worker 39hL2zBfBZAjJKLkPvrR85crgbsKqW8sCR

So at some stage you successfully connected for 15 minutes (approximately 90 minutes ago). What did you do then?

Of course, I think this time is 15 seconds. Not 15 minutes!

I was just checking different ports on solo.ckpool.org.
I don't know how it got connected for a moment!

But now I checked again a few times. But it doesn't work anymore!

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: bache_plus on May 28, 2020, 07:39:18 PM

Quote from: -ck on May 28, 2020, 07:15:28 PM

Try each of the following:

Code:

denode.ckpool.org:3333
denode.ckpool.org:443
denode.ckpool.org:80

All is dead!

I saw you authorise on the pool at this time:
[2020-05-28 23:15:29.387] Authorised client 1085395 worker 39hL2zBfBZAjJKLkPvrR85crgbsKqW8sCR as user 39hL2zBfBZAjJKLkPvrR85crgbsKqW8sCR
and then drop at this time:
[2020-05-28 23:15:44.775] Dropped client 1085395 user 39hL2zBfBZAjJKLkPvrR85crgbsKqW8sCR worker 39hL2zBfBZAjJKLkPvrR85crgbsKqW8sCR

So at some stage you successfully connected for 15 minutes (approximately 90 minutes ago). What did you do then?

bache_plus

newbie

Activity: 11

Merit: 0

Quote from: -ck on May 28, 2020, 07:15:28 PM

Try each of the following:

Code:

denode.ckpool.org:3333
denode.ckpool.org:443
denode.ckpool.org:80

All is dead!

http://s12.picofile.com/file/8398520326/ckpool5.JPG

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Try each of the following:

Code:

denode.ckpool.org:3333
denode.ckpool.org:443
denode.ckpool.org:80

Update: Note I've disabled these since this post if anyone was trying them.

bache_plus

newbie

Activity: 11

Merit: 0

The denode address is also dead!

I don't know what happened that happened like this !!!
http://s12.picofile.com/file/8398518618/ckpool4.JPG

There was apparently a work in the pool. miner I couldn't check in the panel if it really get work, Because before I go to the pool to check stats. I restarted the miner.
https://solo.ckpool.org:444/users/39hL2zBfBZAjJKLkPvrR85crgbsKqW8sCR

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Try mining to:

Code:

denode.ckpool.org:3333

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

If there's demand I could set up a relay in Germany with some of the funds given to me if that helps. However I'd have to point out that it is still better to mine directly to the pool.

Topic: [∞ YH] solo.ckpool.org 2% fee solo mining 256 blocks solved! - page 229. (Read 102489 times)