Topic: [ANN] BTC Clicks - Bitcoin PTC (Paid-to-click) Website - page 6. (Read 47086 times)
So 00:00, 08:00 and 16:00 UTC? But still only rentable once a day?
Referrals will now be added every 8 hours instead of every 24 hours.
good , i am get rent refferal again 
We're making some changes the the referral re-stock procedure. I'll update you soon. For now there are some referrals available.
I addition I was able to pinpoint the problem with the 404 errors and I'm working on fixing it.
I addition I was able to pinpoint the problem with the 404 errors and I'm working on fixing it.
Refs not reset again. Come on, stop messing around.
so difficult rent for refferals every day , so upgrade member long time to profit
Timmyh1986
Accidentally transferred money to my purchase balance
What's your username? I think I've replied to you but your mail server keeps rejecting my emails.
Accidentally transferred money to my purchase balance
does support answer there tickets im still waiting on a reply and its almost been 72 hours
Most emails are answered. What have you asked?
does support answer there tickets im still waiting on a reply and its almost been 72 hours
so , how i can rent referalls? 1 week i am join but twice success rent referrals . i am always reload my browser, but still no unavailable? 
The 403/404 errors will happen due to a burst of multiple requests from the same IP address. As for the timeouts are they 502 or 505 errors?
They're not really timeouts, rather very long delays. I either get a 403/404 or it works after 10+ seconds. Never seen a 5xx.Quote
Do the errors happen all the time regardless of the time of the day, or do they occur at a certain of the day? I'm not understanding how and why would you get timeouts when the servers is barely at 10% capacity whenever I check.
I'm using the site at various times during the day, though I'm not sure if the errors are during a certain timeframe.
Quote
I've checked the logs against the last IP address you used to login into and it seems you are triggering the burst protection, is there anyone else on your network using the website?
No.
Can you PM me your current IP address or re-log so it updates on the system? I'll have a look at the most recent logs.
i am premium member, i am always stay my pc for rent referrals, after 24 hours server reset why always NO REFERRALS UNAVAILABLE ? i am always stay after server reset
Referrals are gone usually by one hour maximum.
i am premium member, i am always stay my pc for rent referrals, after 24 hours server reset why always NO REFERRALS UNAVAILABLE ? i am always stay after server reset
The 403/404 errors will happen due to a burst of multiple requests from the same IP address. As for the timeouts are they 502 or 505 errors?
They're not really timeouts, rather very long delays. I either get a 403/404 or it works after 10+ seconds. Never seen a 5xx.Quote
Do the errors happen all the time regardless of the time of the day, or do they occur at a certain of the day? I'm not understanding how and why would you get timeouts when the servers is barely at 10% capacity whenever I check.
I'm using the site at various times during the day, though I'm not sure if the errors are during a certain timeframe.
Quote
I've checked the logs against the last IP address you used to login into and it seems you are triggering the burst protection, is there anyone else on your network using the website?
No.
I've just seen a POST /ajax/vrequest HTTP/1.1 that's supposed to load the timeout until the captcha and that was answered with a 403 from your server.
Don't you have any logs? I bet you find tons of 403 and 404 in there.
Or this one:
12 seconds to load the captcha.
404 with timestamp from your server. (Your clock is off btw). The ad was not expired or anything. A reload worked fine.
And finally I managed to get "An error has occured" when solving the captcha. This didn't even cause any network traffic AFAICS.
I'm probably wasting 50% more time due to all these errors because I have to load ads over and over or solve captchas twice etc.
Not cool.
Don't you have any logs? I bet you find tons of 403 and 404 in there.
Or this one:
Code:
11:39:02.401193 [...] > 198.154.102.18.80: P [bad tcp cksum 5f97!] 2519:3176(657) ack 2497 win 16603 (DF) (ttl 127, id 57636, len 697)
[...]
GET /captcha?c=view&uid=[...] HTTP/1.1
Host: btcclicks.com
Connection: keep-alive
[...]
11:39:02.623465 198.154.102.18.80 > [...]: . [tcp sum ok] 2497:2497(0) ack 3176 win 172 (DF) (ttl 54, id 27013, len 40)
[...]
11:39:14.699238 198.154.102.18.80 > [...]: . 2497:3949(1452) ack 3176 win 172 (DF) (ttl 54, id 47128, len 1492)
[...]
HTTP/1.1 200 OK
[...]
[...]
GET /captcha?c=view&uid=[...] HTTP/1.1
Host: btcclicks.com
Connection: keep-alive
[...]
11:39:02.623465 198.154.102.18.80 > [...]: . [tcp sum ok] 2497:2497(0) ack 3176 win 172 (DF) (ttl 54, id 27013, len 40)
[...]
11:39:14.699238 198.154.102.18.80 > [...]: . 2497:3949(1452) ack 3176 win 172 (DF) (ttl 54, id 47128, len 1492)
[...]
HTTP/1.1 200 OK
[...]
12 seconds to load the captcha.
Code:
11:43:03.216432 [...] > 198.154.102.18.80: P [bad tcp cksum f3ee!] 1577:2267(690) ack 8451 win 16603 (DF) (ttl 127, id 8866, len 730)
[...]
GET /view?a=de62719500104a229d2106f835feeb03183fabb12ddbe46af1d409feab92f2ea HTTP/1.1
Host: btcclicks.com
Connection: keep-alive
[...]
11:43:03.399658 198.154.102.18.80 > [...]: . [tcp sum ok] 8451:8451(0) ack 2267 win 154 (DF)
[...]
11:43:03.436719 198.154.102.18.80 > [...]: . 8451:9903(1452) ack 2267 win 154 (DF) (ttl 54, id 49389, len 1492)
[...]
HTTP/1.1 404 Not Found
Server: nginx
Date: Sun, 07 Sep 2014 09:42:57 GMT
[...]
[...]
GET /view?a=de62719500104a229d2106f835feeb03183fabb12ddbe46af1d409feab92f2ea HTTP/1.1
Host: btcclicks.com
Connection: keep-alive
[...]
11:43:03.399658 198.154.102.18.80 > [...]: . [tcp sum ok] 8451:8451(0) ack 2267 win 154 (DF)
[...]
11:43:03.436719 198.154.102.18.80 > [...]: . 8451:9903(1452) ack 2267 win 154 (DF) (ttl 54, id 49389, len 1492)
[...]
HTTP/1.1 404 Not Found
Server: nginx
Date: Sun, 07 Sep 2014 09:42:57 GMT
[...]
404 with timestamp from your server. (Your clock is off btw). The ad was not expired or anything. A reload worked fine.
And finally I managed to get "An error has occured" when solving the captcha. This didn't even cause any network traffic AFAICS.
I'm probably wasting 50% more time due to all these errors because I have to load ads over and over or solve captchas twice etc.
Not cool.
The 403/404 errors will happen due to a burst of multiple requests from the same IP address. As for the timeouts are they 502 or 505 errors?
Do the errors happen all the time regardless of the time of the day, or do they occur at a certain of the day? I'm not understanding how and why would you get timeouts when the servers is barely at 10% capacity whenever I check.
I've checked the logs against the last IP address you used to login into and it seems you are triggering the burst protection, is there anyone else on your network using the website?
I've just seen a POST /ajax/vrequest HTTP/1.1 that's supposed to load the timeout until the captcha and that was answered with a 403 from your server.
Don't you have any logs? I bet you find tons of 403 and 404 in there.
Or this one:
12 seconds to load the captcha.
404 with timestamp from your server. (Your clock is off btw). The ad was not expired or anything. A reload worked fine.
And finally I managed to get "An error has occured" when solving the captcha. This didn't even cause any network traffic AFAICS.
I'm probably wasting 50% more time due to all these errors because I have to load ads over and over or solve captchas twice etc.
Not cool.
Don't you have any logs? I bet you find tons of 403 and 404 in there.
Or this one:
Code:
11:39:02.401193 [...] > 198.154.102.18.80: P [bad tcp cksum 5f97!] 2519:3176(657) ack 2497 win 16603 (DF) (ttl 127, id 57636, len 697)
[...]
GET /captcha?c=view&uid=[...] HTTP/1.1
Host: btcclicks.com
Connection: keep-alive
[...]
11:39:02.623465 198.154.102.18.80 > [...]: . [tcp sum ok] 2497:2497(0) ack 3176 win 172 (DF) (ttl 54, id 27013, len 40)
[...]
11:39:14.699238 198.154.102.18.80 > [...]: . 2497:3949(1452) ack 3176 win 172 (DF) (ttl 54, id 47128, len 1492)
[...]
HTTP/1.1 200 OK
[...]
[...]
GET /captcha?c=view&uid=[...] HTTP/1.1
Host: btcclicks.com
Connection: keep-alive
[...]
11:39:02.623465 198.154.102.18.80 > [...]: . [tcp sum ok] 2497:2497(0) ack 3176 win 172 (DF) (ttl 54, id 27013, len 40)
[...]
11:39:14.699238 198.154.102.18.80 > [...]: . 2497:3949(1452) ack 3176 win 172 (DF) (ttl 54, id 47128, len 1492)
[...]
HTTP/1.1 200 OK
[...]
12 seconds to load the captcha.
Code:
11:43:03.216432 [...] > 198.154.102.18.80: P [bad tcp cksum f3ee!] 1577:2267(690) ack 8451 win 16603 (DF) (ttl 127, id 8866, len 730)
[...]
GET /view?a=de62719500104a229d2106f835feeb03183fabb12ddbe46af1d409feab92f2ea HTTP/1.1
Host: btcclicks.com
Connection: keep-alive
[...]
11:43:03.399658 198.154.102.18.80 > [...]: . [tcp sum ok] 8451:8451(0) ack 2267 win 154 (DF)
[...]
11:43:03.436719 198.154.102.18.80 > [...]: . 8451:9903(1452) ack 2267 win 154 (DF) (ttl 54, id 49389, len 1492)
[...]
HTTP/1.1 404 Not Found
Server: nginx
Date: Sun, 07 Sep 2014 09:42:57 GMT
[...]
[...]
GET /view?a=de62719500104a229d2106f835feeb03183fabb12ddbe46af1d409feab92f2ea HTTP/1.1
Host: btcclicks.com
Connection: keep-alive
[...]
11:43:03.399658 198.154.102.18.80 > [...]: . [tcp sum ok] 8451:8451(0) ack 2267 win 154 (DF)
[...]
11:43:03.436719 198.154.102.18.80 > [...]: . 8451:9903(1452) ack 2267 win 154 (DF) (ttl 54, id 49389, len 1492)
[...]
HTTP/1.1 404 Not Found
Server: nginx
Date: Sun, 07 Sep 2014 09:42:57 GMT
[...]
404 with timestamp from your server. (Your clock is off btw). The ad was not expired or anything. A reload worked fine.
And finally I managed to get "An error has occured" when solving the captcha. This didn't even cause any network traffic AFAICS.
I'm probably wasting 50% more time due to all these errors because I have to load ads over and over or solve captchas twice etc.
Not cool.
Could these annoying 404 errors be fixed? It's increasingly often that clicking an ad gives a 404 and reloading once (sometimes twice) loads the ad. I think the same error is causing the "An error occured" after entering the captcha, which also happens more and more often.
Are you using some load balancer and the actual web servers disagree on something? The site also feels sluggish very often compared to the past. You click and there are several seconds delay before something happens (captcha appearing, captcha solution being accepted, countdown starting, ...)
Are you using some load balancer and the actual web servers disagree on something? The site also feels sluggish very often compared to the past. You click and there are several seconds delay before something happens (captcha appearing, captcha solution being accepted, countdown starting, ...)
I have yet to come across this problem. I'm not denying its existence, but I have tried several times to reproduce the errors and have failed.
Could these annoying 404 errors be fixed? It's increasingly often that clicking an ad gives a 404 and reloading once (sometimes twice) loads the ad. I think the same error is causing the "An error occured" after entering the captcha, which also happens more and more often.
Are you using some load balancer and the actual web servers disagree on something? The site also feels sluggish very often compared to the past. You click and there are several seconds delay before something happens (captcha appearing, captcha solution being accepted, countdown starting, ...)
Are you using some load balancer and the actual web servers disagree on something? The site also feels sluggish very often compared to the past. You click and there are several seconds delay before something happens (captcha appearing, captcha solution being accepted, countdown starting, ...)
Just buy bitcoin, time versus profit...
Jump to: