Page 1 of 3
Not able to check Username Availability, because GDPR
Posted: Tue Jun 05, 2018 7:00 pm
by mindmaster
I get the following error when I try to check username availability:
Code: Select all
Test account: XXXXXUSERNAMEHERE - texuxudib568A@gmail.com - No Proxy
* FAILED: Errors detected: {"title":"Forbidden","code":1026,"detail":"","gdpr_is_consent_blocking":true,"gdpr_needs_age":true,"gdpr_minimum_required_age":16,"gdpr_needs_consent":true}
* FAILED: XXXXXUSERNAMEHERE
Re: Not able to check Username Availability, because GDPR
Posted: Wed Jun 06, 2018 4:24 am
by support@rootjazz
mindmaster wrote: ↑Tue Jun 05, 2018 7:00 pm
I get the following error when I try to check username availability:
Code: Select all
Test account: XXXXXUSERNAMEHERE - texuxudib568A@gmail.com - No Proxy
* FAILED: Errors detected: {"title":"Forbidden","code":1026,"detail":"","gdpr_is_consent_blocking":true,"gdpr_needs_age":true,"gdpr_minimum_required_age":16,"gdpr_needs_consent":true}
* FAILED: XXXXXUSERNAMEHERE
How are you trying to check username availability?
How can i face this issue?
Can you please provide steps that i can replicate the issue for you?
Are you using EU IP/Proxy?
Regards
Re: Not able to check Username Availability, because GDPR
Posted: Wed Jun 06, 2018 11:15 am
by mindmaster
I loaded a list with usernames.
IP is from Europe.
Re: Not able to check Username Availability, because GDPR
Posted: Thu Jun 07, 2018 4:25 am
by support@rootjazz
How can i check usernames availability?
In which tab?
Are you just checking username availability?
Or doing any other action that has username availability as part of action?
Can you please answer?
Regards
Re: Not able to check Username Availability, because GDPR
Posted: Thu Jun 07, 2018 9:51 am
by mindmaster
1. Scrape section
2. Insert path of the username text file
3. click scrape
4. Run
Re: Not able to check Username Availability, because GDPR
Posted: Fri Jun 08, 2018 4:16 am
by support@rootjazz
mindmaster wrote: ↑Thu Jun 07, 2018 9:51 am
1. Scrape section
2. Insert path of the username text file
3. click scrape
4. Run
I have replicated this issue and for Asian ip there is no issue.
I have tried with Russian IP and i got no issues.
Can you please mention the IP country?
That i can check?
Regards
Re: Not able to check Username Availability, because GDPR
Posted: Fri Jun 08, 2018 9:49 am
by mindmaster
I told you the IP is from Europe.
GDPR is affecting Europe. Not Asia.
Tried with proxies from different countries. UK, Sweden, DE, RO
Re: Not able to check Username Availability, because GDPR
Posted: Sat Jun 09, 2018 3:41 pm
by martin@rootjazz
Delete cookies from account (right click accounts list)
log in again. The program will detect GDPR and should accept the conditions, which should then remove this block which appears to be on your account
Re: Not able to check Username Availability, because GDPR
Posted: Sat Jun 09, 2018 9:12 pm
by mindmaster
Same issue before and after deleting cookies.
I even loaded a new account.
Although from what I see on "Scrape - check USERNAME availability" there is no need to select an account.
Also, tried checking username availability both:
- and not selecting an account.
It seems it works the same and there is no need to select an account.
Tested with no proxy, with Romanian and UK proxies.
Results are the same, as shown bellow:
Code: Select all
Testing: afwsefwef4fgert3eg4343g34e(641)
Test account: afwsefwef4fgert3eg4343g34e - sadasdasdasdasd@gmail.com - No Proxy
* FAILED: Errors detected: {"title":"Forbidden","code":1026,"detail":"","gdpr_is_consent_blocking":true,"gdpr_needs_age":true,"gdpr_minimum_required_age":16,"gdpr_needs_consent":true}
* FAILED: afwsefwef4fgert3eg4343g34e
Scraped: 0 available usernames to register
Code: Select all
Testing: afwsefwef4fgert3eg4343g34e(641)
Test account: afwsefwef4fgert3eg4343g34e - jbmclennanP1fucs@gmail.com - Proxy: 185.193.xx.xx:xx:xxxxxxxxxxxxxxx:xxxxxxxx
* FAILED: Errors detected: {"title":"Forbidden","code":1026,"detail":"","gdpr_is_consent_blocking":true,"gdpr_needs_age":true,"gdpr_minimum_required_age":13,"gdpr_needs_consent":true}
* FAILED: afwsefwef4fgert3eg4343g34e
Scraped: 0 available usernames to register
If you need one if my proxies for testing I can share the details.
Re: Not able to check Username Availability, because GDPR
Posted: Mon Jun 11, 2018 7:17 am
by support@rootjazz
mindmaster wrote: ↑Sat Jun 09, 2018 9:12 pm
Same issue before and after deleting cookies.
I even loaded a new account.
Although from what I see on "Scrape - check USERNAME availability" there is no need to select an account.
Also, tried checking username availability both:
- and not selecting an account.
It seems it works the same and there is no need to select an account.
Tested with no proxy, with Romanian and UK proxies.
Results are the same, as shown bellow:
Code: Select all
Testing: afwsefwef4fgert3eg4343g34e(641)
Test account: afwsefwef4fgert3eg4343g34e - sadasdasdasdasd@gmail.com - No Proxy
* FAILED: Errors detected: {"title":"Forbidden","code":1026,"detail":"","gdpr_is_consent_blocking":true,"gdpr_needs_age":true,"gdpr_minimum_required_age":16,"gdpr_needs_consent":true}
* FAILED: afwsefwef4fgert3eg4343g34e
Scraped: 0 available usernames to register
Code: Select all
Testing: afwsefwef4fgert3eg4343g34e(641)
Test account: afwsefwef4fgert3eg4343g34e - jbmclennanP1fucs@gmail.com - Proxy: 185.193.xx.xx:xx:xxxxxxxxxxxxxxx:xxxxxxxx
* FAILED: Errors detected: {"title":"Forbidden","code":1026,"detail":"","gdpr_is_consent_blocking":true,"gdpr_needs_age":true,"gdpr_minimum_required_age":13,"gdpr_needs_consent":true}
* FAILED: afwsefwef4fgert3eg4343g34e
Scraped: 0 available usernames to register
If you need one if my proxies for testing I can share the details.
Reported this thread to admin and he will reply back here after investigation. Perhaps he will ask for more details/proxys you are using. Please be patient.
Regards