Silly me, my config had
ipv6.stratum.bitcoin.cz:3333
whereas the new(?) url is
stratum.bitcoin.cz:3333
I guess I have been booted and then was trying to connect to the server with old credentials.
Sorry for the confusion, though I hope someone else finds your resolution suggestions helpful!
Cheers
Topic: Slush's pool suddenly reports wrong url? (Read 1395 times)
Quote
Or your firewall software, or router... (Have you recently gotten a security update?)
Btw I haven't gotten a security update lately or router firmware update.
Thanks a lot for those possible solutions!
I'll try the different suggestions and will update the thread.
I'll try the different suggestions and will update the thread.
On slushes side...
It could be pointing you to a pool that is down... not realizing the pool is down.
That server MAY have also "backed-up", and may take a moment to "refresh the credentials" from the main server.
also...
Your computer DNS cache could be messing with the connection, trying to connect to the "prior IP" that no longer exists for that NAME, thus, serving you to a non-existent IP. (They use rolling IP's, so that reduces attacks.)
Or, the NAME SERVER they use may be down, so it does not know the actual IP to send you to. (Or the name-server thinks you have the IP of a prior attacker. Because ISP's use recycled rolling IP's too.)
If it is your name-server, DNS service on your computer... (You can just FLUSH it by selecting "repair connection". Then disable that horrible service. Your IPS and your ROUTER already do DNS caching, if your computer does it, that just exposes you to DNS attacking viruses. Computers no longer need to use DNS service. Shut it down and select "disable" for that service.)
It could be pointing you to a pool that is down... not realizing the pool is down.
That server MAY have also "backed-up", and may take a moment to "refresh the credentials" from the main server.
also...
Your computer DNS cache could be messing with the connection, trying to connect to the "prior IP" that no longer exists for that NAME, thus, serving you to a non-existent IP. (They use rolling IP's, so that reduces attacks.)
Or, the NAME SERVER they use may be down, so it does not know the actual IP to send you to. (Or the name-server thinks you have the IP of a prior attacker. Because ISP's use recycled rolling IP's too.)
If it is your name-server, DNS service on your computer... (You can just FLUSH it by selecting "repair connection". Then disable that horrible service. Your IPS and your ROUTER already do DNS caching, if your computer does it, that just exposes you to DNS attacking viruses. Computers no longer need to use DNS service. Shut it down and select "disable" for that service.)
legendary
Activity: 1862
Merit: 1011
Reverse engineer from time to time
Same thing happened to me, but on the BitParking pool. The website was opening fine via a browser, but as soon as I point my miner to the pool, cgminer would not connect.
Could be that your ISP is blocking the "type" of packet going out... They will do that if something seems "viral", and because there is a virus that installs a miner, the data seems viral to them.
Or your firewall software, or router... (Have you recently gotten a security update?)
Or they updated the server, and may have changed an "allowed" rule... You might be sharing an IP from a prior "offender", or they may have altered code that your miner isn't using correctly (rare). Or you previously sent them "corrupt data", and they blocked you. (Eg, if your video-card has errors, and it validates shares with the error, so YOU think it is correct, but when they check it, it is not. Thus, you look like you are attacking with "fraudulent work", so they invalidated your credentials.
P.S. Have you checked the "worker" setup, to see if they "accidentally" scrambled your workers credentials. (Databases get bugged once in a while. If it is expecting "sdfuyos7f8s" worker to connect, but your workers actual name is "bob"... that could cause issues.)
Or your firewall software, or router... (Have you recently gotten a security update?)
Or they updated the server, and may have changed an "allowed" rule... You might be sharing an IP from a prior "offender", or they may have altered code that your miner isn't using correctly (rare). Or you previously sent them "corrupt data", and they blocked you. (Eg, if your video-card has errors, and it validates shares with the error, so YOU think it is correct, but when they check it, it is not. Thus, you look like you are attacking with "fraudulent work", so they invalidated your credentials.
P.S. Have you checked the "worker" setup, to see if they "accidentally" scrambled your workers credentials. (Databases get bugged once in a while. If it is expecting "sdfuyos7f8s" worker to connect, but your workers actual name is "bob"... that could cause issues.)
I've been using cgminer 3.1 and the same conf file for over 2 months.
Last night suddenly it got disconnected and couldn't be able to connect ever since.
Workers appear fine, account appears fine, and can connect with Bitminter. Cgminer reports that the url might be wrong or workers credentials etc...
Again, nothing has changed from my side.
Btw, I am UK based using Virgin media, you think that has to do with ISP?
Last night suddenly it got disconnected and couldn't be able to connect ever since.
Workers appear fine, account appears fine, and can connect with Bitminter. Cgminer reports that the url might be wrong or workers credentials etc...
Again, nothing has changed from my side.
Btw, I am UK based using Virgin media, you think that has to do with ISP?
Jump to: