Shared SSL Access
Important - Deprecated Feature
Due to GCom Internet's new feature of the free provision of Comodo SS/TLS DV Certificates to all hosted domains, the shared SSL function is now deprecated and scheduled for full termination after Friday, 30th September, 2016.
For more information, please refer to the knowledge base article Free https:// SSL/TLS.
Deprecated Details Follow
Gcom Internet provides shared SSL to its hosting clients at no additional cost above their standard hosting fee.
On each hosting server, a special purpose SSL certificate is installed on a generically named subdomain which forms an alias over the entire server.
By accessing your existing site structure under the SSL encryption offered by our shared certificate, you can provide full SSL to your own end users without the cost or complication of purchasing and installing your own certificate.
The first step in providing SSL access to your site is to determine which server you are hosted on, and therefore which shared SSL prefix you need to use in your URI references.
To determine which server is currently hosting your site or service, and which shared SSL prefix applies, you just need to log in to your cPanel and look at the server name listed in the side column.
Each server has a name of two syllables. The shared SSL prefix for each server is simply made up of the first letter of each syllable. As an example, the shared SSL prefix for the server "Tamworth" would be "tw".
Once you have the relevant shared SSL prefix, you can reference your site under the security of SSL by way of the following URI format...
...where "xx" is replaced with the previously obtained shared SSL prefix for your server, and...
...where "admin00" is replaced with the primary cPanel administrator login name for your site.
Remember to include the tilde "~" character before your cPanel administrator login name.
A trailing slash "/" is required at the end of the URI unless a specific file is referenced.
Because SSL performs encryption processes during data transfers, it adds a load to the CPU's of the server. Please only use SSL references within your site's coding where they are actually required. SSL should only be invoked during data acceptance or delivery where sensitive data actually requires encrypted protection.
Examples of valid shared SSL URI formats
https://sslxx.servers121.com/~admin00/ would direct to the default file (usually "index.html" or similar) in the "public_html" folder. A trailing slash "/" must be provided to terminate the URI since it points to a folder.
https://sslxx.servers121.com/~admin00/sales/ would direct to the default file (usually "index.html" or similar) in the "public_html/sales" folder. A trailing slash "/" must be provided to terminate the URI since it points to a folder.
https://sslxx.servers121.com/~admin00/sales/contact.html would direct to the specific file "contact.html" in the "sales" folder. The URI must not be terminated with a trailing slash "/" since it is referencing a specific file