Sorry to resurrect an old thread, but this has now happened to me yet again, and my 32p account has been banned as a result.
These are the (obfuscated) logs I managed to capture:
Code: Select all
21-Sep-2018 11:02:11 - ERROR :: mylar.valid_skey_attempt.463 : SEARCH-QUEUE : Got an exception [('Connection aborted.', BadStatusLine("''",))] trying to GET to: https://32p.obfuscated/ajax.php
21-Sep-2018 11:02:17 - ERROR :: mylar.valid_login_attempt.538 : SEARCH-QUEUE : [32P-AUTHENTICATION] The data returned by the login page was not JSON: <!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>News :: 32Pxxxs</title>
<meta charset='utf-8' />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="referrer" content="origin-when-cross-origin" />
<meta content="32Pxxxs, The Website Where Comics are #1!" name="description" />
<snip, but the complete HTML for the main page follows, which suggests the login did work correctly>
21-Sep-2018 11:02:17 - WARNING :: mylar.login.624 : SEARCH-QUEUE : [32P-AUTHENTICATION] Both session key and credential-based logins failed.
21-Sep-2018 11:02:17 - ERROR :: mylar.__init__.41 : SEARCH-QUEUE : [32P-AUTHENTICATION] [LOGIN FAILED] Disabling 32P provider until login error(s) can be fixed in order to avoid temporary bans.
21-Sep-2018 11:07:07 - WARNING :: mylar.Process.384 : Thread-21 : There were no files located - check the debugging logs if you think this is in error.
21-Sep-2018 12:07:07 - WARNING :: mylar.Process.384 : Thread-29 : There were no files located - check the debugging logs if you think this is in error.
21-Sep-2018 13:07:08 - WARNING :: mylar.Process.384 : Thread-26 : There were no files located - check the debugging logs if you think this is in error.
21-Sep-2018 14:07:08 - WARNING :: mylar.Process.384 : Thread-19 : There were no files located - check the debugging logs if you think this is in error.
21-Sep-2018 15:07:08 - WARNING :: mylar.Process.384 : Thread-24 : There were no files located - check the debugging logs if you think this is in error.
21-Sep-2018 16:07:08 - WARNING :: mylar.Process.384 : Thread-15 : There were no files located - check the debugging logs if you think this is in error.
21-Sep-2018 17:07:08 - WARNING :: mylar.Process.384 : Thread-23 : There were no files located - check the debugging logs if you think this is in error.
21-Sep-2018 18:07:08 - WARNING :: mylar.Process.384 : Thread-22 : There were no files located - check the debugging logs if you think this is in error.
21-Sep-2018 19:07:08 - WARNING :: mylar.Process.384 : Thread-21 : There were no files located - check the debugging logs if you think this is in error.
21-Sep-2018 19:26:40 - ERROR :: mylar.valid_login_attempt.545 : Thread-13 : [32P-AUTHENTICATION] Got unexpected status result: {u'status': u'error', u'show_attempts': u'true', u'message': u'You must complete the captcha.', u'attempts': 1, u'twostep': u'false'}
21-Sep-2018 19:26:40 - WARNING :: mylar.login.624 : Thread-13 : [32P-AUTHENTICATION] Both session key and credential-based logins failed.
21-Sep-2018 19:26:40 - ERROR :: mylar.__init__.41 : Thread-13 : [32P-AUTHENTICATION] [LOGIN FAILED] Disabling 32P provider until login error(s) can be fixed in order to avoid temporary bans.
21-Sep-2018 19:46:41 - ERROR :: mylar.valid_login_attempt.545 : Thread-14 : [32P-AUTHENTICATION] Got unexpected status result: {u'status': u'error', u'show_attempts': u'true', u'message': u'You must complete the captcha.', u'attempts': 2, u'twostep': u'false'}
21-Sep-2018 19:46:41 - WARNING :: mylar.login.624 : Thread-14 : [32P-AUTHENTICATION] Both session key and credential-based logins failed.
21-Sep-2018 19:46:41 - ERROR :: mylar.__init__.41 : Thread-14 : [32P-AUTHENTICATION] [LOGIN FAILED] Disabling 32P provider until login error(s) can be fixed in order to avoid temporary bans.
21-Sep-2018 19:54:51 - WARNING :: mylar.Process.384 : Thread-13 : There were no files located - check the debugging logs if you think this is in error.
21-Sep-2018 20:06:41 - ERROR :: mylar.valid_login_attempt.545 : Thread-15 : [32P-AUTHENTICATION] Got unexpected status result: {u'status': u'error', u'show_attempts': u'true', u'message': u'You must complete the captcha.', u'attempts': 2, u'twostep': u'false'}
21-Sep-2018 20:06:41 - WARNING :: mylar.login.624 : Thread-15 : [32P-AUTHENTICATION] Both session key and credential-based logins failed.
21-Sep-2018 20:06:41 - ERROR :: mylar.__init__.41 : Thread-15 : [32P-AUTHENTICATION] [LOGIN FAILED] Disabling 32P provider until login error(s) can be fixed in order to avoid temporary bans.
21-Sep-2018 20:26:40 - ERROR :: mylar.valid_login_attempt.545 : Thread-16 : [32P-AUTHENTICATION] Got unexpected status result: {u'status': u'error', u'show_attempts': u'true', u'message': u'You must complete the captcha.', u'attempts': 3, u'twostep': u'false'}
21-Sep-2018 20:26:40 - WARNING :: mylar.login.624 : Thread-16 : [32P-AUTHENTICATION] Both session key and credential-based logins failed.
21-Sep-2018 20:26:40 - ERROR :: mylar.__init__.41 : Thread-16 : [32P-AUTHENTICATION] [LOGIN FAILED] Disabling 32P provider until login error(s) can be fixed in order to avoid temporary bans.
21-Sep-2018 20:46:40 - ERROR :: mylar.valid_login_attempt.545 : Thread-13 : [32P-AUTHENTICATION] Got unexpected status result: {u'status': u'error', u'show_attempts': u'true', u'message': u'You must complete the captcha.', u'attempts': 4, u'twostep': u'false'}
21-Sep-2018 20:46:40 - WARNING :: mylar.login.624 : Thread-13 : [32P-AUTHENTICATION] Both session key and credential-based logins failed.
21-Sep-2018 20:46:40 - ERROR :: mylar.__init__.41 : Thread-13 : [32P-AUTHENTICATION] [LOGIN FAILED] Disabling 32P provider until login error(s) can be fixed in order to avoid temporary bans.
21-Sep-2018 20:54:51 - WARNING :: mylar.Process.384 : Thread-17 : There were no files located - check the debugging logs if you think this is in error.
21-Sep-2018 21:06:40 - ERROR :: mylar.valid_login_attempt.545 : Thread-22 : [32P-AUTHENTICATION] Got unexpected status result: {u'status': u'error', u'show_attempts': u'true', u'message': u'You must complete the captcha.', u'attempts': 4, u'twostep': u'false'}
21-Sep-2018 21:06:40 - WARNING :: mylar.login.624 : Thread-22 : [32P-AUTHENTICATION] Both session key and credential-based logins failed.
21-Sep-2018 21:06:40 - ERROR :: mylar.__init__.41 : Thread-22 : [32P-AUTHENTICATION] [LOGIN FAILED] Disabling 32P provider until login error(s) can be fixed in order to avoid temporary bans.
21-Sep-2018 21:26:40 - ERROR :: mylar.valid_login_attempt.545 : Thread-14 : [32P-AUTHENTICATION] Got unexpected status result: {u'status': u'error', u'show_attempts': u'true', u'message': u'You must complete the captcha.', u'attempts': 5, u'twostep': u'false'}
21-Sep-2018 21:26:40 - WARNING :: mylar.login.624 : Thread-14 : [32P-AUTHENTICATION] Both session key and credential-based logins failed.
21-Sep-2018 21:26:40 - ERROR :: mylar.__init__.41 : Thread-14 : [32P-AUTHENTICATION] [LOGIN FAILED] Disabling 32P provider until login error(s) can be fixed in order to avoid temporary bans.
21-Sep-2018 21:46:40 - ERROR :: mylar.valid_login_attempt.545 : Thread-19 : [32P-AUTHENTICATION] Got unexpected status result: {u'status': u'error', u'show_attempts': u'true', u'message': u'You must complete the captcha.', u'attempts': 6, u'twostep': u'false'}
21-Sep-2018 21:46:40 - WARNING :: mylar.login.624 : Thread-19 : [32P-AUTHENTICATION] Both session key and credential-based logins failed.
21-Sep-2018 21:46:40 - ERROR :: mylar.__init__.41 : Thread-19 : [32P-AUTHENTICATION] [LOGIN FAILED] Disabling 32P provider until login error(s) can be fixed in order to avoid temporary bans.
21-Sep-2018 21:54:51 - WARNING :: mylar.Process.384 : Thread-16 : There were no files located - check the debugging logs if you think this is in error.
21-Sep-2018 22:06:40 - ERROR :: mylar.valid_login_attempt.538 : Thread-20 : [32P-AUTHENTICATION] The data returned by the login page was not JSON: <!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>Error :: 32Pxxxs</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta content="32Pxxxs, The Website Where Comics are #1!" name="description" />
<snip>
<p class="pagedetails">
Your IP has been banned. </p>
</div>
</div>
As you can see, there was an initial failure that doesnt look like a failure, because the login worked well enough to output the entire HTML of the main index page. I know it says "Connection aborted", but thats obviously not true because the whole 32p web page came back. I guess the HTML failed to parse or something.
Then, despite the provider being automatically disabled to prevent bans, after several hours it just started trying again on its own, which eventually led to my IP being banned.
Once again, there was no warning of a problem in the GUI, and no way short of real-time log monitoring to see that it was failing. I guess manually re-testing the connection would have thrown an error, but it isnt really practical to do that every hour of the day.
I dont know if i'll get my 32p account reinstated, because this is now the second time that this has happened and I dont know how many chances they give. Its hard to have trust in the tool when this kind of thing keeps happening tho