Prevent DNS issues after a completed migration
under review
R
Robert Flarity
Every time I've attempted to transfer a wordpress site using the migration tool within WPE's Site Migration tab it has always brought over a broken, nonfunctional mess. The BlogVault migration plugin however has worked flawlessly. Is there any guarantee that these issues will be resolved since the BlogVault plugin is reaching end of life? I assumed there would be no way to continue using that plugin after the end of life date.
Kevin Hoffman
under review
Please note since we have received a few posts about general differences between the new and old plugins, I've renamed this post to focus specifically on the DNS issue so that others who experience it might find it more easily.
R
Robert Flarity
This is specifically issues with the plugin downloaded from the steps on the Site Migration tab, wpe-site-migration-1.0.0-beta.23.zip
Kevin Hoffman
Robert Flarity: Thank you for the feedback. I'm the product manager of the WP Engine Site Migration plugin. We will do everything we can to make sure you have a reliable migration method going forward. I tried to look up past migrations that used your email, but only found one "completed" migration on January 18th.
Has it been your experience that the migration completes, but the site is is left in a broken state? If so, please share more about what is broken. I'm also going to reach out via email if you are more comfortable sharing details there.
R
Robert Flarity
Kevin Hoffman: Hey, thanks for writing back! On the 18th I actually used the plugin that utilizes BlogVault, not the one thats downloadable on the wpe site migration page. I've included a photo of where I'm talking about just to make sure its clear which was the one I used that had issues. I attempted to use that one on the day before and the site had some strange DNS issues that didnt make any sense. For some reason on that transfer, setting PHP to 7.4 (as this is an outdated site I need to update) caused the SSL to not resolve and some odd DNS errors while the site would show on PHP 8.2 but would critical error due to deprecated PHP. I've had similar odd issues when attempting to use this plugin as opposed to this one: https://wordpress.org/plugins/wp-site-migrate/. This one works perfectly.
Kevin Hoffman
Robert Flarity: Yep we're talking about the same plugin and the same migration. It might have appeared as Jan 18 on our end because the timestamp was UTC.
Our plugin does not make any changes to DNS as a result of the migration so I'm having trouble pinpointing what could have gone wrong. Can you provide any more detail on the DNS errors you mentioned, where you saw the errors or what they said?
(Also I removed your screenshot because your Support Pin was visible.)
R
Robert Flarity
Kevin Hoffman: Thank you for that! I cant provide too much info as when there were apparent issues I went to use the blogvault migration plugin. I do have a few screenshots I can show though, the browsers response to trying to reach the site after it was brought over and how the domains tab looked.
Kevin Hoffman
Robert Flarity: Thanks that's helpful! It is strange that the Chrome screenshot shows
www
because that should never be included with our wpenginepowered.com
URLs. I just checked the following URLs and the version with www
shows that error, while removing www
allows the site to load:This is to be expected since the
www
version is not actually listed on your Domains page. Do you happen to remember how you got to that URL, whether you typed it in by hand or clicked a link somewhere in the User Portal?R
Robert Flarity
Kevin Hoffman: I believe I simply clicked the link at the top of the portal
Kevin Hoffman
Robert Flarity: Thank you for that info. I've been unable to replicate a scenario where the User Portal includes a link with
www
but I have reached out to my colleagues to see if they are aware of any similar reports.