>>770
i had this happen a few times the first day or so when i kept refreshing too before it started giving the actual error