Facebook
Twitter- Server operating system version
- Ubuntu 22.4
- Plesk version and microupdate number
- 18.0.71#2
Before moving our staging, newly build, website to production. I wanted to move the current production website to the dev.example.com subdomain.
The move seems to be done well, all documents seem to be present.
Even the maintenance state was copied over.
However:
* wp-toolkit keeps reporting the site as broken
* ERR [
{extension/wp-toolkit} failed to reset cache for instance #X reason: Error: site 'dev.example.com/' not found. Verify DOMAIN_CURRENT_SITE matches an existing site or use --url=<url> to override.
* error is proeprted reported twice, then a line telling me there is a broken wordpress instance found then twice again.
DNS checks all out okay, all records are correct and resolvable. Yes also checked externally
SOmehow somwhere wp-toolkit doesn't get it and is unable to resolve.
And yes DOMAIN_CURRENT_SITE is correct as well, even the details in the instances table in the wp-toolkit sqlite3 db is set correctly.
I even have tried detaching it, cleaning if present the remaining entries in the sqlite3 database and scanning for it again, no luck.
Any suggestions to get this working again? I want to have this fixed before even attempting a move from staging to production in case I run into the same errors.
The move seems to be done well, all documents seem to be present.
Even the maintenance state was copied over.
However:
* wp-toolkit keeps reporting the site as broken
* ERR [
{extension/wp-toolkit} failed to reset cache for instance #X reason: Error: site 'dev.example.com/' not found. Verify DOMAIN_CURRENT_SITE matches an existing site or use --url=<url> to override.
* error is proeprted reported twice, then a line telling me there is a broken wordpress instance found then twice again.
DNS checks all out okay, all records are correct and resolvable. Yes also checked externally
SOmehow somwhere wp-toolkit doesn't get it and is unable to resolve.
And yes DOMAIN_CURRENT_SITE is correct as well, even the details in the instances table in the wp-toolkit sqlite3 db is set correctly.
I even have tried detaching it, cleaning if present the remaining entries in the sqlite3 database and scanning for it again, no luck.
Any suggestions to get this working again? I want to have this fixed before even attempting a move from staging to production in case I run into the same errors.
