Support

Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Yes. I read, I experimented with options for 3 days. Believe me, if I could have avoided paying for support, I would have.
Joomla! version: (1.7)
PHP version: (5.3)
MySQL version: (unknown)
Host: http://budmcneese.temperedlight.com
Akeeba Backup version: (unknown)

Description of my issue: First of all, akeebabackup is a great tool! I am new to Joomla but have had success with tests of the akeebabackup/restore tool on the local host. Here is the problem:

I am attempting to migrate my site from the local machine to GoDaddy. The restoration seems to work fine. The front end seems to work perfectly fine. I can get to the login page for the backend but, after logging in I am redirected to http://budmcneese.temperedlight.com/index.php and get a 404. I am sure it is something simple I am overlooking but have tried the kickstart restore process a dozen times. The only way I can get it to work is if I create a kicktemp folder at the root and restore from there. Unfortunately, it puts all of my content into the kicktemp folder. i.e. http://budmcneese.temperedlight.com/kicktemp/index.php or http://budmcneese.temperedlight.com/kicktemp/administrator.

Help!

p.s. - Tried to attach the log file but I got a COM MEDIA ERROR.

There are a couple of possibilities that are occuring:

1) An error or issue in the .htaccess file
2) An error in the configuration.php
3) Subdomain configuration at GoDaddy

The first one I'd check is the configuration.php file and the live_site definition. See if it is set correctly to http://budmcneese.temperedlight.com. If it is not, set it that way and then try to login.

The second thing I would try is to rename the .htaccess file in the root of the site. See if there are any potential directives in there that could be causing this.

The third thing is to check your GoDaddy definition of the subdomain. GoDaddy and other cpanel based systems DO allow you to set subdomains to point at a subdirectory of the main directory to store files. This keeps the public_html complete free of sites. In theory, a subdomain IS a subdirectory in the public_html for many systems.

Since the backup did restore without error, I don't feel it is a problem with the backup itself, so the log isn't necessary.