Yes, I'm also getting this error. Tried 2 different times to chat with support and all it did was waste my time. Issue began 8/1.
