400 undefined during database restore

benhen31
(@benhen31)

8 years ago
Hi,

When attempting to do a local restore of the database x-cloner reads the database file, then when attempting the restore errors out with a ‘400 undefined’ error. The restore is half completed, meaning I’m then locked out of the WordPress admin, as the site url has been changed to that of the source site, but the search/replace hasn’t yet been executed. So wp keeps redirecting back to the source url when I try and login.

Tried spinning up a new WordPress install several times with the same result. What could be the cause?

The log seems to have no relevant errors:

[ SNIP ]
- This topic was modified 8 years ago by Jan Dembowski.

Viewing 6 replies - 1 through 6 (of 6 total)

Moderator Jan Dembowski
(@jdembowski)

Forum Moderator and Brute Squad

8 years ago

Please don’t post log data here. After 10 lines it becomes unreadable.

If you need to share that please use https://pastebin.com/ and share a link to that paste instead.

XCloner
(@xcloner)

8 years ago

Have you tried using another database so you don’t replace your existing site tables?

Thread Starter benhen31
(@benhen31)

8 years ago

Here’s the log on pastebin:https://pastebin.com/bJfecRuX

Hi Liuta,

I haven’t tried that yet, I was just following the on screen restore wizard. I’ll try that.

Thanks,
Ben.

Thread Starter benhen31
(@benhen31)

8 years ago

Just tried it with a clean db. Same error:
https://screencast.com/t/zYzEnV7cNFe

XCloner
(@xcloner)

8 years ago

For some reason, you are still overriding your existing database, please check the wp-config.php file to see which database is in use

Thread Starter benhen31
(@benhen31)

8 years ago

So, got a little further. It turned out I missed the s from https on the search/replace step.

However, now that I’ve corrected that, the restore gets a bit further and then errors with a 400 ‘bad request’ right near the end. I end up with an almost restored site, but with some bits missing.

The problem seems to be that when x-cloner restores the database it’s overwriting the wp login session info that’s stored in the database, so when x-cloner moves to the next instruction after doing that it throws an error, since I’m no longer logged in. This means the restore can never complete.
Other people seem to be able to restore fine though using the WordPress interface so there must be something I’m missing? What could that be. Are there some tables I should be excluding from the source backup to avoid this?

Thanks,
Ben.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘400 undefined during database restore’ is closed to new replies.