Tried with different proxies and also with my local ip,
and accounts always get "Authentication Required" even if there is a correct mail pop.
Hope we get a fix for that.
***WARNING*** accounts don't log in - UPDATE feb 27th FIXED?
Re: ***WARNING*** accounts don't log in - UPDATE feb 27th FIXED?
It's working on my side but only the 2fa update have a problem .
- martin@rootjazz
- Site Admin
- Posts: 34855
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: ***WARNING*** accounts don't log in - UPDATE feb 27th FIXED?
Sorry guys, been away the last few days, kids and I all with sickness.
going through the thread now
going through the thread now
- martin@rootjazz
- Site Admin
- Posts: 34855
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
- martin@rootjazz
- Site Admin
- Posts: 34855
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: ***WARNING*** accounts don't log in - UPDATE feb 27th FIXED?
May I test your account here please? I think it may be the type of proxy you are using and an update I need to make. If this is ok, I can get the details from your logs, I just need your permissionhacking wrote: ↑Sat Mar 02, 2024 11:51 am
When running the task, a CMD window pops up, displaying the following content:LOGFILE:logs_24661Code: Select all
unique id: ZaBwXXXXXXX received: C:\Users\XXXname\AppData\Local\Temp\8e09283e-06e5-4a3b-9615-730884fced36.tmp received {'Cookies': ['{"domain":".twitter.com","name":"guest_id_marketing","path":"/","value":"v1%3A170937980720590000"}', '{"domain":".twitter.com","name":"guest_id_ads","path":"/","value":"v1%3A170937980720590000"}', '{"domain":".twitter.com","name":"personalization_id","path":"/","value":"\\"v1_rc+3luNgdAzjMFkvaTlYA==\\""}', '{"domain":".twitter.com","name":"guest_id","path":"/","value":"v1%3A170937980720590000"}', '{"domain":".twitter.com","name":"ct0","path":"/","value":""}'], 'Headers': {'Accept': '', 'Host': 'twitter.com'}, 'Post': False, 'PostDataJson': '', 'Proxy': '', 'Url': 'https://twitter.com/i/js_inst?c_name=ui_metrics'} GET: https://twitter.com/i/js_inst?c_name=ui_metrics Failed to perform, ErrCode: 35, Reason: 'BoringSSL SSL_connect: SSL_ERROR_SYSCALL in connection to twitter.com:443 '. This may be a libcurl error, See https://curl.se/libcurl/c/libcurl-errors.html first for more details. Traceback (most recent call last): File "C:\Users\XXXname\AppData\Roaming\rootjazz\Twitterdub\python\Lib\site-packages\curl_cffi\requests\session.py", line 830, in request c.perform() File "C:\Users\XXXname\AppData\Roaming\rootjazz\Twitterdub\python\Lib\site-packages\curl_cffi\curl.py", line 292, in perform self._check_error(ret, "perform") File "C:\Users\XXXname\AppData\Roaming\rootjazz\Twitterdub\python\Lib\site-packages\curl_cffi\curl.py", line 134, in _check_error raise error curl_cffi.curl.CurlError: Failed to perform, ErrCode: 35, Reason: 'BoringSSL SSL_connect: SSL_ERROR_SYSCALL in connection to twitter.com:443 '. This may be a libcurl error, See https://curl.se/libcurl/c/libcurl-errors.html first for more details. The above exception was the direct cause of the following exception: Traceback (most recent call last): File "C:\Users\XXXname\AppData\Roaming\rootjazz\Twitterdub\python\rjclient.py", line 111, in <module> main() File "C:\Users\XXXname\AppData\Roaming\rootjazz\Twitterdub\python\rjclient.py", line 96, in main raise e File "C:\Users\XXXname\AppData\Roaming\rootjazz\Twitterdub\python\rjclient.py", line 92, in main send = ProcessFile(received) ^^^^^^^^^^^^^^^^^^^^^ File "C:\Users\XXXname\AppData\Roaming\rootjazz\Twitterdub\python\rjclient.py", line 40, in ProcessFile r = Get(j['Url'], j['Headers'], GetProxies(j['Proxy']), j['Cookies']) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Users\XXXname\AppData\Roaming\rootjazz\Twitterdub\python\rjclient.py", line 15, in Get r=s.get(url,impersonate="chrome", headers=headers,proxies=proxies, verify=False); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Users\XXXname\AppData\Roaming\rootjazz\Twitterdub\python\Lib\site-packages\curl_cffi\requests\session.py", line 834, in request raise RequestsError(str(e), e.code, rsp) from e curl_cffi.requests.errors.RequestsError: Failed to perform, ErrCode: 35, Reason: 'BoringSSL SSL_connect: SSL_ERROR_SYSCALL in connection to twitter.com:443 '. This may be a libcurl error, See https://curl.se/libcurl/c/libcurl-errors.html first for more details.
- martin@rootjazz
- Site Admin
- Posts: 34855
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: ***WARNING*** accounts don't log in - UPDATE feb 27th FIXED?
Sorry, I thought you got errors and the process exited. Do you mean this or the python CMD actually freezes and does nothing?
If it errors, that is best, I can add a loop to detect this then wait (x) seconds and try again.
Where: pause / num_retries is customisable
- martin@rootjazz
- Site Admin
- Posts: 34855
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: ***WARNING*** accounts don't log in - UPDATE feb 27th FIXED?
Your proxy is asking for authentication, it's refusing the connection. Are you sure it does / doesn't require IP auth and isn't un:pw?joj.j2111 wrote: ↑Sun Mar 03, 2024 4:19 pm it's still giving me this eror:
PROXY ISSUE DETECTED: ***** *****@****.com ****.com:9008:*****:***** 407
*****:******/
{"proxy-error":"Error 407. Authentication error. Please check your authentication settings. You can authenticate either by IP white listing or by username + password."}
Validate account failed: (55168745) PROXY_AUTHENTICATION_REQUIRED : Proxy issue detected: 407
even when I white listed my ip adress.
Re: ***WARNING*** accounts don't log in - UPDATE feb 27th FIXED?
yes, approximately the same as in the program settings, there is also a delay for proxy rotation... for example, I have a repeat 2 times, a delay of 8 seconds....martin@rootjazz wrote: ↑Wed Mar 06, 2024 6:42 pmYour proxy is asking for authentication, it's refusing the connection. Are you sure it does / doesn't require IP auth and isn't un:pw?joj.j2111 wrote: ↑Sun Mar 03, 2024 4:19 pm it's still giving me this eror:
PROXY ISSUE DETECTED: ***** *****@****.com ****.com:9008:*****:***** 407
*****:******/
{"proxy-error":"Error 407. Authentication error. Please check your authentication settings. You can authenticate either by IP white listing or by username + password."}
Validate account failed: (55168745) PROXY_AUTHENTICATION_REQUIRED : Proxy issue detected: 407
even when I white listed my ip adress.