Auth File

[Mario]

Hey,
We just moved our store from one server to another. This is the first time we have owned the license to Shopsite (before we were using our hosts version on a shared server). For some reason, when our auth file was generated, it used our IP as the Store URL. So when we log into the backend we get the following error message:


____________________________________________________________________________________
Warning!
The domain name contained in your auth file does not match the domain name of this server.
Expected domain name: http://our.ip/shopping
instead got domain name: www.ourdomain.com
Your Store will still function correctly with this version of ShopSite. However, to ensure future compatibility either obtain a new auth file from your reseller or run ShopSite from http://our.ip/shopping

_________________________________________________________________________________

It actually is causing problems for us though. Netscape users get a "Unexpected Certificate Name" error message when moving from our shipping screen to the checkout screen. I believe that shopsite is somehow using the IP address in this process to place the order. Our security cert is only for our domain and not our IP and this is what poses a problem.

I would like some advice. If we change the auth file, should this correct this problem? Also is using the instructions in Shopsite Knowledgebase Solution S03192 the only way to change the auth file? We are up and running our store and have made all of our adjustments in the backend. We have custom templates running and have tweaked just about every aspect of the backend.

O yes, we are running Shopsite SC 5.0.0.0.1 (with the patches applied) on a Cobalt RaQ3 with Linux.

Help will be appreciated.

Thanks as always,

Mario

P.S. NEW SHOPSITE TEAM: Good Luck and keep up the good work!

[loren_d_c]

Mario,

this shouldn't be affecting your shopping cart. The shopping cart URL's
are based off of the settings under Preferences -> Hosting Service, the
Shopping Cart secure URL and the Shopping Cart CGI's URL. These,
especially the secure URL, need to be correct. If the Shopping Cart
secure URL domain does not match the domain in the secure certificate
being used on the secure webserver, then a browser warning will be
displayed to all shoppers when they go to checkout.

-Loren

Mario wrote:

Hey,
We just moved our store from one server to another. This is the
first time we have owned the license to Shopsite (before we were using
our hosts version on a shared server). For some reason, when our auth
file was generated, it used our IP as the Store URL. So when we log
into the backend we get the following error message:


____________________________________________________________________________________

Warning!

The domain name contained in your auth file does not match the domain
name of this server.

Expected domain name: http://our.ip/shopping
instead got domain name: www.ourdomain.com

Your Store will still function correctly with this version of
ShopSite. However, to ensure future compatibility either obtain a new
auth file from your reseller or run ShopSite from
http://our.ip/shopping

_________________________________________________________________________________

It actually is causing problems for us though. Netscape users get a
"Unexpected Certificate Name" error message when moving from our
shipping screen to the checkout screen. I believe that shopsite is
somehow using the IP address in this process to place the order. Our
security cert is only for our domain and not our IP and this is what
poses a problem.

I would like some advice. If we change the auth file, should this
correct this problem? Also is using the instructions in Shopsite
Knowledgebase Solution S03192 the only way to change the auth file? We
are up and running our store and have made all of our adjustments in
the backend. We have custom templates running and have tweaked just
about every aspect of the backend.

O yes, we are running Shopsite SC 5.0.0.0.1 (with the patches applied)
on a Cobalt RaQ3 with Linux.

Help will be appreciated.

Thanks as always,

Mario

P.S. NEW SHOPSITE TEAM: Good Luck and keep up the good work!

[Mario]

But the error isn't coming up to all shoppers. Only those using Netscape.
The URL's under Preferences -> Hosting service are correct except for the
one that says Store URL, which uses our IP address instead of our domain.

Should the new auth file be generated? What exactly will it entail after my
host gets if for us? Will it correct the unchangeable field "Store URL" in
the backend? Why else could Netscape users be getting this error?

Thanks Loren,
You are always a great help.

Mario


"Loren" <loren_d_c@yahoo.com> wrote in message
news:3B8C4B7B.D0E3339B@yahoo.com...

Mario,

this shouldn't be affecting your shopping cart. The shopping cart URL's
are based off of the settings under Preferences -> Hosting Service, the
Shopping Cart secure URL and the Shopping Cart CGI's URL. These,
especially the secure URL, need to be correct. If the Shopping Cart
secure URL domain does not match the domain in the secure certificate
being used on the secure webserver, then a browser warning will be
displayed to all shoppers when they go to checkout.

-Loren


Mario wrote:

Hey,
We just moved our store from one server to another. This is the
first time we have owned the license to Shopsite (before we were using
our hosts version on a shared server). For some reason, when our auth
file was generated, it used our IP as the Store URL. So when we log
into the backend we get the following error message:



____________________________________________________________________________

________

Warning!

The domain name contained in your auth file does not match the domain
name of this server.

Expected domain name: http://our.ip/shopping
instead got domain name: www.ourdomain.com

Your Store will still function correctly with this version of
ShopSite. However, to ensure future compatibility either obtain a new
auth file from your reseller or run ShopSite from
http://our.ip/shopping


____________________________________________________________________________

_____

It actually is causing problems for us though. Netscape users get a
"Unexpected Certificate Name" error message when moving from our
shipping screen to the checkout screen. I believe that shopsite is
somehow using the IP address in this process to place the order. Our
security cert is only for our domain and not our IP and this is what
poses a problem.

I would like some advice. If we change the auth file, should this
correct this problem? Also is using the instructions in Shopsite
Knowledgebase Solution S03192 the only way to change the auth file? We
are up and running our store and have made all of our adjustments in
the backend. We have custom templates running and have tweaked just
about every aspect of the backend.

O yes, we are running Shopsite SC 5.0.0.0.1 (with the patches applied)
on a Cobalt RaQ3 with Linux.

Help will be appreciated.

Thanks as always,

Mario

P.S. NEW SHOPSITE TEAM: Good Luck and keep up the good work!