-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
after last change NIA version #24
Comments
check account, i don't have this problems on new registered account. |
2015-02-17T15:35:22.172Z - info: [MungeDetector] Trying to use internal munge data. |
Hello, could you help me debug this problem? I don't have accounts currently. Just add one line to output NIA response in file apply patch: patch requestfactory.coffee < patch.txt patch.txt --- requestfactory.coffee 2015-02-19 20:18:21.000000000 +0800
+++ requestfactory.coffee 2015-02-19 20:19:43.000000000 +0800
@@ -198,6 +198,7 @@
if body.trim().length is 0
return new Error 'Empty server response. Please try adding more accounts.'
+ logger.info body
return new Error 'unknown server response'
return null remember to execute |
after i patch :: |
Emm... unreasonable :-( |
I will try later, maybe this account was banned |
2015-02-20T09:12:55.961Z - info: [MungeDetector] Trying to use internal munge data. unbelievable |
so the server just response nothing LOL |
but if i log into web all is ok |
Fixed, account was soft banned, after login on ingress and wait 2 days all is ok. |
Currently ingress exporter doesn't bypass botguard, that's why accounts are easily banned. |
@summerwish have any ideas how to bypass botguard? |
*****ck yeah :: Can we use IITC or not? |
ist there now any solution? |
Today IITC updated, please update the files, get "unknown server response", account is not banned, error persist on new account.
The text was updated successfully, but these errors were encountered: