Configuring Kloxo

Configuring Kloxo

Login with the username admin and the password admin. It will force you to change the administrator password first thing.

After you change your password and reach the main control panel, you will see a red warning at the top saying that you need to configure lxguard. Click the link to take care of that. Accept the default setting of 20, check the box that says you understand it, then click the Update button. Go back to the main page.

Again, you will see a warning at the top of the page, this time for the mail server. Click the link to take care of that. In the “My Name” box, enter your domain name with the prefix “mail”. So if your domain name is yourdomain.com you would enter mail.yourdomain.com into that box. Go ahead and check the Enable Spamdyke box and leave the Enable Domainkey box checked. Those options don’t use a lot of resources. However, the virus scanner will use about 100 mb of memory to run. Leave that unchecked for the time being. Also leave the rest of the settings in that panel the way they are. Click the Update button. Go back to the main Kloxo page.

Before we start adding things, let’s make sure that all of the necessary services are running. As both a Kloxo and Linux administrator, it’s important for you to understand that not all services are managed as the Linux administrator. Many services are controlled exclusively by Kloxo. For example, you probably won’t be able to start the courier-imap (pop email server) as the Linux administrator, but you can as Kloxo administrator. The two places to do that are:

Linux Service Administration – Webmin, by selecting the System icon at the top, then opening the “Bootup and Shutdown” icon.

Kloxo Service Administration – Main Kloxo admin panel in the Server:Linux box, then open the Services icon.

So lets get everything running that needs to be running by opening the Kloxo Services icon, as described above. What you want to see is in the image below, but you’ll probably see a lot of red at first.

The “State” column indicates whether a service is running. If it’s green it’s running, if it’s red it’s stopped, and if it’s gray it’s not installed. For any service that is red under “State”, click on the red button and see if it goes to green. It should. Do that for all stopped services. If for some reason you have difficulty getting services started in Kloxo, try with webmin under System in “Bootup and Shutdown.”.

The “Sb” column indicates whether the service is configured to start at boot time. You want to do that for all installed services, so click them to make them all green.

Djbdns (tinydns) button should be gray, and that’s fine because we are using named (BIND) instead, which is a much more advanced DNS server. Likewise lighttpd should be gray, and that’s fine because httpd (Apache) is used instead, which is a more advanced web server.

The above image shows that spamassassin is installed and running. Your spamassassin running lights will be gray, since spamassassin isn’t installed by default. That’s fine, since we’ll be using spamdkye as a spam filter instead. Just leave spamassassin uninstalled.

You may wish to reboot your server now to see if everything comes back up as it should.
Hint: You can reboot the system either from the VPS control panel, from Kloxo in the “Machine” box, using webmin (System category, Bootup and Shutdown icon), or by issuing this command in PuTTY.

# shutdown –r now

If everything came back up as it should, go to webmin and check some of the other critical services (click the System icon at the top of webmin, then open the “Bootup and Shutdown” icon. Pay particular attention to the following services.

Clamav – It will not be running because we specified to not use it in the email scanning settings. You may decide to use it in the future, but you should let Kloxo control clamav.

Crond – Should be running, start it if it is not running, and make sure it’s set to restart at boot time.
Mysqld – Should be running, start it if it is not running, and make sure it’s set to restart at boot time.
Let’s create your primary domain now. Log back in to Kloxo as admin.

http://youripaddress:7778

You will see some tabs near the top (Home, Domains, Subdomains, Mail accounts). Select the Domains tab. You should get a red warning that you haven’t setup a default DNS. Fill it out like the following image, substituting your primary business domain in place of yourdomain.com. Click Add.
In the future, as you add reseller accounts, you will create DNS templates for the reseller’s business domain to give the appearance of private label branding for your resellers.

Once the DNS template is done, click on the Domains tab again. Now enter your domain name in the two boxes, as was done in the following image, then click Add. That created your web space, your DNS entries, and your FTP account, as well as a few other entries around your server. Since this is the first domain you’ve created you will want to verify that everything went well.

Verify that your web space exists. You can do that by using webmin. Click the Others button at the top, then select File Manager. Double-click the Home folder, then the admin folder. You should see a folder with your domain name. Open it, and you should see a cgi-bin folder, an image folder, and an index.html file. That’s your web space. Client accounts will also be in the /home directory, but will have their own directory instead of being in the /home/admin directory.

Verify that your DNS entries were made. You can do that by clicking the Servers icon at the top of webmin, then clicking BIND DNS Server. You should see a Zone icon for your domain. Click on that icon, then click the A icon at the top left. That will show you all of the entries that are defined for your domain. If that’s there then all is well. There will be a new zone created for each domain you add.

Verify that the DNS server is responding to queries about your domain. Do that by logging in to PuTTY as root, then issue the following “dig” command, substituting your IP address after the @ sign and your real domain name instead of yourdomain.com.

# dig @174.34.133.23 yourdomian.com