install freezes at "Loading Character Set specific data 59%"

[earmsby]

Could it have anything to do with collation? As far as I can tell from everything I can see in phpMyAdmin the database and tables use UTF, but is it possible that something somewhere else is latin-1 and that is causing a problem? I guess if that were the problem none of the UTF-8 data would be written.

Next, I wonder if the issue has something to do with 1&1. I might try to replicate this install on another server just to see if I get a different result or if the same thing happens.

Meanwhile, if you can think of any other possible reason or possible place for me to look for info that would shed light on the problem, I'd be appreciative.

I'm guessing no one else has reported any problem like this?

Thanks for your help!

[DrByte]

[QUOTE=earmsby;1308471]Could it have anything to do with collation? As far as I can tell from everything I can see in phpMyAdmin the database and tables use UTF, but is it possible that something somewhere else is latin-1 and that is causing a problem? I guess if that were the problem none of the UTF-8 data would be written.
[/code]
For a fresh install I don't see how collation matters in this context.

Next, I wonder if the issue has something to do with 1&1. I might try to replicate this install on another server just to see if I get a different result or if the same thing happens.

Perhaps.

I'm guessing no one else has reported any problem like this?

Nobody.
Of the hundreds of installs I've done, I've not encountered it failing like this, at least not without logging a "why" in the logs.

[lat9]

Are you trying to enable HTTPS from the get-go? 1&1 (shared-server accounts) currently has some "issues" like no support for TLS 1.2 that could be getting in the way.

[earmsby]

Are you trying to enable HTTPS from the get-go? 1&1 (shared-server accounts) currently has some "issues" like no support for TLS 1.2 that could be getting in the way.

Yes, I was using HTTPS from the start because the current live site does. I thought you had to use https to even be able to log into the admin section at all. I guess I try the process again without it just to see what happens and if that makes a difference.

[earmsby]

I guess I can try the process again without it just to see what happens and if that makes a difference.

Tried it without HTTPS at all and still froze adding UTF data.

Next step is to try it on a different server. I'm continuing to suspect it's an issue with 1&1. They lock down a number of things that I have found irritating to get around (like no remote MYSQL access so I can only work with the database through their myphpadmin portal).

[earmsby]

Tried it without HTTPS at all and still froze adding UTF data.

Next step is to try it on a different server. I'm continuing to suspect it's an issue with 1&1. They lock down a number of things that I have found irritating to get around (like no remote MYSQL access so I can only work with the database through their myphpadmin portal).

Ok, I tried running pretty much the exact same install on a different server (BlueHost) this time and the database step ran in a matter of seconds with no problem. So, I think that means I will need to ask the client to put in a support ticket with 1&1. Is there anything I would want to advise him to ask them to look at?

The ironic thing here is that 1&1 is basically forcing him to upgrade to ZC 1.5.5 because of their forced upgrade to php7 in May. But if some setting on their server is tripping this up and preventing him from doing this upgrade then they're planning to charge him extra money for staying on php 5.x