I got that error as well, retried updating a couple of hours later and had no problems