Currently i’m evaluating Interworx and i’m very impressed, good job and keep up the good work!

I found some small bugs, maybe someone can confirm these;
I’m using a default install on Centos 5 running in VMware 6.

After I login, and I go Server / Software updates.
Then I click on the “Automatic Update Options” UPDATE button without changing something. After this i click in the menu on the " NodeWorx Home" link. This way all static text in InterWorx is in CAPITALS between ## ## like


  1. When I go to System Services / Web server and I click on the link PHP Info (https://xxx:2443/nodeworx/http.php?mode=phpinfo) then i looks like the PHP file is not parsed well and output looks like

phpinfo() PHP Version => 5.1.6 System => Linux interworx.synrg.nl 2.6.18-8.1.8.el5 #1 SMP Tue Jul 10 06:50:22 EDT 2007 i686 Build Date => May 8 2007 19:37:29 Configure Command => ‘./configure’ ‘–build=i686-redhat-linux-gnu’ ‘–host=i686-redhat-linux-gnu’ ‘–target=i386-redhat-linux-gnu’ ‘–program-prefix=’ ’

phpMyAdmin is working fine, so something else should be wrong here.

  1. For me it was impossible to login after my initial install. After I stopped the firewall via LyNX I could login from a remote machine. Maybe a good idea to deactivate the firewall and after first login ask the admin to whitelist IP’s and activate it.

Can anyone confirm these or pls let me know what i’m doing wrong :slight_smile:

I reinstalled Interworx again, on a different server. This time using Xen + CentOS (previous post was Vista + Vmware + CentOS). All three reported issues are still there, and I followed the installation guide, so is it possible these are bugs?


I’ve confirmed 1), this is indeed a bug. If you find an other ways you can reproduce this same behavior, let us know.

  1. is a confirmed problem on CentOS 5 - it’s using the CLI version of php, which is reporting the info in non-html format.

  2. I agree, the install script should take care of this. I’ll make sure it gets tweaked.

Thanks for posting these! We’ll get them fixed asap.


this is happing to my new server, this is on a totally new clean install with centos 5 x64
was this fixed or how do i fix it
Thank you