Closed pacobarbe31 closed 1 year ago
dmarts05
commented
1 year ago That's interesting. Remove --session parameter, redeem feature is working well on my end. Email alerts only happen when an account gets locked, banned... I will try to add support for other kind of alerts soon.
BTW, what have you exactly specified in "goal"?
RustyRin
commented
1 year ago I am also having issues with auto-redeem and emails. An account got locked, it said it was going to send and email but I never got it.
********************ms_account_email@gmail.com********************
[LOGIN] Logging-in...
[LOGIN] Writing email...
[LOGIN] Writing password...
[EMAIL SENDER] This account has been locked! Sending email...My email config looks like this
[
{
"sender": "my_email@gmail.com",
"password": "gmail_app_password_here",
"receiver": "my_email@gmail.com",
"withdrawal": "true",
"lock": "true",
"ban": "true",
"phoneverification": "true",
"proxyfail": "true"
}
]For auto-redeem, idk if I am setting the goal wrong, but it does not seem to be reading that there is a goal at all. on each account I have tried
{
"username": "rin.new.spam@gmail.com",
"password": "apZxogmchKuZfFjkJo7R",
"goal": "Overwatch Digital Code"
}I have also changed the goal to "Overwatch Digital Code—200 Coins", but this also did not work.
dmarts05
commented
1 year ago I am also having issues with auto-redeem and emails. An account got locked, it said it was going to send and email but I never got it.
********************ms_account_email@gmail.com******************** [LOGIN] Logging-in... [LOGIN] Writing email... [LOGIN] Writing password... [EMAIL SENDER] This account has been locked! Sending email...My email config looks like this
[ { "sender": "my_email@gmail.com", "password": "gmail_app_password_here", "receiver": "my_email@gmail.com", "withdrawal": "true", "lock": "true", "ban": "true", "phoneverification": "true", "proxyfail": "true" } ]For auto-redeem, idk if I am setting the goal wrong, but it does not seem to be reading that there is a goal at all. on each account I have tried
{ "username": "rin.new.spam@gmail.com", "password": "apZxogmchKuZfFjkJo7R", "goal": "Overwatch Digital Code" }I have also changed the goal to "Overwatch Digital Code—200 Coins", but this also did not work.
Email alerts are working on my end. Have you set up 2FA in that Gmail account? Have you generated an app password for this purpose and put in the json correctly? If your answer is yes to both questions I don't really know how to help you sorry.
For your auto-redeem problem, try disabling headless mode and watch carefully during the auto-redeem process, it is possible that it's not finding you reward (send me a screenshot or video). Remember to put --redeem as a parameter.
RustyRin
commented
1 year ago --emailalerts --redeemdmarts05
commented
1 year ago
- I have 2FA
- I have ran it headless and not headless, same results
- I have also added the arguments
--emailalerts --redeem- I do had app password. Though idk if this is just formatting or not, but Google had it separated into 4 sections of 4 characters. It says to just use all 16, so I copied all 16 and used it. Further, Google also says that the app password was never used.
Please, provide a screenshot or video during the auto-redeem process so I can see what the problem is. Have you configured the app password as Other? Copy the characters without spaces.
pacobarbe31
commented
1 year ago Sorry for the late, after building a new environment on VPS, with fresh install, I actually get emails from blocked accounts or other emails type.
I think that auto redeem feature doesn't work because the parameter --headless was activated, and without this parameter I couldn't lauch the script due to an error :
I've found that some people have the same problem, probably because I installed chrome manually (see : compatibility on VPS)
I actually try to resolve this error, I will try proposed solutions and I will come back if solution was find for me.
Thank you for your help !
dmarts05
commented
1 year ago It was all due to an indentation error. Auto-redeem has been fixed in my latest pull request. Update your script and it should work now.
dmarts05
commented
1 year ago Sorry for the late, after building a new environment on VPS, with fresh install, I actually get emails from blocked accounts or other emails type.
I think that auto redeem feature doesn't work because the parameter --headless was activated, and without this parameter I couldn't lauch the script due to an error :
I've found that some people have the same problem, probably because I installed chrome manually (see : compatibility on VPS)
I actually try to resolve this error, I will try proposed solutions and I will come back if solution was find for me.
Thank you for your help !
You need headless mode for a VPS, check my latest pull request, auto-redeem is fixed now.
pacobarbe31
commented
1 year ago Sorry for the late, after building a new environment on VPS, with fresh install, I actually get emails from blocked accounts or other emails type. I think that auto redeem feature doesn't work because the parameter --headless was activated, and without this parameter I couldn't lauch the script due to an error :
You need headless mode for a VPS, check my latest pull request, auto-redeem is fixed now.
You're the best ! thank you for your help, it was the indentation ! Thanks for this fix :)
All my accounts need a phone verification to be redeemed actually, I think because they are Microsoft accounts and not gmail accounts used for the bot.
RustyRin
commented
1 year ago
- I have 2FA
- I have ran it headless and not headless, same results
- I have also added the arguments
--emailalerts --redeem- I do had app password. Though idk if this is just formatting or not, but Google had it separated into 4 sections of 4 characters. It says to just use all 16, so I copied all 16 and used it. Further, Google also says that the app password was never used.
Please, provide a screenshot or video during the auto-redeem process so I can see what the problem is. Have you configured the app password as Other? Copy the characters without spaces.
I know its closed now, it is not that big of deal.
But the script just doesn't seem to really recognize that redeem is on.
The only recognition of it is at the start of the script
This was with --headless --redeem --emailalerts
[INFO] everyday : None
[INFO] headless : True
[INFO] session : False
[INFO] error : False
[INFO] fast : False
[INFO] accounts : None
[INFO] proxies : None
[INFO] authproxies : False
[INFO] privacy : False
[INFO] emailalerts : True
[INFO] redeem : TrueI never again see anything in the terminal about redeeming.
For emails, there is no space.
qwertyuiopasdfgh kinda looking
Only thing is that I have the same address for sending and receiving, for self email.
I have changed it to a different receiver email, but really only been able to test it when an account gets locked or banned. Which has yet to happen since editing it.
Hello,
I've the last version of this great MicrosoftRewardsClaimer, thank you again for this great work. I've 6 accounts that farm very well (just one that is blocked actually). Some of my accounts now have points to be redeem (Amazon gift cards in UK), but nothing happend when I launch the script. I have all parameters specified :
python3 MicrosoftRewardsBot.py --emailalerts --redeem --headless --session --fast:accounts.jsonhave goals specified on each account,email.jsonhave also all parameters (with 2FA password app). I have no errors in logs :Maybe the
--headlessscript mod can't activate email and auto-redeem ? Or problem is probably based on my environment ? I launch this script in a private server in cloud (ubuntu with 1vcpu and 1gb).Thank you for your help !