Forgot your username?             Forgot your password?

You need to be a subscriber in order to receive support. If you want to report a bug or ask a pre-sales question, you don't have to be a subscriber. Just use the Contact Us link at the footer of the site.

Subscribe

#9238 – 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

Posted in ‘Akeeba Backup’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Wednesday, 21 December 2011 19:11 UTC
BellaFresca


Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the forum before posting? Yes
Have I read the documentation before posting (which pages?)? No
Joomla! version: 1.5.23
PHP version: (unknown)
MySQL version: (unknown)
Host: (optional, but it helps us help you)
Akeeba Backup version: Akeeba Backup Core3.3.10



Description of my issue:
Greetings. I am attempting to migrate my client's website from a company that is not helpful and in fact is preventing her from resolving some fairly minor issues.

The current website is
www.bella-fresca.com

I have successfully backed up her site and moved it to here:
http://biz100.inmotionhosting.com/~bigass6/bella/

I have confirmed that all the files were correctly installed in the new location, and the Mysql db was migrated over as well. The Joomla backend shows all the articles correctly and all the products, prices etc in Virtuemart are all correct. There were no errors in the kickstart installation.

As you can see, the links do not work and some of the images do not display.

The specific error is:
Not Found

The requested URL /bella/index.php was not found on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

So I searched your excellent troubleshooting documents, specifically this:

https://www.akeebabackup.com/troubleshooter/prbasicts.html

I have checked all the settings described in this document and performed all checks and corrections it recommends.

I spoke with my ISP and they believe that the problem is that the DNS is still set to the original location and that once the DNS is moved to the new location it will work fine.
I believe they are correct, but because the site is live, I want to be 100% certain that everything is correct before I ask for the DNS to be relocated since my client needs it to be a smooth transition.

Your input is greatly appreciated.

Wednesday, 21 December 2011 19:23 UTC
nicholas
AKEEBASUBS, DELUXE
Are you using SEF URLs on that site? If you do, you have to disable that feature while testing your site on the temporary URL; when you attach a regular domain name to the site, you can re-enable them. You may also have to modify the configuration.php's live_site variable and/or remove the .htaccess file, as mentioned in the troubleshooter.

The problem is caused by how Apache works. When using a temporary URL (the one with the /~username/ part inside it) Apache can not handle redirections, the feature which is enabled by .htaccess and which powers the SEF URLs.
Friday, 23 December 2011 00:53 UTC
BellaFresca
yes as stated, I have performed ALL of the steps described in your troubleshooting documents for this issue. My only concern is that I need the problem to be gone when the dns is moved to the new location.

Thanks
Friday, 23 December 2011 08:31 UTC
nicholas
AKEEBASUBS, DELUXE
The thing is, as I said:
The problem is caused by how Apache works. When using a temporary URL (the one with the /~username/ part inside it) Apache can not handle redirections, the feature which is enabled by .htaccess and which powers the SEF URLs.


There are two ways to test:
- Attach the regular domain name, wiat for the DNS to propagate and hope for the best. This usually works.
- Do you have a domain name registered you don't really use? You can add it to your site, test it and when you're done, remove it. I have half a dozen of domain names I don't use and I use them exactly for this reason :)
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.