Magento

And don’t forget the “S” in the https://

Hi there,

I’m having trouble getting my shared SSL to work with 1&1;.

After a long haul I FINALLY got version 1.0.19870 to install, but now i can’t get the secure parts working. I get this error:

“Firefox has detected that the server is redirecting the request for this address in a way that will never complete.”

the store works (http://www.lo-five.com/store) but the admin doesn’t. Where do i make the changes you suggest?

Thanks

Jim

Figured out a way to get the login on onepage working with shared ssl at 1and1.  Just change the last line of
loginPostAction() in /app/code/core/Mage/Customer/controllers/AccountController.php from

to

Hi,

I’m having problems with shared SSL. I have done exactly as you have described CGray but not sure I have the correct detail to replace the mysite.com part of your advice. Is it that we should have the original site detail or the URL for the shared SSL?

I have actually done both and it still sends me to the 404 Not found page.

Look forward to your quick response.

The /sitename.com is refering to the path name on the ssl proxy.

For Example assume that on 1and1 your full url for shared ssl would be along the lines of:

https://ssl.perfora.net/sitename.com

in this case you would use “/sitename.com” in the script.

The problem is after it logs you in it tries to do a redirect to /customer/account/?SID= instead of $secure_url/customer/account/?SID=
So what should be
https://ssl.performa.net/sitename.com/customer/account
becomes
https://ssl.performa.net/customer/account

Hope this explains it well enough.

Thanks CGray. I gave up in the end and bought a dedicated SSL certificate. That’s all working fine now for Paypal.

I’ve moved on to my next frustration - Can’t get Google Checkout to talk to Magento though. Always get an error from Googlecheckout:

“We encountered an error trying to access your server at https://www.mysite.co.uk/index.php/googlecheckout/api/; the error we got is: Send failed with code: 401. Response body was: Failed to Get Basic Authentication Headers”

I can get payment from Google, but it doesn’t appear in my admin or orders list. Anyone help?

Hi,

I have added some information to the bug ticket, I’ll paste it here for those who need to find a solution, not really a fix....

“We have the same problem here. I noticed one way to make it work : disable URL Rewrite in Configuration / Web - and now links to shared SSL server (like the customer login page) work fine.

Our alias for the shared SSL contains a ~ :

https://ssl.ourhost.com/~ourdomain/path

Could there be a problem with the rewriting system and the ~, causing it to land on a 404 when Rewrite is on and working fine when it is off ?

Hope you guys are on your way to figuring this out for good. Thank you so much!”

-----
David - Advertising and multimedia @ http://www.tzav.fr

As of magento 1.1.6 (stable) it is still necessary to patch:

app/code/core/Mage/Core/Model/Config.php
app/code/core/Mage/Core/Model/Store.php

with the code in the first post or else you get an infinite redirect when using shared ssl with X-header-redirect like 1&1;and DF are using.

I havent tested the Member Login, but this is a serious bug that should be patched by Varien Please.

Thanks

Regards,
tronics

I have ver 1.6 with 1and1 ssl share and it works for me. But I get this problem:

I have 2 store views. One english and one spanish....

The problem is when it redirects to ssl server, only accepts the spanish language because it is the default store view.

Any ideas?

http://www.publicidadporcelana.es

I am trying to use the secure ssl certificate, when i go to my website at https://mydomain.com/magento/ it shows as secure with Warnings Contains unauthenticated content? All of the links and the pictures refer to my http://mydomain.com/magento

General - Web
Unsecure
Base Url

Use Secure URL in Frontend Yes

Deleted the cache.

In the technical details of the browser it also states that Connection Partially Encrypted, parts of the page you are viewing were not encrypted before being transmitted over the internet. Information sent over the Internet without encryption can be seen by other people while it is in transit.

Any help would be greatly appreciated. I have been searching the boards and trying new things for two days now.

Thank you.

UPDATE

Well after two days I think I got what I wanted. I am using my shared SSL certificate from Netfirms.

In Admin System Configeration Web

Unsecure

Base Url http://www.cornholesupplies.com/eStore/
Base Link URL ((secure_base_url))
Base Skin URL ((secure_base_url))skin/
Base Media URL ((secure_base_url))media/
Base JavaScript URL ((secure_base_url))js/

Secure

Base URL https://www.cornholesupplies.com/eStore/
Base Link URL https://www.cornholesupplies.com/eStore/
Base Skin URL ((secure_base_url))skin/
Base Media URL ((secure_base_url))media/
Base JavaScript URL ((secure_base_url))js/

Use secure URLs in Frontend Yes
Use Secure Urls in Admin No

I assume this forces magento to use the secure base url in the whole website. If you go to http://www.cornholesupplies.com/eStore it is not secure but all of the links and images are secure and by clicking anything in the site it will go to the SSL encrypted pages with no errors.

If anyone sees a problem with this please feel free to contact me as I am not a pro at this by far and don’t want to create any security issues. If there is some other way that this can be done please let me know as well. I have seen alot of threads about the SSL issues and nothing worked for me. Thank you for your time.

cannonballdex:

Question for you since this thread seems to be dead now anyways. The cornholesupplies.com website seems to be running quite fast for a Magento site. What sort of resources are behind it? Dedicated server? Dual Quad Xeon? 8GB or RAM? Just wondering of the specs?

tronics - 09 April 2008 07:51 AM

Hello for me this fix works with 1.0 !!

Almost everything works.
Except for the Login for existing customer on checkout…

When submitting your login credentials
https://sslsite.com/shop/checkout/onepage/
instead of
https://sslsite.com/domain.com/shop/checkout/onepage/
is called.
That is not working of course because the domain in this shared ssl environment is always
http://www.domain.com/ OR
http://sslsite.com/domain.com/

This might be a bug in magento..
Apart a fix for this shared ssl should go into the core.

Thanks

Regards,
rrrr4

Did anyone figure out how to resolve the bad links in the existing customer login form???

Do i need to follow the instructions here for 1.3.2.2.

The shop is set up fine, but the minutes I change to secured SSL for frontend, I get 4040 errors on my accounts, log in etc.

I have shared ssl setup.

The site works fine at: http://www.yumalum.com/

But clicking on my account links - look for this address: https://www2.securedweb.co.uk/mrx9yum/customer/account/?SID=441fc9e3c27028876f7d25884f4d1bcf, and provide the 404 message.

Can anyone help please.

BigWil - 05 March 2009 05:28 PM

cannonballdex:

Question for you since this thread seems to be dead now anyways. The cornholesupplies.com website seems to be running quite fast for a Magento site. What sort of resources are behind it? Dedicated server? Dual Quad Xeon? 8GB or RAM? Just wondering of the specs?

Sorry for the long delay in the message, I haven’t used these boards in sometime because my site is running perfectly. I am using a dedicated server with SimpleHelix, I am not sure about the specs but I am very satisfied with the service and the speed.

I have solved my problem and what follows may not be that clear, but I hope it helps anyone having similar problems:

The problem stems from having a Shared SSL certificate and the location of the physical install of Magento and the Rewritebase setting.

1. http server is http://www.mysite.com
2. https server is http://www2.securesite.com/mysecsitename
3. location of https server is mapped to root directory of web space

This does not work as the secure pages cannot be found when rewritebase is set to / as Magento is looking for the pages in /mysitename.

So, solution was:
1. Rewritebase /mysecsitename
2. In root directory, ln -s <root directory> mysecsitename

This in affect maps the sub-directory to the root directory, and all pages can be found.