Host Migration headaches

  • Ok, I am pretty new to this.

    I am moving from managed wordpress hosting from GoDaddy to normal WP hosting where you have access to cPanel and mySQL etc.

    I tried using Duplicator for migration to new host. However, the problem is that the site backup from old host is ~300MB, and the new host does not allow editing of PHP.ini to modify the 50MB upload limit on new host. So I am unable to upload the backup archive to the new server for restoration.

    Does simply copy-pasting folders through FTP work? I know thats a dumb question, but I’d rather spend a day doing that than build the entire website from scratch.

    Are there any other alternatives I can use?

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

  • Normally, you should be able to use FTP to move a site.

    Download (through FTP) all the files from the old site, then upload (also through FTP) all those files to the new site.

    The database can not be uploaded/downloaded with FTP though. I don’t know if the database export is included in the 300MB site backup or if it’s a separate file, but if you have access to the database admin (through phpMyAdmin or another tool), you can do an export of the database from the old site, and then import it on the new site.

    I’m not sure if this will work for you but I’ve found the plugin WP Clone to be pretty miraculous at letting me clone sites to move them.

    Thread Starter tyrannosaurhex

    (@asg1123)

    Alright, so I did a manual file movement through FTP to the new host.

    Then I exported the DB from old host and imported it to the new host using phpMyAdmin. Added new users to the database and wp-config.php.

    Changed the A record in DNS manager to IPs of new host.

    However, the website is not accesible. Anything I may have missed?

    Have you changed your Name servers?

    What is getting displayed when you navigate to your site?

    Thread Starter tyrannosaurhex

    (@asg1123)

    Seems to be working now. i think it was the A record and nameserver update which took time to refresh. Had TTL set to 600 secs but it took 4 hours, lol.

    Thanks.

    Is there anything else I should tale care of?

    BTW, I am kind of worried about the db username, password in wp-config file. How do I check and make sure it is not publicly accessible.

    Hi. Glad to hear it is working.

    Make sure that the permissions on your wp-config.php file are 750 as this is the recommended permission.

    Check this link for more detail:
    https://codex.www.ads-software.com/Hardening_WordPress

    Hope this helps.

    Forgot to say, there is a section in the link above that mentions moving your wp-config.php outside your web root – this is HIGHLY recommended.

    Let me know if you need any help with this (or you don’t understand the instructions at https://codex.www.ads-software.com/Hardening_WordPress ).

    Good luck!

    Moderator Samuel Wood (Otto)

    (@otto42)

    www.ads-software.com Admin

    Seems to be working now. i think it was the A record and nameserver update which took time to refresh. Had TTL set to 600 secs but it took 4 hours, lol.

    FYI: If you actually changed nameservers for the domain to wholly new ones, then that’s a 48 hour wait, minimum. In some cases, parts of the internet may not see your new nameservers for 2 weeks. Changing nameservers is generally something you don’t do lightly.

    If on the other hand you kept the same nameserver, but just changed the A record, then your TTL would indeed come into play. However, TTL’s for records less than 30 minutes typically don’t work very well. It’s recommended to use a TTL of 1800 or higher. One hour (3600) is considered pretty reliable if you really need it. But if you don’t have failover plans and such, then something like 24 hours is better and can give you better overall performance.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Host Migration headaches’ is closed to new replies.