Installation FAQ

In general InterWorx works on most common RedHat based distros. Please view our Distro Guide for more information.

It is our intention is to eventually support all rpm based distributions.

Support is also planned for for Debian (which is not RPM based but is package based) and FreeBSD. NO ETA IS AVAILABLE

There are no plans to support Windows based servers.

Yes, if you can run a ssh script and are able to use the rpm command, you should have no problem installing InterWorx-CP. If you are uncomfortable doing this or encounter problems, an InterWorx staffer can install it for a $50 fee.

We recommend the “server” class install as it provides most of what you need and leaves off many things that you don’t. A “base” install will also work, but you will need to add many packages during the InterWorx install. Doing a “full” install will give you many things that you don’t need which will eat up disk space and contain many more packages to keep updated and patched.

There are no hard and fast requirements, but here is a recommended scheme that works for us:

/boot = 512M
/tmp = 2G
swap = 2G (varies with mem)
/ = rest 

InterWorx-CP does not need any special partitioning scheme, however whatever partition that houses the /home directory (or /chroot if you intend to configure your server to support Jailed Shells) -- whether it’s own partition or the / [root] partition -- will house the InterWorx software and all of your websites and related data so it needs to be large enough to accommodate it. For Clustering configurations the InterWorx home directory has been removed from /home/interworx and moved to /usr/local/interworx (with a symlink from the old to the new location). If /tmp has it’s own partition you may want to give it at least one gig of space for use during import operations, we recommend two GB.

Here are three examples of partitioning schemes from InterWorx boxes. All work fine:

Mount Point  	Partition  	Size 

/               /dev/hda2       110G
/boot           /dev/hda1       99M

-- or --

/               /dev/sda3       981M
/boot           /dev/sda1       99M
/home           /dev/sda8       125G
/tmp            /dev/sda7       994M 
/usr            /dev/sda6       9.7G
/var            /dev/sda5       9.7G

-- or --

/  	        /dev/sda5  	70.82 GB
/boot 	        /dev/sda1 	0.09 GB
/tmp 	        /dev/sda3 	1.00 GB
/storage 	/dev/sdb1 	378.25 GB
/backups 	/dev/sdc1 	76.81 GB

These are NOT mutually exclusive.

Please visit the System Requirements page for more information.

No, InterWorx only works with DJBDNS.

No, InterWorx only works with qMail.

Yes, it is safe to upgrade your PHP. Since InterWorx runs it’s own instance if PHP, it will not interfere with the functioning of the CP.

Yes, it is safe to upgrade your MySQL. Since InterWorx-CP runs it’s own instance if MySQL, it will not interfere with the functioning of the CP.

You can recompile the Apache on your server to add modules, but InterWorx-CP will encounter errors without the suexec settings in the .iworx version of Apache.

InterWorx-CP will install its own versions of these software packages during the install process. If other versions are installed they will cause errors in the install script and you will be asked to remove them. For that reason it is best to remove any versions of apache (or another web server), or any MTA, MDA, or FTP servers, before beginning the install.

1. Add an A record for the mail server if one doesn’t exist already. This A record should have the IP of the off-server mail box (eg. mail.mailserver.com)
2. Next, add the MX record for the previously added ‘mail.mailserver.com’ and give it a ‘target’ of ‘10’ or some other integer for the precedence level. (one record)
3. Run the command /home/vpopmail/bin/vdeldomain <domain> to tell qMail that mail for that domain is not being handled locally.

If you have an InterWorx server with a domain on it whose mail is hosted on another server, you will need to run the following commands to be able to mail that domain name from your server.

# ~vpopmail/bin/vdeldomain YOUR-DOMAIN.tld 

Of course, you will replace YOUR-DOMAIN.tld with the affected domain name. This command will turn email off on the domain so that emails will not be sent to the server if you use an alternate email server.

A SiteWorx account will have the language you specify on the SiteWorx account creation screen. Once logged in, the interface will be translated into that language. To change this default, as well as change the language on the login screen do the following:

