Migration failed: Unexpected token '
under review
P
Preston Ciere
Yes, this displayed as soon as the migration started, at initialization. I've attached a screenshot. The plugin's error log doesn't provide any details.
Kevin Hoffman
Preston Ciere: Thanks for clarifying. To start a migration, the plugin sends a REST API request to the
initiate-migration
endpoint. "Unexpected token" is a JavaScript error that suggests the response was not valid JSON.To better diagnose the error in your browser, can you please open your browser's DevTools and try the process again? When the "Initialization failed" error appears on screen, check the Console tab and Network tab of DevTools. In the Network tab, select the
initiate-migration
request and then open the Response tab. Please screenshot or pass along any errors that you see.See the attached screenshot for reference.
P
Preston Ciere
Kevin Hoffman No console errors. Attached is the screenshot. I'll also paste the response from the "initiate-migration" request. However, another request did provide an error - see second screenshot.
Kevin Hoffman
Preston Ciere: Thanks, I copied the info you shared and deleted those comments. Looking into it now.
Kevin Hoffman
Preston Ciere: I searched the following string from your response and came across a few troubleshooting articles.
"The requested URL was rejected. Please consult with your administrator."
The common solution recommended across these articles is to clear cache and cookies. Can you try that? Another possible explanation is a firewall configuration issue.
- https://www.intel.com/content/www/us/en/support/articles/000090806/programs.html
- https://stackoverflow.com/questions/8892197/how-to-resolve-the-requested-url-was-rejected-please-consult-with-your-adminis
Kevin Hoffman
under review
Kevin Hoffman
Hi Preston Ciere. I'm the product manager of the WP Engine Site Migration plugin. Thanks for passing along this feedback. The old plugin is no longer available but I will be happy to help troubleshoot this issue with you.
Can you please clarify where you were at in the plugin when this error occurred?