Apparently this issue was resolved as of 3am EDT this morning, you should no longer experience this error
View solution in original post