You can modify the default language set for all new SiteWorx accounts by editing /home/interworx/iworx.ini. Look for this block:

[iworx.language] 
ini="languages.ini"
siteworx="en-us" 

And change “en-us” to the 2 letter language code for your language.

(Look in /home/interworx/lang/languages.ini to find the corresponding 2 letter code for your language.) Again, this will only change the default language for all future SiteWorx accounts. If you have already created a few SiteWorx accounts, you will need to change the language on those manually. However, all new SiteWorx accounts will automatically be set to your chosen default language.

Version 2.1.0 will add a nodeworx=”lang_code” entry, so similar to the way new siteworx accounts pull the siteworx= language, new resellers will pull the nodeworx= language.

UPDATE: With InterWorx 3.0 language settings are determined by each individual user. Thos can be changed (even for the master user from the following screens:

• NodeWorx:Users (in NodeWorx) -- for all NodeWorx users including the system admin
• Resellers:Users (in NodeWorx) -- for all resellers
• SiteWorx:Users (in SiteWorx) -- for all SiteWorx users including the website admin

1. Edit /etc/yum.conf
2. Locate the line exclude= and add the packages you wish to exclude
3. Save /etc/yum.conf

No, you do not have to register your own DNS server. The only real reason to register your own is aesthetics and if you are doing business it looks more professional. But if it’s just your own projects then by all means use the one provided by your data center (e.g. Sago). Many people do.

Be aware that Sago pulls DNS data from the InterWorx boxes 4 times a day so it may take slightly longer for your sites to resolve. For security reasons there is no way to PUSH the data.

Yes, You need some ports open on an InterWorx box, or you’ll get an invalid license file error or a non functional box. Here is an example of a sample of an iptables -L -n on an InterWorx box with the correct open ports.

ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:110 state NEW
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:995 state NEW
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:143 state NEW
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:80 state NEW
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:2080 state NEW
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:443 state NEW
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:2443 state NEW
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:21 state NEW
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:22 state NEW
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:25 state NEW
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:53 state NEW
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:953 state NEW
SOURCE: Sagonet Support

The license currently installed on this server is showing up as invalid to InterWorx-CP. This may be nothing more than a simple misconfiguration on your system, or the license could actually be invalid. Before opening a support ticket please try the following:

1. Check your system time and verify that it is correct. Even if it is off by only a few minutes you should reset it to the correct time. The easiest way to do so is to run the following in a root shell:

service ntpd stop
ntpdate bitsy.mit.edu
service ntpd start

2. Make sure your firewall has port 2443 open both outbound and inbound. If it’s not open then InterWorx-CP can’t talk to the licensing server.

3. Run the following command from a root shell to re-sync your license after checking the system time:

/home/interworx/cron/license.pex --sync

4. After performing the above please refresh [the license error] page to see if the license is now valid.

5. Finally, if the license is still showing as invalid please open a support ticket with the datacenter which sold you your license. If you bought your license directly through the InterWorx-CP website then please open a ticket with [the InterWorx team] directly.

There are three other possible fixes depending on the exact cause:

The most common (a variation on the same):

Assuming you have a valid license but your InterWorx license is coming up as invalid, do the following:

service ntpd stop
ntpdate tick.usno.navy.mil
service ntpd start

Edit the file /etc/ntp.conf

Scroll down to where it says server 127.127.1.1 and change it to " server tick.usno.navy.mil " (minus the quotes)

The IP is 192.5.41.40 in case the server is DNSless.

Then run this command:

# ~iworx/cron/license.pex --sync

After fixing ntp, you can also run this command to set the correct date in BIOS:

# hwclock --systohc

Another possibility is:

Sometimes the invalid license in InterWorx is caused by log files. If you try the first KB article and Iworx is still not up, try this.

From the Sagonet Knowledge Base:

Here’s exactly what I did to fix a customer’s server. I started off with the usual way to fix the invalid license issue, then it evolved into something else.

Red Hat Linux release 9 (Shrike)
Kernel r on an m
root@x.x.x.x's password:
[root@server9 root]# service ntpd stop
Shutting down ntpd: [ OK ]
[root@server9 root]# ntpdate tick.usno.navy.mil
2 Feb 14:50:46 ntpdate[11502]: step time server 192.5.41.40 offset 279.134463 sec
[root@server9 root]# service ntpd start
Starting ntpd: [ OK ]
[root@server9 root]# /home/interworx/cron/license.pex --sync
File size limit exceeded

Generally, if the sync runs, there is no message at all. A file limit exceeded error usually means a log file is full. Check /var/logs first for any logs 2GB or larger.

[root@server9 log]# ls -lh
total 2.1G
-rw------- 1 iworx iworx 9.5M Feb 2 14:44 access.log
-rw------- 1 iworx iworx 0 Jan 16 2004 access.log.1
-rw------- 1 iworx iworx 11M Feb 2 07:50 error.log
-rw------- 1 iworx iworx 8.2K Jan 16 2004 error.log.1
-rw-r--r-- 1 iworx iworx 22K Feb 2 07:44 horde.log
-rw------- 1 iworx iworx 1.6M Jan 22 2004 iworx-65.110.53.100.log.gz
-rw------- 1 root root 2.0G Jan 31 04:28 iworx.log
-rw------- 1 iworx iworx 514 Jan 16 2004 iworx.log.1
-rw------- 1 iworx iworx 7.6K Oct 15 18:59 mysqld.log
-rw------- 1 iworx iworx 658 Jan 16 2004 mysqld.log.1
[root@server9 log]# pwd
/home/interworx/var/log

This is the next place you check. As you can see above, the iworx log is 2GB, the limit of ext file systems.

[root@server9 log]# mv iworx.log iworx.log_old
[root@server9 log]# touch iworx.log
[root@server9 log]#

[root@server9 log]# /home/interworx/cron/license.pex --sync
[root@server9 log]#
^^^^^^^^^
No errors, that's good. 

You could safely remove the file if you’d like, but since this isn’t my server I’d rather not do that. And yet another possibility:

And lastly:

Due to an update on June 29, 2005, Red Hat 9 servers with InterWorx were getting Invalid License errors. The problem was a curl version issue. To fix this issue, do: yum update

~iworx/cron/license.pex --sync 

This shouldn’t effect anyone now, but I’m including it just in case.

Yes.

yum install php-pgsql
service httpd restart

It only shows up if you are running CentOS 4.x or RedHat Enterprise 4.x with NAT installed and configured AND for upgraders you also need to make some changes to your file system in order to work:

• /home/vpopmail needs to be moved to /var/vpopmail
• /home/interworx needs to be moved to /usr/local/interworx
• Symlinks must be created from the old to the new locations.

The screens to control load balancing do not appear unless NAT is also properly configured. When this is the case you will see a Clustering category on the main menu.

InterWorx maintains a server with mirrors of the operating systems it supports as well as the InterWorx-CP and other provided RPMs.

Each distribution has it’s own archive.

STATUS: Rebuilding system disk quotas
STATUS: (ignore errors regarding: 'Old file not found')
quotacheck: Mountpoint (or device) / not found.
quotacheck: Can't find filesystem to check or filesystem not mounted with quota option.

This error means your VPS provider has turned off quotas in Virtuozzo. It is safe to complete the install, but InterWorx will not work properly (specifically you won’t be able to create SiteWorx accounts) until this is fixed. You will need to contact your VPS provider’s support department to get this turned on. They will need to shut down the VPS to do it so you will save time if you give them permission to do so in the initial request.

This is a normal error on a Virtuozzo VPS install. As long as the iworx service starts in the end you are fine.

This always happens until you run goiworx.pex for the first time and is safe to ignore.