The error may be cached. Can you try logging in from a private browser window and/or clearing your cache for the site? Let me know if it works now. I was experiencing the same error, but it works fine now. I suspect the error is being cached.