Archive for the 'Webmin Support' Category


Cloudmin Introduction

Cloudmin Introduction

It is a UI built on top of Webmin for managing virtual systems, such as Xen, KVM and OpenVZ instances. Using Cloudmin you can create, destroy, resize, startup, shutdown and restrict multiple instances using different virtualization technologies from a single interface. It also has a full command line API that can be used to manage virtual systems from a shell script or via HTTP requests.

Cloudmin is designed for use by VPS hosting companies that sell virtual systems to their customers, but is also suited for anyone who wants to get into virtualization for application management, testing, controlling a cluster of Virtualmin hosts, or just to learn about cloud computing.


Got a packet bigger than ‘max_allowed_packet’ bytes

If you get this error when trying to dump a MySQL DB, this is due to the packet limit of MySQL server.

To solve this issue, add an extra entry into /etc/my.cnf file under [mysqld] group:

max_allowed_packet = 100M

This will reset the limitation to 100Mb for file insertion into blob type (or longblob) column. Then restart mysql server:

/sbin/service mysql restart



Troubleshooting BIND

Troubleshooting BIND

There are a number of tools that are available to assist with testing and troubleshooting problems with your BIND configuration. The simplest tool on most systems is the host command, which simply performs an address lookup or a reverse address lookup. More complete information can be gathered using dig.

The simplest usage of host is to lookup an address, or a name.

$ host has address mail is handled by 0

Ask for the name servers that are authoritative for a domain by using the -t ns command line option..

$ host -t ns name server name server name server name server

The MX record can be retrieved by using the -t mx option.

$ host -t mx

Just like host, it is possible to query your default system resolver, or you can query a name server specified on the command line. For example, I could query my local name server about the domain.

$ dig @

More at


Creating and editing ACLs

Creating and editing ACLs

Before you can block or allow requests from some address, to some server or for some page you will need to create an appropriate ACL. The basic steps to do this are :

1. Select the type of ACL to create from the drop-down menu below the Access control lists table and click the* Create new ACL* button.

2. On the form that appears, enter a name for your new ACL in the ACL name field. If more than one has the same name, it will be treated as matched if any ACL with that name matches. The name should consist of only letters and numbers, with no spaces or special characters.

3. Fill in the rest of the form as explained in the table below.

4. In the Failure URL field, enter a complete URL that clients who are denied by this ACL will be redirected to. This allows you to define custom error pages to be displayed instead of the default Squid responses.

5. Click the Save button at the bottom of the form.

Once an ACL has been created you can edit it by clicking on its name in the list, changing the fields and clicking Save. Or your can delete it (if it is not in use by some proxy or ICP restriction) with the Delete button. As usual, the Apply Changes link must be used to activate any changes that you make.

Squid has an amazing number of ACL types, although not all are available in all versions of the server.

Many types of ACL are inappropriate for certain situations. For example, if a client sends a CONNECT request the URL path is unavailable, and thus a URL Path Regexp ACL will not work. In cases like this the ACL is automatically assumed not to match.

Article taken from -

Changing the proxy ports and addresses in Webmin

By default, Squid listens for proxy requests on TCP port 3128 on all of your system’s IP addresses. Because this is not the usual port that proxies are run on (8000 and 8080 seem to be the most common), you may want to change it. You might also want to edit the listening address so that only clients on your internal network can connect, if your system has more than one network interface.

To specify the ports that Squid uses, follow these steps :

1. On the module’s main page, click on the Ports and Networking icon.

2. In the Proxy addresses and ports table, select the Listed below option. In the table below, each row defines a listening port and optionally an address to bind to. Any existing ports and addresses will be listed, followed by a single blank row for adding a new one. In the first empty field in the Port column, enter a port number like 8000 or 8080. In the Hostname/IP address column, either select All to accept connections on any of your system’s interfaces, or the second option to enter an IP address in the adjacent text box. Using this table, Squid can be configured to listen on as many ports as you like. However, because only one blank row appears at a time you will need to save and re-open the form to add more than one new port.

3. ICP is a protocol used by Squid to communicate with other proxies in a cluster. To listen on a port other than the default of 3130 for ICP, fill in the ICP port field. This is not generally necessary though, as only other proxies ever use this protocol.

4. Squid will normally accept ICP connections on any IP address. To change this, select the second radio button in the Incoming UDP address field and enter one of your system’s interface IPs into its text field. This can be useful if all of the other proxies that your server might want to communicate with are on a single internal LAN.

5. Click the Save button at the bottom of the page to update the configuration file with your new settings, then click the Apply Changes link back on the main page to activate them.

Article taken from

« Prev - Next »