And old SSL problem with a new spin?

FixItPete · December 25, 2004

Ok I've read this: http://www.oscommerce.com/forums/index.php?showtopic=48574 MANY TIMES and I have the same problem posted here... a ssl dir that is /usr/wwws/users/username and a non ssl dir that is /usr/www/users/username...

Here is my catalog config:

define('HTTP_SERVER', 'http://www.mydomain.com'); // eg, http://localhost - should not be empty for productive servers

define('HTTPS_SERVER', 'https://www.mydomain.com'); // eg, https://localhost - should not be empty for productive servers

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

define('HTTP_COOKIE_DOMAIN', 'www.mydomain.com');

define('HTTPS_COOKIE_DOMAIN', 'www.mydomain.com');

define('HTTP_COOKIE_PATH', '/catalog/');

define('HTTPS_COOKIE_PATH', 'https://www.mydomain.com');

define('DIR_WS_HTTP_CATALOG', '/catalog/');

define('DIR_WS_HTTPS_CATALOG', '/');

define('DIR_WS_IMAGES', 'images/');

define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/');

define('DIR_WS_INCLUDES', 'includes/');

define('DIR_WS_BOXES', DIR_WS_INCLUDES . 'boxes/');

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', 'pub/');

define('DIR_FS_CATALOG', '/usr/www/users/useraccount/catalog/');

define('DIR_FS_DOWNLOAD', DIR_FS_CATALOG . 'download/');

define('DIR_FS_DOWNLOAD_PUBLIC', DIR_FS_CATALOG . 'pub/');

Here is my admind config:

define('HTTP_SERVER', 'http://www.mydomain.com'); // eg, http://localhost - should not be empty for productive servers

define('HTTP_CATALOG_SERVER', 'http://www.mydomain.com');

define('HTTPS_CATALOG_SERVER', 'https://www.mydomain.com');

define('ENABLE_SSL_CATALOG', 'true'); // secure webserver for catalog module

define('DIR_FS_DOCUMENT_ROOT', '/usr/www/users/useraccount/catalog/'); // where the pages are located on the server

define('DIR_WS_ADMIN', '/catalog/admin/'); // absolute path required

define('DIR_FS_ADMIN', '/usr/www/users/useraccount/catalog/admin/'); // absolute pate required

define('DIR_WS_CATALOG', '/catalog/'); // absolute path required

define('DIR_FS_CATALOG', '/usr/www/users/useraccount/catalog/'); // absolute path required

define('DIR_WS_IMAGES', 'images/');

define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/');

define('DIR_WS_CATALOG_IMAGES', DIR_WS_CATALOG . 'images/');

define('DIR_WS_INCLUDES', 'includes/');

define('DIR_WS_BOXES', DIR_WS_INCLUDES . 'boxes/');

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_CATALOG_LANGUAGES', DIR_WS_CATALOG . 'includes/languages/');

define('DIR_FS_CATALOG_LANGUAGES', DIR_FS_CATALOG . 'includes/languages/');

define('DIR_FS_CATALOG_IMAGES', DIR_FS_CATALOG . 'images/');

define('DIR_FS_CATALOG_MODULES', DIR_FS_CATALOG . 'includes/modules/');

define('DIR_FS_BACKUP', DIR_FS_ADMIN . 'backups/');

Obviously I have something wrong, I think I have read the "Vger" post and done as indicated, but if I am wrong (and I may be!), could you please let me know?

This is driving me crazy!

Thank you to all!

Pete

FixItPete · December 25, 2004

Edit:

This is NOT a shared SSL.

Edit 2:

When I go to https://www.mydomain.com/checkout_shipping.php I get a page not found error. When I go to: https://www.mydomain.com I see a directory with cgi-bin in it.

Thanks again.

boxtel · December 25, 2004

Ok I've read this: http://www.oscommerce.com/forums/index.php?showtopic=48574 MANY TIMES and I have the same problem posted here... a ssl dir that is /usr/wwws/users/username and a non ssl dir that is /usr/www/users/username...

Here is my catalog config:

define('HTTP_SERVER', 'http://www.mydomain.com'); // eg, http://localhost - should not be empty for productive servers

define('HTTPS_SERVER', 'https://www.mydomain.com'); // eg, https://localhost - should not be empty for productive servers

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

define('HTTP_COOKIE_DOMAIN', 'www.mydomain.com');

