Moved my site to a new server. Now it doesn't work!

[DorianJ]

As stated, I moved my site to a new server. The main catalog/index.php page loads, but everything else does not work. It has something to do with the .htaccess files (and possibly the Ultimate SEO contribution).

 

If I change the .htaccess file to Rewrite Engine Off then it loads a page that says...

 

Forbidden

You don't have permission to access /catalog/product_info.php on this server.

 

If I turn the rewrite engine on, then it rewrites the URL into a huge line ending in .html and loads an error 404 not found page.

 

.htaccess has given a problem EVERY time for EVERY web site that I've ever had to move to another server. Why can't these files simply be copied over to a new server and work like they did on the previous server? Very frustrating because now my store is offline.

[davidinottawa]

As stated, I moved my site to a new server. The main catalog/index.php page loads, but everything else does not work. It has something to do with the .htaccess files (and possibly the Ultimate SEO contribution).

 

If I change the .htaccess file to Rewrite Engine Off then it loads a page that says...

 

Forbidden

You don't have permission to access /catalog/product_info.php on this server.

 

If I turn the rewrite engine on, then it rewrites the URL into a huge line ending in .html and loads an error 404 not found page.

 

.htaccess has given a problem EVERY time for EVERY web site that I've ever had to move to another server. Why can't these files simply be copied over to a new server and work like they did on the previous server? Very frustrating because now my store is offline.

 

 

LOL!

 

It's not the *file* where the issue lies - it's the *server*.

 

Each host has the right to set up their server in any way that they please - so each server will be have the same Apache configuration.

You can utilize the htaccess file to accommodate for Apache directives that are either included and you don't want them, or not included and you want them to be from the basic setup provided by your host.

 

Do you have real paths in your htaccess file that you are referencing ?

i.e. /home/usr/username/htdocs/public_html/catalog

, etc ?

If so - then the paths will need to be updated.

 

Same goes for your includes/configure.php file. You may be using full paths that were true on the old server, but will obviously not be valid on the new server.

 

david

[DorianJ]

The server was with the same host so all the settings were the same. I fixed the problem by going to the Admin UI and clearing the cache for the Ultimate SEO settings. Now the site loads and all products can be viewed, however...

 

the checkout procedure doesn't work! It loads a screen that says,

 

"Forbidden

 

You don't have permission to access /checkout_shipping.php on this server.

 

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

 

I changed the permissions to 777 and it still says there is not permission. What could possibly be causing this?

[Guest]

The server was with the same host so all the settings were the same. I fixed the problem by going to the Admin UI and clearing the cache for the Ultimate SEO settings. Now the site loads and all products can be viewed, however...

 

the checkout procedure doesn't work! It loads a screen that says,

 

"Forbidden

 

You don't have permission to access /checkout_shipping.php on this server.

 

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

 

I changed the permissions to 777 and it still says there is not permission. What could possibly be causing this?

 

Are you chmoding using your ftp client ?

If so - try your file manager in your control panel with your host instead.

[DorianJ]

Yes, I always use the File Manager in cPanel to chmod. It's not working. Could this be an issue with the SSL certificate?

[Guest]

Yes, I always use the File Manager in cPanel to chmod. It's not working. Could this be an issue with the SSL certificate?

 

 

Well----- no.

 

There error is clear :

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

 

Are you sure you have your includes/configure.php file set up properly ?

http://www.oscommerce.com/forums/index.php?showtopic=193738

[DorianJ]

Yes, the config files are correct. I double checked them, but they didn't need any changes. I'm still with the same host, just on a different server.

[Guest]

Yes, the config files are correct. I double checked them, but they didn't need any changes. I'm still with the same host, just on a different server.

 

 

well - my guess is something somewhere is referincing an old path.

do you have ssh ?

 

if so - get a value from your path like the vlaue before the public_html and grep for it like this :

xargs grep <username> *.php

[DorianJ]

get a value from your path like the vlaue before the public_html and grep for it like this :

xargs grep <username> *.php

Any chance you can post a step-by-step for this? Kinda vague to me.

[DorianJ]

PROBLEM SOLVED!!!

 

It WAS an issue with the SSL Security Certificate!

 

When a certificate is signed for a web site by a CA, the public and private keys get created for the EXACT web server that the site is running on. Therefore, if you move the site to a new server, your SSL Certificate must be re-keyed to match a new key generated by this new server. (I won't go into details about how to do this -- your host will help you out.) Otherwise, the certificate is trying to secure a site that it thinks doesn't exist because the public and private keys are not matching up and therefore you get Error 403!

 

This is an issue only for the secure pages of your web site (ie: all the "checkout_" pages, create account pages, etc). If your configure.php file has a line that reads this:

 

define('ENABLE_SSL', true);

 

then you will get 403 Error when trying to access any secure (https) page when the SSL cert has not been set up properly. In order to fix this (temporarily, of course) you will need to change that line to read:

 

define('ENABLE_SSL', false);

 

but doing this will mean that your store will not be encrypting anything when SSL is turned off.