Checkout links/button just goes to the Cart page

Hi
I have a site which has just recently been taken out of Maintenance Mode after the summer (it sells winter fuels).
Now, when I try to go to the checkout it just reloads the Cart (It also shows customers as logged out when they go to a product page even though they're still logged in - don't know if this is connected but Guest checkout is enabled).

The address is http://www.freddie-flame.co.uk/index.php (I've put up an html holding page while I try and sort out the Problem).

I'm using the 'RealEx Remote Credit/Debit 3D Secure' payment extension which was working perfectly earlier in the year.

Many thanks

Works fine for me. Takes me to checkout

Sorry, I've since changed the payment system to Paypal because the client was desperate to sell!
It seems its a problem with the SSL Certificate which was needed for the Realex payments, because when I disabled that it worked (with Paypal).
The SSL expired a few weeks ago because the client decided to drop Realex, then they decided to keep it along side Paypal so I ordered a new one which was installed ok. Despite none of the settings changing and the admin area working ok with it, thats when the 'add to cart' button problem started.
At least I know now its related to the SSL, I just need to re-enable it at some point to test it again!

You can't just enable SSL and expect it to work. You need to make sure to change BOTH of your config.php files to https in the appropriate places.

Good point. The config files remained the same (setup for working with SSL) from the previous Certificate. Nothing changed in the Opencart setup from when it was working fine with the old SSL to when I installed the new one. Is there something other than the config files that I've missed? It seems letting one SSL expire and just installing a new one has upset things somehow...

No, then the SSL is not installed right if everything else is correct.

Thanks for that - I'll get back on to the hosting company....

I've just had to revisit this because my client had wanted to leave the site alone for a while as it was working with Paypal.
I now need to get the SSL sorted again, however!

I got this back from my hosts saying it must be in the setup of opencart somehow:

Here's a wget attempt on that SSL address:

$ wget https://www.freddie-flame.co.uk/index.p ... t/checkout
--2013-09-28 15:44:56-- https://www.freddie-flame.co.uk/index.p ... t/checkout
Resolving http://www.freddie-flame.co.uk... 176.32.227.117
Connecting to http://www.freddie-flame.co.uk|176.32.227.117|:443... connected.
HTTP request sent, awaiting response... 302
Location: http://www.freddie-flame.co.uk/index.ph ... ckout/cart [following]
--2013-09-28 15:44:56-- http://www.freddie-flame.co.uk/index.ph ... ckout/cart
Connecting to http://www.freddie-flame.co.uk|176.32.227.117|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `index.php?route=checkout%2Fcart.1'

[ <=> ] 8,814 --.-K/s in 0s

2013-09-28 15:44:57 (824 MB/s) - `index.php?route=checkout%2Fcart.1' saved [8814]

As can be seen here, there is a 302 redirect away from the https address, to the http address instead. This can't be due to our systems in any way, especially as the wget logs above show the SSL connection itself (on port 443) working. There must be some part of your site scripts, or your site's .htaccess file, causing this redirect.

I'm afraid I don't fully understand the above - can anyone shed any light?

I never previously touched the htaccess file when setting up the SSL originally. I've got SEO URLs turned on with a .htaccess file (turned that off but no difference)

many thanks...

On the advice of the hosting company I have changed the config file to force the site into SSL always and that seems to have fixed it!

// HTTP
define('HTTP_SERVER', 'https://www.freddie-flame.co.uk/');
define('HTTP_IMAGE', 'https://www.freddie-flame.co.uk/image/');
define('HTTP_ADMIN', 'https://www.freddie-flame.co.uk/admin/');

So far it seems to have worked, though I'd like to know where the original error came from