1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Resellers

Discussion in 'Legacy Sitebuilder Software' started by gudzon, Jun 20, 2005.

  1. gudzon

    gudzon Guest

    0
     
    Hello,

    I'm learning SB 2.0 now and got stuck at Resellers. Cannot find any information on this in the instructions.

    I've created a reseller. His domain is, let's say, reseller.com. What URL for the sitebuilder his customers should use to start building the trial web site from scratch? Obviously, it cannot be the same address as mine - I have my customizations, he has his.

    So if my customer's SB is here: http://sitebuilder.mydomain.com/wizard/index.php, what should my reseller's customers use?

    I would appreciate your help.

    Thank you,

    Peter
     
  2. smilebb

    smilebb Guest

    0
     
    Sorry I cant help, but I also have the same question. Any replies much appreciated.
     
  3. Danil Fomichev

    Danil Fomichev Guest

    0
     
    Here is the ways for reseller to be identified:

    1. Register reseller.sitebuilder.mydomain.com domain, configure it in httpd as virtual host.

    2. Get resellers' domain name via GET/POST-query with reseller variable.
    For example:
    http://sitebuilder.mydomen.com/index.php?reseller=reseller.com

    let us assume that this is basic domain:
    sitebuilder.mydomain.com

    and resellers' domain with some IP as basic domain:
    reseller.com

    altough if anybody comes to reseller.com then Sitebuilder would determine it as sitebuilder.mydomen.com/?reseller=reseller.com

    I guess it would help ;)
     
  4. RogerW37

    RogerW37 Guest

    0
     
    Assuming sitebuilder.mysite.com and I add a reseller called "somehost.com" so I would have somehost.sitebuilder.mysite.com correct?

    So for every reseller you are saying I need to do two things.

    1. Edit the DNS zone file for mysite.com to include:
    somehost.sitebuilder.mysite.com 14400 A ##.##.###.##

    AND

    2.
    pico /usr/local/apache/conf/httpd.conf

    <VirtualHost ##.##.###.##:80>
    ServerAlias *somehost.sitebuilder.*
    DocumentRoot /usr/local/sitebuilder/htdocs
    BytesLog domlogs/sitebuilder.*-bytes_log
    ServerName *somehost.sitebuilder.*
    ErrorLog logs/sitebuilder-error_log
    CustomLog logs/sitebuilder-access_log common
    DirectoryIndex index.php
    AddDefaultCharset UTF-8

    <Directory /usr/local/sitebuilder/htdocs>
    AllowOverride All
    </Directory>

    <Directory /usr/local/sitebuilder/install>
    AllowOverride none
    </Directory>

    <Directory /usr/local/sitebuilder/htdocs/users>
    AllowOverride none
    </Directory>

    <Directory /usr/local/sitebuilder/htdocs/repository>
    AllowOverride none
    </Directory>

    <Directory /usr/local/sitebuilder/install.bkp>
    AllowOverride none
    Order deny,allow
    Deny from All
    </Directory>
    </VirtualHost>

    Is that correct? Do I need everything as noted above?

    Thank you,
    Roger
     
  5. RogerW37

    RogerW37 Guest

    0
     
    ADDING RESELLERS - "The Guide"

    ONE TIME CHANGES TO ACCOMODATE RESELLERS - BEGIN

    IMPORTANT NOTE: Please read the entire direction to the last item before attempting these procedures.

    In the event httpd.conf is overwritten or there is a move to a new server, the sitebuilder conf file is kept separate. This will also make it easier to update the conf file with new resellers and diagnose any errors.

    1. Remove all entries about sitebuilder from:
    /usr/local/apache/conf/httpd.conf

    2. Add one entry in httpd.conf for sitebuilder:
    Include /usr/local/apache/conf/sitebuilder.conf

    3. Create sitebuilder.conf in the folder as noted directly above. In this case it would be in /usr/local/apache/conf and called sitebuilder.conf

    4. Any sitebuilder entries you removed from httpd.conf, place them in the newly created sitebuilder.conf file.

    5. Restart apache
    httpd restart

    Test your sitebuilder as up to this point, we really have only made a simple change and your sitebuilder should still be in full working order.

    ONE TIME CHANGES TO ACCOMODATE RESELLERS - END

    Now a reseller comes along and you need to set them up. Here we go...

    The sitebuilder.conf file will contain all of your manually added resellers. That's why it's important to create a separate file to maintain all of this information.

    MANUALLY ADD RESELLER - STEP 1

    The beginning of the sitebuilder.conf file has my main configuration for my hosting site.

    #
    # SiteBuilder configuration file
    #

    ########################## BEGIN MAIN SITEBUILDER

    #NameVirtualHost sitebuilder

    <VirtualHost ##.##.##.##:80>
    Alias /admin/ /usr/local/sitebuilder/htdocs/admin/
    ServerAlias *sitebuilder.*
    DocumentRoot /usr/local/sitebuilder/htdocs
    ServerName *sitebuilder.*
    ErrorLog logs/sitebuilder-error_log
    CustomLog logs/sitebuilder-access_log common
    DirectoryIndex index.php
    AddDefaultCharset UTF-8
    <Directory /usr/local/sitebuilder/htdocs>
    AllowOverride All
    </Directory>

    php_admin_flag max_execution_time 0
    php_admin_value memory_limit 32M

    <Directory /usr/local/sitebuilder/htdocs/install>
    AllowOverride none
    </Directory>

    <Directory /usr/local/sitebuilder/htdocs/users>
    AllowOverride none
    </Directory>

    <Directory /usr/local/sitebuilder/htdocs/repository>
    AllowOverride none
    </Directory>

    <Directory /usr/local/sitebuilder/htdocs/install.bkp>
    AllowOverride none
    Order deny,allow
    Deny from All
    </Directory>


    </VirtualHost>

    ########################## END MAIN SITEBUILDER

    After it, I add resellers such as:

    ########################## BEGIN RESELLER SITEBUILDER
    <VirtualHost ##.##.##.##:80>
    Alias /admin/ /usr/local/sitebuilder/htdocs/admin
    ServerAlias *sitebuilder.yourreseller.com
    DocumentRoot /usr/local/sitebuilder/htdocs
    ServerName *sitebuilder.yourreseller.com
    ErrorLog logs/sitebuilder-error_log
    CustomLog logs/sitebuilder-access_log common
    DirectoryIndex index.php
    AddDefaultCharset UTF-8

    <Directory /usr/local/sitebuilder/htdocs>
    AllowOverride All
    </Directory>

    <Directory /usr/local/sitebuilder/install>
    AllowOverride none
    </Directory>

    <Directory /usr/local/sitebuilder/htdocs/users>
    AllowOverride none
    </Directory>

    <Directory /usr/local/sitebuilder/htdocs/repository>
    AllowOverride none
    </Directory>

    <Directory /usr/local/sitebuilder/install.bkp>
    AllowOverride none
    Order deny,allow
    Deny from All
    </Directory>
    </VirtualHost>

    ##################################

    For each new reseller, just copy and paste and change two lines (ServerAlias and ServerName).

    Restart apache so it will see the newly added reseller.

    MANUALLY ADD RESELLER - STEP 2

    Okay, so we've added the reseller to the sitebuilder.conf file. The next step is...

    Log in to WHM
    DNS Functions >> Edit DNS Zone >> Select the reseller's domain to modify and add the following two lines...

    sitebuilder.yourreseller.com. 14400 A ##.##.##.##
    *.sitebuilder.yourreseller.com. 14400 A ##.##.##.##
    The above bolded item was added on April 5, 2006. Without it, the temporary trail accounts won't work since it can't recognize trial accounts without it.

    MANUALLY ADD RESELLER - STEP 3

    Now you need to setup a reseller within sitebuilder itself.

    1. Login to sitebuilder admin
    http://sitebuilder.yourdomain.com/admin_login.php

    2. Resellers Management Icon

    3. Add Reseller Button

    4. IMPORTANT: The Domain will be sitebuilder.yourreseller.com (make sure to put sitebuilder. at the beginning or it won't work - trust me!)

    5. The rest of the information is setup like a normal sitebuilder plan.

    6. NOTE: When you setup a reseller, you or the reseller will need to visit their (as in the resellers) admin and adjust the plan to include the host and modules and templates. If this isnt done, visitors to the resellers trial sitebuilder site wont work (cant show any templates, modules, etc.).

    7. You also need to tell resellers about their links such as:
    Send your trial visitors here: http://sitebuilder.yourreseller.com
    Send your paying visitors here: http://sitebuilder.yourreseller.com/sitelogin.php
    Your Admin: http://sitebuilder.yourreseller.com/admin_login.php

    Enjoy!
     
  6. noimad1

    noimad1 Guest

    0
     
    RogerW37,

    Great guide, thank you very much. However, I am having one more problem.

    First, I also added to my customers zone file a

    * A 1440 Myip address

    So that his trial sites would point to the IP address where my sitebuilder software is.

    However, that led me to my other problem. When my reseller has a customer setup a trial account it gives them the temporary URL of:

    http://tempname.sitebuilder.resellerdomain.com

    However, if you try to go to that URL it gives the standard plesk screen:

    "This is the Pleskâ„¢ default page" etc.

    However, if you go to:

    http://tempname/myname.com

    His temporary site comes up ok?

    I am sure this is just a matter of getting the dns setup correctly.

    Did you have to make any additional changes to get this to work?
     
  7. RogerW37

    RogerW37 Guest

    0
     
    Thanks noimad1 :)

    See my original post above and find the bolded section. Maybe this will help as it also must be done or trail accounts won't work.

    ADDING RESELLERS - "The Guide"
    LOST RESELLERS FIX

    When you upgrade SiteBuilder, at the time of this writing, it overwrites the /usr/local/apache/conf/sitebuilder.conf file which is bad because it has all your resellers in it.

    Here's how to fix this. The bolded item shows the difference.

    In "2. Add two entries in httpd.conf for sitebuilder:" above...
    Include /usr/local/apache/conf/sitebuilder.conf
    Include /usr/local/apache/conf/sitebuilder_resellers.conf

    We are going to put all the resellers in their own file instead of the sitebuilder.conf file.

    MANUALLY ADD RESELLER - STEP 1
    Here I stated in my original post to put sitebuilder info and sitebuilder resellers info in /usr/local/apache/conf/sitebuilder.conf

    However, only put sitebuilders info in /usr/local/apache/conf/sitebuilder.conf such as:

    ########################## BEGIN MAIN SITEBUILDER

    #NameVirtualHost sitebuilder

    <VirtualHost ##.##.##.##:80>
    Alias /admin/ /usr/local/sitebuilder/htdocs/admin/
    ServerAlias *sitebuilder.*
    DocumentRoot /usr/local/sitebuilder/htdocs
    ServerName *sitebuilder.*
    ErrorLog logs/sitebuilder-error_log
    CustomLog logs/sitebuilder-access_log common
    DirectoryIndex index.php
    AddDefaultCharset UTF-8
    <Directory /usr/local/sitebuilder/htdocs>
    AllowOverride All
    </Directory>

    php_admin_flag max_execution_time 0
    php_admin_value memory_limit 32M

    <Directory /usr/local/sitebuilder/htdocs/install>
    AllowOverride none
    </Directory>

    <Directory /usr/local/sitebuilder/htdocs/users>
    AllowOverride none
    </Directory>

    <Directory /usr/local/sitebuilder/htdocs/repository>
    AllowOverride none
    </Directory>

    <Directory /usr/local/sitebuilder/htdocs/install.bkp>
    AllowOverride none
    Order deny,allow
    Deny from All
    </Directory>

    </VirtualHost>

    ########################## END MAIN SITEBUILDER

    That is also important because sitebuilder upon new releases usually gets new commands inside this file and it should be updated.

    Then put the resellers info in /usr/local/apache/conf/sitebuilder_resellers.conf such as:

    ########################## BEGIN RESELLER SITEBUILDER
    <VirtualHost ##.##.##.##:80>
    Alias /admin/ /usr/local/sitebuilder/htdocs/admin
    ServerAlias *sitebuilder.yourreseller.com
    DocumentRoot /usr/local/sitebuilder/htdocs
    ServerName *sitebuilder.yourreseller.com
    ErrorLog logs/sitebuilder-error_log
    CustomLog logs/sitebuilder-access_log common
    DirectoryIndex index.php
    AddDefaultCharset UTF-8

    <Directory /usr/local/sitebuilder/htdocs>
    AllowOverride All
    </Directory>

    <Directory /usr/local/sitebuilder/install>
    AllowOverride none
    </Directory>

    <Directory /usr/local/sitebuilder/htdocs/users>
    AllowOverride none
    </Directory>

    <Directory /usr/local/sitebuilder/htdocs/repository>
    AllowOverride none
    </Directory>

    <Directory /usr/local/sitebuilder/install.bkp>
    AllowOverride none
    Order deny,allow
    Deny from All
    </Directory>
    </VirtualHost>

    ##################################

    Etc. with another reseller after that.

    This way, when sitebuilder is upgraded, it won't affect your reseller configuration file!

    Enjoy!
    Roger
     
  8. noimad1

    noimad1 Guest

    0
     
    Thank you very much. I did miss the one "A" entry of *.sitebuilder.myreseller.com.

    Thanks a million!

    Regards,
    Damion
     
  9. juliana_padron

    juliana_padron Guest

    0
     
    Hey... are these instructions applied to SiteBuilder Windows 2.0? If it's not, how could I provide this solution?

    Thanks a lot!
     
Loading...