Moving servers

[Seahawk]

We have had a successful site running for 8 months and it has been great to use.

We have only accepted PayPal on the site but decided to implement the credit card module. As part of this, we asked our web host company for an SSL certificate.

The server the site was hosted on could not support SSL for some reason and so the technical staff moved all of the files over to a different server. The site no longer works, the home page showing "System Setup required." None of the files have been changed and the hosting company is the same as before. They also host our data base, so no change there.

Do we have to re-install Zen Cart or is it a simple case of changing the two configuration files: includes/configure.php and /admin/includes/configure.php files to reflect the new server pathway?

We are running Zen Cart 1.3.8a. We have found it to be stable and have the view that if something works, leave it! We are not developers or computer experts, so be gentle with us!

Regards
Nigel& Sarah

[DrByte]

The correct way to move from server to server is described here: https://www.zen-cart.com/tutorials/i...hp?article=100
The method explained there is intentional since it builds the correct configure.php files content for you, without making you guess what needs to be put in each spot.
That said, yes, you just need to make sure the configure.php files contain the right values for the server you're on.

As far as using the outdated v1.3.8a, do take note that there were some serious security vulnerabilities in that version. You should make sure you've applied all the patches, and/or upgrade to the latest version, else you risk getting hacked.

[Seahawk]

Hello,

Thank you and noted on the old version. Is it possible to make the new install using the new version straight away or should I use the old one and then upgrade?

[DrByte]

Either way is fine.

[Seahawk]

Many thanks for all your help - site is running well on its new, faster server!.

The SSL certificate has been set up in the last 24 hours and I am now having problems with that. It is a dedicated certificate, not shared. I have followed the instructions in the FAQs about changing the two config files to display TRUE in both ENABLE_SSL and ENABLE_SSL_CATALOG and SSL_ADMIN. No luck; I saw an error 404 page in both instances, even after clearing the browser cache and restarting and all the other usual work rounds. As always, I am probably missing something obvious...

The support guys at my ISP assures me the Cert is okay, so any pointers would be appreciated please!

BTW, once this is sorted out, the next exciting instalment is the upgrade!! Phew!

[DrByte]

If you're asking for input on that, a domain name would help.

[Seahawk]

The config files data is the following:

/*************** NOTE: This file is similar, but DIFFERENT from the "admin" version of configure.php. ***********/
/*************** The 2 files should be kept separate and not used to overwrite each other. ***********/

// Define the webserver and path parameters
// HTTP_SERVER is your Main webserver: eg-http://www.your_domain.com
// HTTPS_SERVER is your Secure webserver: eg-https://www.your_domain.com
define('HTTP_SERVER', 'http://www.nairnshire-modelling-supplies.co.uk');
define('HTTPS_SERVER', 'https://www.nairnshire-modelling-supplies.co.uk');

// Use secure webserver for checkout procedure?
define('ENABLE_SSL', 'true');

// NOTE: be sure to leave the trailing '/' at the end of these lines if you make changes!
// * DIR_WS_* = Webserver directories (virtual/URL)
// these paths are relative to top of your webspace ... (ie: under the public_html or httpdocs folder)
define('DIR_WS_CATALOG', '/');
define('DIR_WS_HTTPS_CATALOG', '/');

define('DIR_WS_IMAGES', 'images/');
define('DIR_WS_INCLUDES', 'includes/');
define('DIR_WS_FUNCTIONS', DIR_WS_INCLUDES . 'functions/');
define('DIR_WS_CLASSES', DIR_WS_INCLUDES . 'classes/');
define('DIR_WS_MODULES', DIR_WS_INCLUDES . 'modules/');
define('DIR_WS_LANGUAGES', DIR_WS_INCLUDES . 'languages/');
define('DIR_WS_DOWNLOAD_PUBLIC', DIR_WS_CATALOG . 'pub/');
define('DIR_WS_TEMPLATES', DIR_WS_INCLUDES . 'templates/');

define('DIR_WS_PHPBB', '/');

// * DIR_FS_* = Filesystem directories (local/physical)
//the following path is a COMPLETE path to your Zen Cart files. eg: /var/www/vhost/accountname/public_html/store/
define('DIR_FS_CATALOG', '/home/sites/xxxxxxx/httpd/htdocs/');

-------------------------------
As does the admin/includes/configuration file (with its slight differences).

I am assuming I do not have to have any folders in the https folder which was provided when the certificate was set up. I do not want the whole site SSL protected.

[DrByte]

ROFL. That's a self-signed certificate. It's not a legitimate SSL certificate. Whatever you've gotten needs to be removed and a real certificate put in place. Until then you'll just keep getting errors when trying to look at your site in SSL mode.

Further, if your hosting company has pointed your SSL traffic into an "https" folder, then they're forcing you into having to duplicate your entire site everytime you do an update. That's a very poor server configuration (very old-school, actually). If they have any clue what they're doing they'll point the SSL traffic to your main httpd/htdocs folder so Zen Cart can handle when to go into SSL mode or not. If they can't do that for you, find a host who can.

[Seahawk]

Many thanks for your help so far.

I am sorry for being thick, but what is a self-signed certificate and how does it differ from a legit one?

I thought I had bought a legit one from the hosting company.

bear in mind when answering, I am no expert at this sort of computing - although learning very rapidly...

I am beginning to think that I meed to move my site to a host that specialises in ZenCart sites...

Regards,

Nigel

[DrByte]

Tell your hosting company that the certificate they've put on your site is self-signed, and not issued by a Trusted Authority.
They'll know exactly what that means, and should fix it up in a couple minutes if they actually did buy a legit certificate for you.

And tell them to visit your HTTPS address: https://www.nairnshire-modelling-supplies.co.uk and see for themselves that the server is clearly not configured properly for SSL on your domain.