pair Networks - World Class Web Hosting - E-Commerce

E-Commerce - Using SSL

SSL

SSL (a.k.a. "secure server") access is available as an add-on to the Basic, Advanced, Webmaster, and High Volume Accounts, and is included with the Developer and Commerce accounts. This article answers common questions about the use of SSL on accounts here at pair Networks.

I have SSL access on my account. Where do I place my files that require secure access?

Once SSL is added to your account, a link named "public_ssl" will be added to your account's home directory. You can follow this link using SSH or FTP to your actual SSL directory (which will be /usr/wwws/users/username).

I have SSL access that was bundled with a Developer or Commerce account. Where do I place my files that require secure access?

With the bundled access included in these accounts, there is not a separate directory for secure server access. All files in your public_html directory may be accessed securely or through the regular web server by simply changing how you link to them.

This is so because our research has shown that most "shopping cart" packages work best when the same set of files can be accessed through regular access and secure access.

Hey! I have an SSL add-on, but I'd prefer that the SSL server pointed to my public_html files, like with the Developer Account!

No problem, just e-mail us at support@pair.com and we can simulate that behavior for you.

What is the URL of my secure files?

First, you need to know the name of the secure server you are on. This should be given in the welcome message you received with your account (for Developer Accounts), in your ShopSite welcome letter (for Commerce accounts), or in the upgrade confirmation (for added-on SSL access). If you are not sure, look up your server's name on the server details list -- the name of the secure server will be listed under the server's regular name. It will look similar to one of three basic forms: ssl.pair.com, shopsite.pair.com, or commerce.pair.com.

For all account types, you can access your secure files at this URL:

https://ssl#.pair.com/username/

Note the s after http in the protocol -- if it's not included, access will not be made securely. You should substitute in your username for username and the specific name of your SSL server, of course.

Do I need to get my own secure certificate?

Not unless you desire/require your SSL access to be done through your domain name (e.g. https://www.example.com/). There is no advantage from a security point-of-view in having your own certificate over using one of ours.

More details about secure certificates are available here.

Please provide feedback on this article.