Where is my padlock

[matti]

Please help guys/dolls

I have a dedicated secure server.....when i go to the log in page, or create account...my page does change to https:// my webby....But i dont have the padlock at the bottom of the page to indecate its secure....I really need to sort this 1 out.....anyone knows where i maybe going wrong.

Cheers

Matti :(

[voxmaris]

That is too funny. I just asked this question on the same forum not 5 minutes ago. No response yet.

 

Is it that you can view other folders in your webroot and the lock appears but in the osCommerce root, the lock disappears?

 

That's what is happening to me.

[matti]

That is too funny. I just asked this question on the same forum not 5 minutes ago. No response yet.

 

Is it that you can view other folders in your webroot and the lock appears but in the osCommerce root, the lock disappears?

 

That's what is happening to me.

 

lol yea you got it M8....Hopefully not to many people are laughing at us.....But looking at your post, your a noob like me.......Give us a break all you master coders......we are users....We leave all the hard bit to you brainy sods....Just wish i knew or could take in just an pinch of what ppl put on this forum,,,,Put 2 of us out of our misery will ya

Matt

[jhsands]

Search the forums for SSL and you will find thousands of posts asking about this question.

 

[1] Do you have external banners?

[2] is configure.php HTTP_SERVER set to https://...

[3] is configure.php SSL_ENABLED set to true ?

[jasonabc]

my page does change to https:// my webby....But i dont have the padlock at the bottom of the page to indecate its secure

When this has happened in my experience the SSL is usually not correctly installed.

[Jack_mcs]

Please help guys/dolls

I have a dedicated secure server.....when i go to the log in page, or create account...my page does change to https:// my webby....But i dont have the padlock at the bottom of the page to indecate its secure....I really need to sort this 1 out.....anyone knows where i maybe going wrong.

Cheers

Matti :(

It sounds like you didn't enable ssl in your configure file. If you can go to https://www.yoursite.com and it displays with the lock, then your ssl is OK. That means the configure file is not setup.

 

Jack

[mtechama]

It sounds like you didn't enable ssl in your configure file. If you can go to https://www.yoursite.com and it displays with the lock, then your ssl is OK. That means the configure file is not setup.

 

Jack

 

 

What are the settings should be to set up SSL?

[jhsands]

What are the settings should be to set up SSL?

 

See my previous post in this column... items 2 & 3.

[mtechama]

Search the forums for SSL and you will find thousands of posts asking about this question.

 

[1] Do you have external banners?

[2] is configure.php HTTP_SERVER set to https://...

[3] is configure.php SSL_ENABLED set to true ?

 

 

[2] is should be https://www.yourdomain.com or what

 

I know number 3 is

 

and here is my configure.php

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

[Jack_mcs]

It should be

define('HTTP_SERVER', 'http://www.mtechama.com'); // eg, http://localhost - should not be empty for productive servers
 define('HTTPS_SERVER', 'http://www.mtechama.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.mtechama.com');
 define('HTTPS_COOKIE_DOMAIN', 'www.mtechama.com');
 define('HTTP_COOKIE_PATH', '/');
 define('HTTPS_COOKIE_PATH', '/');
 define('DIR_WS_HTTP_CATALOG', '/');
 define('DIR_WS_HTTPS_CATALOG', '/');

 

Jack

[mtechama]

It should be

define('HTTP_SERVER', 'http://www.mtechama.com'); // eg, http://localhost - should not be empty for productive servers
 define('HTTPS_SERVER', 'http://www.mtechama.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.mtechama.com');
 define('HTTPS_COOKIE_DOMAIN', 'www.mtechama.com');
 define('HTTP_COOKIE_PATH', '/');
 define('HTTPS_COOKIE_PATH', '/');
 define('DIR_WS_HTTP_CATALOG', '/');
 define('DIR_WS_HTTPS_CATALOG', '/');

 

Jack

 

does it purpose to show a pad lock when they create an account?

[Jack_mcs]

Yes, you should see one.

 

Jack

[mtechama]

Yes, you should see one.

 

Jack

 

 

well it didn't work. its still shows http://www.yourdomain.com/create_account.php and no pad lock.

[jpweber]

You missed an "S". Also, if it's a very cheap SSL, some cheap SSL's don't show the padlock. Don't forget the https:// when you define the HTTPS_Server. Anyway,

 

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

define('HTTPS_SERVER', 'httpS://www.mtechama.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.mtechama.com');

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

define('HTTP_COOKIE_PATH', '/');

define('HTTPS_COOKIE_PATH', '/');

define('DIR_WS_HTTP_CATALOG', '/');

define('DIR_WS_HTTPS_CATALOG', '/');

 

J

[mtechama]

You missed an "S". Also, if it's a very cheap SSL, some cheap SSL's don't show the padlock. Don't forget the https:// when you define the HTTPS_Server. Anyway,

J

 

 

I have tried that but it still didn't work if you got to http://www.mtechama.com and click on create an account you will find out

[jpweber]

Are you sure you have SSL installed? I can't get any https:// site to work. Are you with a host? You need to get the CSR code from them, then go to the SSL company, buy the SSL, have them give you the key, then give the key back to the host and let them install it. Are you sure you have SSL installed?

 

J

[jasonabc]

the cookie domain must have the www. part removed:

 

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

 

But this is trivial stuff. Your SSL is not set up or configured. Get your host to do this for you or use their free (shared) one.

[MEDIAZONE]

Are you sure you have SSL installed? I can't get any https:// site to work. Are you with a host? You need to get the CSR code from them, then go to the SSL company, buy the SSL, have them give you the key, then give the key back to the host and let them install it. Are you sure you have SSL installed?

 

J

 

fyi - I see a padlock on your site

[jpweber]

I dont' see a padlock. In fact, I can't get any https:// page to load on his website. Are you sure your configure file is configured correctly -- assuming you have SSL installed properly?

[mtechama]

I just purchase Certificate SSL with my Hosting and it install on my server and still not working here is my settings to my configure.php

 

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

[jpweber]

I just purchase Certificate SSL with my Hosting and it install on my server and still not working here is my settings to my configure.php

 

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

 

You look good now. Padlock is there, secured by Valicert. You have nonsecure content on your website, and to get rid of that message "would you like to display the nonsecure items", you have to take out the http:// links in your coding.

 

So forget the <base href="http://www.mtechama.com/">. Just delete it.

Forget the <a href="http://www.mtechama.com/index.php"> ... just make it <a href="../index.php">

Forget the <a href="https://www.mtechama.com/checkout_shipping.php" class="headerNavigation"> ... just make it <a href="checkout_shipping.php">, and so on and so on.

 

Do that for all your http:// links. Make 'em without the http://. Other than that, you seem good to go.

 

J

[mtechama]

You look good now. Padlock is there, secured by Valicert. You have nonsecure content on your website, and to get rid of that message "would you like to display the nonsecure items", you have to take out the http:// links in your coding.

 

So forget the <base href="http://www.mtechama.com/">. Just delete it.

Forget the <a href="http://www.mtechama.com/index.php"> ... just make it <a href="../index.php">

Forget the <a href="https://www.mtechama.com/checkout_shipping.php" class="headerNavigation"> ... just make it <a href="checkout_shipping.php">, and so on and so on.

 

Do that for all your http:// links. Make 'em without the http://. Other than that, you seem good to go.

 

J

 

What coding are you talking about?

[jpweber]

In create_account.php .... and login.php

 

You have all hard links ... like <a href="http://www.metchama.com/login.php">, just put <a href="login.php"> ... get rid of the http:// on all your links. That way, you won't get that message, "would you like to display nonsecure items", etc. ...

 

Your site works good in my Mozilla, but in Internet Explorer, it's a little messed up. Nevertheless, your SSL seems to be working properly now.

 

J

[mtechama]

In create_account.php .... and login.php

 

You have all hard links ... like <a href="http://www.metchama.com/login.php">, just put <a href="login.php"> ... get rid of the http:// on all your links. That way, you won't get that message, "would you like to display nonsecure items", etc. ...

 

Your site works good in my Mozilla, but in Internet Explorer, it's a little messed up. Nevertheless, your SSL seems to be working properly now.

 

J

 

Ok where do I edit the links like like <a href="http://www.metchama.com/login.php">, just put <a href="login.php">?

[jpweber]

Ok where do I edit the links like like <a href="http://www.metchama.com/login.php">,'>http://www.metchama.com/login.php">, just put <a href="login.php">?

 

Do you have a PHP editor like Crimson Editor or PHP Designer 2006, Textpad, or whatever? If not, just use notepad. Go into where you keep your files on your hard drive, and open up login.php. Find the http;// links and change them around, so they don't include the http://. Do this for create_account.php also, which is located in your catalog folder (unless you renamed it). In other words, change <a href="http://www.metchama.com/login.php"> to simply <a href="login.php">, and do that for all the http:// based links. Save the files, and use your FTP tool to upload them to the proper directories on your server.

 

As an alternative, go to your ADMIN tool ... http://www.yoursite.com/catalog/admin, log in. Then click "languages", then "define". Then find your files, and edit them that way.

 

J