define('HTTPS_COOKIE_DOMAIN', 'www.mydomain.com');

define('HTTP_COOKIE_PATH', '/catalog/');

define('HTTPS_COOKIE_PATH', 'https://www.mydomain.com');

define('DIR_WS_HTTP_CATALOG', '/catalog/');

define('DIR_WS_HTTPS_CATALOG', '/');

define('DIR_WS_IMAGES', 'images/');

define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/');

define('DIR_WS_INCLUDES', 'includes/');

define('DIR_WS_BOXES', DIR_WS_INCLUDES . 'boxes/');

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', 'pub/');

define('DIR_FS_CATALOG', '/usr/www/users/useraccount/catalog/');

define('DIR_FS_DOWNLOAD', DIR_FS_CATALOG . 'download/');

define('DIR_FS_DOWNLOAD_PUBLIC', DIR_FS_CATALOG . 'pub/');

Here is my admind config:

define('HTTP_SERVER', 'http://www.mydomain.com'); // eg, http://localhost - should not be empty for productive servers

define('HTTP_CATALOG_SERVER', 'http://www.mydomain.com');

define('HTTPS_CATALOG_SERVER', 'https://www.mydomain.com');

define('ENABLE_SSL_CATALOG', 'true'); // secure webserver for catalog module

define('DIR_FS_DOCUMENT_ROOT', '/usr/www/users/useraccount/catalog/'); // where the pages are located on the server

define('DIR_WS_ADMIN', '/catalog/admin/'); // absolute path required

define('DIR_FS_ADMIN', '/usr/www/users/useraccount/catalog/admin/'); // absolute pate required

define('DIR_WS_CATALOG', '/catalog/'); // absolute path required

define('DIR_FS_CATALOG', '/usr/www/users/useraccount/catalog/'); // absolute path required

define('DIR_WS_IMAGES', 'images/');

define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/');

define('DIR_WS_CATALOG_IMAGES', DIR_WS_CATALOG . 'images/');

define('DIR_WS_INCLUDES', 'includes/');

define('DIR_WS_BOXES', DIR_WS_INCLUDES . 'boxes/');

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_CATALOG_LANGUAGES', DIR_WS_CATALOG . 'includes/languages/');

define('DIR_FS_CATALOG_LANGUAGES', DIR_FS_CATALOG . 'includes/languages/');

define('DIR_FS_CATALOG_IMAGES', DIR_FS_CATALOG . 'images/');

define('DIR_FS_CATALOG_MODULES', DIR_FS_CATALOG . 'includes/modules/');

define('DIR_FS_BACKUP', DIR_FS_ADMIN . 'backups/');

Obviously I have something wrong, I think I have read the "Vger" post and done as indicated, but if I am wrong (and I may be!), could you please let me know?

This is driving me crazy!

Thank you to all!

Pete

<{POST_SNAPBACK}>

set your cookie paths to /

FixItPete · December 25, 2004

set your cookie paths to /

<{POST_SNAPBACK}>

So, just make:

define('HTTP_COOKIE_PATH', '/catalog/');

define('HTTPS_COOKIE_PATH', 'https://www.mydomain.com');

to

define('HTTP_COOKIE_PATH', '/');

define('HTTPS_COOKIE_PATH', '/');

Is that correct?

Just those two lines?

I just want to make sure I do the exact right thing.

Thanks,

Pete

FixItPete · December 25, 2004

FYI:

I did what was indicated in the reply above and:

So, just make:

define('HTTP_COOKIE_PATH', '/catalog/');

define('HTTPS_COOKIE_PATH', 'https://www.mydomain.com');

to

define('HTTP_COOKIE_PATH', '/');

define('HTTPS_COOKIE_PATH', '/');

And that does *not* fix the problem.

:(

Pete

P.S. I have changed it back to:

define('HTTP_COOKIE_PATH', '/catalog/');

define('HTTPS_COOKIE_PATH', 'https://www.mydomain.com');

pending the *right* way to do it.

Thanks again,

Pete

stevel · December 25, 2004

Those changes are correct, but won't help the problem you are having. You also need to make this change:

define('DIR_WS_HTTPS_CATALOG', '/catalog/');

FixItPete · December 25, 2004

Those changes are correct, but won't help the problem you are having. You also need to make this change:

define('DIR_WS_HTTPS_CATALOG', '/catalog/');

<{POST_SNAPBACK}>

Hi Steve,

I changed:

define('DIR_WS_HTTPS_CATALOG', '/');

to:

define('DIR_WS_HTTPS_CATALOG', '/catalog/');

I also did the changes that were suggested above...

It still doesn't work... UGH!

Pete

stevel · December 25, 2004

Does your host make you put SSL content in a separate location on the server?

FixItPete · December 25, 2004

Does your host make you put SSL content in a separate location on the server?

<{POST_SNAPBACK}>

I think so, the host is pair.com and...

ssl dir that is /usr/wwws/users/username

Which I can see when I go to https://www.mydomain.com (this is where I see the cgi-bin)

and a non ssl dir that is /usr/www/users/username

I am aware of a way where you use ~ to make things work but

a) I read that this is not the way it should be

B) I don't know/understand how to do it.

Thanks for the help Steve, I really do appreciate it!

Pete

stevel · December 25, 2004

Then you have to upload a copy of the site files to the wwws folder.

FixItPete · December 25, 2004

Then you have to upload a copy of the site files to the wwws folder.

<{POST_SNAPBACK}>

Hmmm... based on everything I have read from Vger and others I was told to NEVER put anything in that dir.

Steve, do you know any other options?

I just don't get it!

UGH!

Pete

stevel · December 25, 2004

Pete,

What I meant by the wwws folder was the version of the site folder that the host tells you is to be used for SSL content. If your host does use a separate folder for that, then you have no choice - you MUST upload a copy of your site to that folder if you want to use SSL.

FixItPete · December 25, 2004

Pete,

What I meant by the wwws folder was the version of the site folder that the host tells you is to be used for SSL content. If your host does use a separate folder for that, then you have no choice - you MUST upload a copy of your site to that folder if you want to use SSL.

<{POST_SNAPBACK}>

So you're saying in addition to the installation that I already have I have to put files in the wwws directory?

Is there a thread or something on which ones need to go where?

Thanks again!

Pete

stevel · December 25, 2004

My advice is to upload all the site files. If you try to pick and choose, you're likely to miss something.

Please consult your host's documentation on how you should upload files to be accessed by SSL. Based on what you said earlier, it would be in the form /usr/wwws/users/username

FixItPete · December 26, 2004

See... this: http://www.oscommerce.com/forums/index.php?showtopic=127233&hl=

is why I think you're not suppose to load the whole thing twice...

NEW INFO:

I just heard from pair.com and they are going to do this:

""we can point SSL to your /usr/www/users/username

directory so that OsCommerce configuration is more pleasant for you""

(instead of: we can point SSL to your /usr/swww/users/username)

Ya think that'll help matters?

UGH!

Vger... Vger... I'll bet you're just sitting back laughing at me. ;)

December 26, 2004

NEW INFO:

I just heard from pair.com and they are going to do this:

""we can point SSL to your /usr/www/users/username

directory so that OsCommerce configuration is more pleasant for you""

(instead of: we can point SSL to your /usr/swww/users/username)

Ya think that'll help matters?

<{POST_SNAPBACK}>

This will make it simpler for you and is the way things should be. Sometimes uploading the files to a separate directory is required, but then you must duplicate everything, yet some of the configuration parameters must point to that directory (file system) - a pain.

Once Pair have reconfigured your SSL you will only need to set the HTTPS settings.

Matti

FixItPete · December 26, 2004

This will make it simpler for you and is the way things should be. Sometimes uploading the files to a separate directory is required, but then you must duplicate everything, yet some of the configuration parameters must point to that directory (file system) - a pain.

Once Pair have reconfigured your SSL you will only need to set the HTTPS settings.

Matti

<{POST_SNAPBACK}>

Hi Matt,

"the way things should be" -- you have no idea how much I wanted to hear that! :)

Now... Pair did their thing and made the aforementioned change. Only still won't work, except it is probably the HTTPS settings you're talking about... what should I be looking at? I'll assume changes to my configs? (admin and catalog?)

Thank you! :)

Pete

December 26, 2004

define('HTTP_SERVER', 'http://www.mydomain.com'); // eg, http://localhost - should not be empty for productive servers
define('HTTPS_SERVER', 'https://www.mydomain.com'); // eg, https://localhost - should not be empty for productive servers
define('ENABLE_SSL', true); // secure webserver for checkout procedure?
define('HTTP_COOKIE_DOMAIN', 'www.mydomain.com');
define('HTTPS_COOKIE_DOMAIN', 'www.mydomain.com');
define('HTTP_COOKIE_PATH', '/catalog/');
define('HTTPS_COOKIE_PATH', '/catalog/');
define('DIR_WS_HTTP_CATALOG', '/catalog/');
define('DIR_WS_HTTPS_CATALOG', '/catalog/');

If you have session (login) problems remove the 'www.' from the cookie settings.

Matti

stevel · December 26, 2004

Yes, it definitely should be that there is no need to upload files twice. My host doesn't require this. I am pleased to see that yours is seeing the light.

I certainly agree that uploading two copies of the files is something to be avoided if possible, but until your host made it unnecessary, you had little choice.

FixItPete · December 27, 2004

Just to update anyone that may need this post down the road.

It looks like right now the /catalog dir had to be copied to the wwws folder. Which begs me to ask, then why do the thing where the wwws (where the SSL cert is) dir points to the www dir (the dir where the catalog dir is) I've got an email into pair.com to find out about this -- and I'll keep updating here.

I'd *really* like to thank Vger for all the help!

Until next update...

Pete

stevel · December 27, 2004

So you ended up doing what I suggested after all? :D

♥Vger · December 27, 2004

I'd *really* like to thank Vger for all the help!

You're welcome. Glad I could help.

Vger

FixItPete · December 27, 2004

Well I'm going around and around with pair.com -- it worked great, then they "fixed" something, which made it not work. Now I'm trying to get them to get it to work again, and I get this:

"However, we can not provide much more support than that for OSCommerce. We

have verified that the set up on the server is correct. I would urge you to check out the pair Newsgroups for assistance, or to check in the help

documentation for OSCommerce."

Riiiiight! Have you tried to use the Newsgroup there? LOL. Which one? Most of it is people wishing other people Happy Birthday from 1998. Come on, give me a break. If you advertise on osCommerce, shouldn't you bend over backwards to get it running on your server? Maybe I'm old-school like that, but if I'm paying for premium hosting, shouldnt' I get something?

How about this one:

I call tech support and told them that I was being denied access to the configure.php file (after they "fixed" something else, the previous time)! -- they fixed it, but then told me that by them "fixing" it, it may have canceled what the other support person was doing to get osCommerce Admin to work. I mean come on now! All this for almost $30 a month?

I'm willing to keep at it with them and I'll keep you all in the loop. If in the end it works, that's great. I understand that once they are up and running things with them can be pretty good.

UPDATE:

They won't help. I'll try for a couple more hours, if I can't get them to work, I'll toss them and make sure others know what happen.

I'll keep you updated.

Pete

stevel · December 27, 2004

What exactly is the problem you are seeing at present?

FixItPete · December 27, 2004

Ok, another update:

Turns out my ORIGNAL admin config (the one that was at the top of this thread) worked when I copy/pasted it.

So... some things you can learn from this post.

a) pair.com seems good at keeping their servers up and running (I only know from what I hear...)

B) they don't know the first thing about osCommerce and only ADVERTISE here to get customers, they DO NOT CARE ABOUT osCommerce. Only the MONEY the customers can bring them.

c) and this is the best one:

Read the last reply from support:

""Yes, I tried them, and https://www.mydomain.com/catalog/admin is

password protected, and

https://www.mydomain.comdir_ws_admincategories.php... isn't a valid

URL. Again, this not something we can support or assist with,

unfortunately.""

HAHAHAHAHAHAHAHAHA -- then why did the tech support say they fixed it in a previous reply? Really they fixed it? How do they know? Did they test it? NOW they are saying it is password protected (like they couldn't get the usr name and pw on their end, duh!)...

Oh well, let's see what happens from here.

Hey... one question... for anyone STILL reading this soap opera. How hard is it to move an osCommerce store after it is set up?

Thanks,

Pete

(!)

And old SSL problem with a new spin?

Recommended Posts

FixItPete

FixItPete

boxtel

FixItPete

FixItPete

stevel

FixItPete

stevel

FixItPete

stevel

FixItPete

stevel

FixItPete

stevel

FixItPete

Guest

FixItPete

Guest

stevel

FixItPete

stevel

♥Vger

FixItPete

stevel

FixItPete

Archived

Browse

Activity