.htaccess file in Home Folder

I was recently migrating an account from InMotion Hosting to Reclaim (why yes, we do provides free migrations). InMotion uses cPanel, so that usually means the migration will be dead simple. But for some reason after I had migrated everything the site was still not resolving. I discovered this when I went to import the existing WordPress site into Installatron. The import failed and I got the following error:

! PHP for the selected domain has failed. Installatron is unable to install to a domain where PHP is not working. Error code: 2; HTTP code: 200

This is usually an .htaccess issue, so I deleted the existing .htaccess file in public_html to no effect. I then searched high and low on the web to find a solution, but nothing doing. I remember Tim talking about a similar issue he had, when he discovered, purely by chance, there was another .htaccess file in the home directory that was preventing the site from loading given it was requiring a different version of PHP. I checked the home directory and sure enough there was an .htaccess file there calling for a different version of PHP. I deleted the file and the problem was solved.

I leave this here as a breadcrumb for the next person who has this issue but can’t find the solution for the life of them. Sharing is caring 🙂

This entry was posted in reclaim and tagged , , . Bookmark the permalink.

2 Responses to .htaccess file in Home Folder

  1. Alan Levine says:

    Dorothy once blogged that there was no .htaccess like home .htaccess– when you say “home” is the the root directory e.g. the one above public_html? Or?

  2. Reverend says:

    Yeah, it is the home directory for that user, so it would be the directory above public_html, usually the cPanel username like cogdogbl or jimgroom or greatblo….not the home with all the user account on cPanel, that might create all sorts of issues 🙂

Leave a Reply to Reverend Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.