This is the first report we’ve had for this issue. I’d suggest retrying at a different time of day. You might have been unlucky and happened to update at the same time that the web team were making changes to the web server.
We’re looking into the issue now. Let us know if the problem persists.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic.