- This topic has 7 replies, 5 voices, and was last updated 5 years, 3 months ago by Wes9999.
February 13, 2017 at 11:02 am #193918developpeurParticipant
I just bought your product.
I was suprised : i can’t simply import remote backup to my localhost website.
I know you can sent a backup with a key but why we can’t import a backup with a key.
It makes more sense to plan to send in both directions because localhost website can ask to get a backup but remote website can’t sent a backup to a localhost.
Is it normal or i missed something ?
Others plugins like wp migrate pro has this important feature but not updraftplus ?
If so, I’m disappointed :(February 13, 2017 at 7:18 pm #194023Dee NutbourneModerator
There is no functionality to request a direct site-to-site backup from the receiving site.
However, there are several alternative methods to transfer backup files to the new site.
These can be found in Step 3 of our migration guide:
David NFebruary 14, 2017 at 8:05 am #194121developpeurParticipant
Thank you for your answer.
I know (for the moment i use another method : i use the remote website as remote storage and i import backups) but it would be cool to permit a 2 way sync with key system because it’s more simple than add ftp credentials or manually download backups.
This is a suggestion.September 14, 2017 at 11:57 pm #229826HeatherParticipant
I just purchased as well, and am very disappointed to not have support for migrating to localhost. That was the big reason I bought this plugin in the first place. I wouldn’t have paid, had I realized.September 19, 2017 at 10:26 am #230463Dee NutbourneModerator
I’m afraid that direct site-to-site migration to localhost sites is not possible because localhost is not a valid domain. As such, there is no way for UpdraftPlus to determine where to send the backup.
However, you can use one of the alternative transfer methods found in the following guide to migrate to a localhost site:
David NApril 30, 2018 at 8:55 pm #278177Wes9999Participant
I would love it if this could be addressed as a feature request. I see I am not the only one who wishes for the destination site to pull the backup from the source site. This would be handy in 2 scenarios. 1. you are testing with a local installation and want to pull down live site to local and then push local changes back to live site on internet.
2. You are migrating from one server to another and the destination site is not resolving the url with DNS yet. example: mysite.com resolves to 18.104.22.168 on the internet. I want to copy contents of that site to another web host where I have set up mysite.com and they are at ip 22.214.171.124 but mysite.com does not resolve YET to 126.96.36.199. Therefore I can’t tell my source site on 123 to push to my destination site because the destination doesn’t resolve publicly yet.June 18, 2018 at 6:07 pm #288497mags1Participant
I am also trying to restore a website to my localhost. I backed up original website, downloaded backup, performed restore on localhost/wordpress (I am using Bitnami stack). I did not select rename “Search and replace site location in the database (migrate)” as I tried initially and then later read in your documentation that that would not work with a local restore. When I try to launch website it fails completely. I edited wp-config.php ” define(‘WP_SITEURL’, ‘https://localhost/wordpress’); define(‘WP_HOME’, WP_SITEURL);” and the site still will not load. What else do I need to change or edit in order to run this copy of my website locally?
MCJJune 18, 2018 at 7:11 pm #288508Wes9999Participant
for anyone struggling with local development, this tool from flywheel is pretty good
mags1, if you have a localhost installation working correctly before the restore, you should select “search and replace” as this will change your links to all use https://localhost instead of the regular website url.
If your localhost installation is NOT working correctly before doing the restore, maybe try flywheel to get that part going and then try the restore again this time choosing “search and replace”.
- The topic ‘Migrate remote to localhost’ is closed to new replies.