Basics like how to use ssh, how to login to DA etc..How to setup /~username/domain.com
Basics like how to use ssh, how to login to DA etc..How to setup /~username/domain.com — If you wish to be able to control all domain on an account before they resolve, you can do so by creating some symbolic links.
Let us say you have domain1.com and domain2.com which you want to be able to access. You would run the following as the user through ssh:
cd /home/username
rm -f public_html
mkdir –mode=755 public_html
cd public_html
ln -s ../domains/domain1.com/public_html domain1.com
ln -s ../domains/domain2.com/public_html domain2.com
Alternatively, if you would just wish to switch which domain is being use for /~username, you can do it so by logging into the User Panel -> Domain Administration -> select the active domain to use and click “Set as Default”.
This will then setup the symbolic link for the selected domain for /~username.
How to add Frame Forwarding to your website
To add frame forwarding to your website, create your html file (usually index.html) with the following code:
<html><head><title>Title of your webpage</title></head>
<frameset cols=”*”>
<frame name=”main” src=”http://www.site-helper.com” scrolling=”auto” noresize>
<noframes>
<body>
Your browser does not support frames
</body>
</noframes>
</frameset>
</html>
Replace all bold items with the values you wish to use.
Why do I need an owned IP for my own SSL certificate?
The reason you must have your own dedicate IP address when you want to use your own SSL certificate (when you do not want the server wide sharing certificate) is because of the way SSL and Apache (httpd) works.
For name base web-hosting (when many domains are on one IP) the web browser will pass the name of the domain being requested inside the httpd headers along with the request.
This way, Apache knows which domain you are trying to access even though there are many domains on that one IP address.
When you want to do the same thing through an SSL connection, the connection has to be making *before* the request can be send.
In this connection, the certificate is passing. The only information that Apache knows before the request is making is which IP the connection is being make to.
It has to be able to know which certificate to send before the request is making, thus you can not use multiple certificates on the same IP (if you do, Apache will use the first certificate listing which DA will always set to the server shares certificate for shared IPs).
If there you want to use your own certificate, it then must be the first certificate listing. This would not work for a sharing IP, because there would multiple domain wanting this status, and the first certificate would the be one showing.
For this reason the sharing certificate is always using on a sharing IP.
For your certificate, DA will acknowledge the IP as being ‘own’ and will remove the server sharing certificate as the first cert to be load, thus your certificate will now be loading instead.
There is a new feature calling SNI developing with Apache and OpenSSL, however, this requires recent version of OpenSSL and that client browsers also supporting it.
