Upgrading to 4.2.3 stuck at 83%

[Jason92s]

I've been stuck at 83% for about 30 minutes. Any suggestions? Can I refresh? Start the whole process over? Many thanks.

[Mark.B]

Just refresh the page, it should carry on.

[Teascu Dorin]

Just refresh the page, it should carry on.

Do you consider this being something normal?
Since it was created, every time I upgrade needs at least 1 or 2 refreshes to finalize the installation.
On another hand, on almost all other languages used with vBulletin 5 the dates and hours are not working and vBulletin is aware of this but no one does anything!

Not professional at all!

[Mark.B]

Do you consider this being something normal?
Since it was created, every time I upgrade needs at least 1 or 2 refreshes to finalize the installation.
On another hand, on almost all other languages used with vBulletin 5 the dates and hours are not working and vBulletin is aware of this but no one does anything!

Not professional at all!

It's down to the server, not vBulletin.

Modern servers tend to have ever stricter limits to prevent attacks, and an upgrade can easily trigger those.

Nothing can be done about it from our end. Usually it just needs a refresh to carry on.

The server I use runs a live 4.2.3 and a demo 5.2.2. Both have been upgraded dozens of times and I've never once needed to refresh. It is poorly configured servers.

GoDaddy is particularly bad with having to refresh, even on a fresh install. I would personally not use GoDaddy to host so much as a 404 page!

As for the language problems, there are open bug reports for those. They will get fixed at some point.