nobaloney
NoBaloney Internet Svcs - In Memoriam †
Using Shared Secure Certificates with DirectAdmin Mini How-To
Jeff Lasman, [email protected] 07/05/04 15:45
======================================
To prevent users from creating links in their websites to host files, images, etc., without having their bandwidth measured, Direct admin doesn't allow http access to user accounts through requests to, for example:
http://www.example.com/~username.
However, there is a serious side-effect.
Those hosting companies who've allowed the use of shared certificate secure site hosting this way:
https://www.hostingcompany.com/~domainusername
will find they no longer work.
The following procedure will enable these hosting companies to continue to offer shared certificate secure site hosting:
1) First the system administrator or reseller must create a site to be used as the shared site. In the case of a systems administrator, this should be done following the instructions in the "System Shared Certificates Mini How-To". In the case of a reseller, the reseller should create a site in his reseller account user administration panel, and protect it with a secure certificate. Either way, for the purposes of this Mini How-To, we'll call the site so created "secure.example.com".
2) If the reseller is to create the secure site's directory structure and maintain it him/herself, s/he will need shell access. If the system administrator doesn't give the reseller shell access than s/he will have to create and maintain the actual directory structure for him/her.
3) Logged in through a shell, the admin/reseller must first navigate to:
/home/admin[or reseller username]/domains/secure.example.com/private_html
4) Then the admin/reseller should create a link as follows:
USERNAME -> /home/USERNAME/domains/CUSTOMER.COM/private_html
Here's how:
ln -s /home/USERNAME/domains/CUSTOMER.COM/private_html USERNAME
where USERNAME must be replaced by the customer's username (in lower-case letters) and CUSTOMER.COM must be replaced by the customer's domain name (in lower-case letters) as originally created in the reseller control panel for the customer's domain.
5) Then the customer should log in (ftp access is fine) and then change to the domains/CUSTOMER.COM directory, and create a private_html directory if there isn't one already there.
Files uploaded into this private_html directory can be reached through the secure site:
https://secure.example.com/USERNAME/
Jeff Lasman, [email protected] 07/05/04 15:45
======================================
To prevent users from creating links in their websites to host files, images, etc., without having their bandwidth measured, Direct admin doesn't allow http access to user accounts through requests to, for example:
http://www.example.com/~username.
However, there is a serious side-effect.
Those hosting companies who've allowed the use of shared certificate secure site hosting this way:
https://www.hostingcompany.com/~domainusername
will find they no longer work.
The following procedure will enable these hosting companies to continue to offer shared certificate secure site hosting:
1) First the system administrator or reseller must create a site to be used as the shared site. In the case of a systems administrator, this should be done following the instructions in the "System Shared Certificates Mini How-To". In the case of a reseller, the reseller should create a site in his reseller account user administration panel, and protect it with a secure certificate. Either way, for the purposes of this Mini How-To, we'll call the site so created "secure.example.com".
2) If the reseller is to create the secure site's directory structure and maintain it him/herself, s/he will need shell access. If the system administrator doesn't give the reseller shell access than s/he will have to create and maintain the actual directory structure for him/her.
3) Logged in through a shell, the admin/reseller must first navigate to:
/home/admin[or reseller username]/domains/secure.example.com/private_html
4) Then the admin/reseller should create a link as follows:
USERNAME -> /home/USERNAME/domains/CUSTOMER.COM/private_html
Here's how:
ln -s /home/USERNAME/domains/CUSTOMER.COM/private_html USERNAME
where USERNAME must be replaced by the customer's username (in lower-case letters) and CUSTOMER.COM must be replaced by the customer's domain name (in lower-case letters) as originally created in the reseller control panel for the customer's domain.
5) Then the customer should log in (ftp access is fine) and then change to the domains/CUSTOMER.COM directory, and create a private_html directory if there isn't one already there.
Files uploaded into this private_html directory can be reached through the secure site:
https://secure.example.com/USERNAME/