I have the same issue and have tried all the different ways to correct it- no luck.
Maybe a compromised log in code?
