Hello SysCP-community,

it's now 4 years since the day we released the first version of SysCP. Again I want to thank everyone who supported us over the years. Thanks go to you who sent in comments, wishes, ideas, suggestions, patches, positive and negative feedback or just have downloaded and used SysCP. I especially want to thank our sponsors who donate all that glue which helps us work together and improve SysCP.

Some words about the current stage of development: Thanks to atari, d00p, EleRas, JamieWolf, Radiation (alphabetically) and all other which I might have forgotten (shame on me) SysCP made huge steps towards 1.2.20 which will contain many new features, bug fixes and improvements.
We now have support for lighttpd, powerdns, domain keys, exim4, pure ftpd, awstats and many more. SysCP now features native SSL support, a sparkling new logging facility and even a password-reminder. Needless to say that we fixed dozens of bugs and revised many parts of the code.

But we need your help: Due to the heavy changes we made we kindly ask you to test the current development trunk. We expect it to be pretty much stable at this time, but there might be some small glitches so don't test it on your production system.
Since 24c3 we have a snapshot service available at http://snapshots.syscp.org where you'll also find debian packages containing the current trunk.
Please report anything you stumble across at our forums. Thanks, your help is much appreciated!

Again, no cake this year, but stay tuned,

Flo and the SysCP-team

Hello SysCP-community,

today we are releasing the next version of SysCP. SysCP 1.2.19 contains several Bugfixes and some new features.

Especially the nasty bugs regarding the hardcoded Listen and the incomplete Zonefiles are now fixed. I'm really sorry about this, it's not clear how we could have overseen them.
The fix of the Listen-Bug requires some attention when you are updating your installation, because the Listen statement is now switched off by default. You have two options: Switch on the Listen statements again for the affected IP/Port combinations before cron_tasks.php is executed or restore your /etc/apache2/ports.conf.

Thanks to Michael Kaufmann (aka d00p) SysCP now features a complete Ticket System. Your customers could easily create support tickets which can be answered directly at the admin panel. It's quite self-explanatory, so just try to use it, it's great fun ;-) Please also have a look at the settings where you can change the behaviour according to your needs.

One little thing regarding PHP4: Because the php dev team has quit supporting PHP4, we decided not to go for PHP4 compatibility anymore. Therefore SysCP will only work with PHP5.

All changes included in this release are listed at https://www.syscp.org/milestone/1.2.19. As always you'll find the packages at http://files.syscp.org. Direct link to the tarball is: http://files.syscp.org/releases/tgz/syscp-1.2.19.tar.gz. Debian users will get it with their next apt-get upgrade.

Flo and the SysCP-team

Hello SysCP-community,

as the last release includes some nasty bugs we are releasing a new version of SysCP now. It contains the follwing bugfixes:

Safemode will be added again to vhosts at cron_tasks, formtoken is now correctly inserted into all admin_customer-scripts, so editing/adding a customer won't end with "The request seems to be compromised." and the installer now sets the mysql-access-hosts correctly.

These are all nasty bugs, so I'm sure all of you will update. But I also want to state, that with the safemode not being inserted in the vhosts your server might have a big problem, when safemode isn't activated globally. Therefore consider SysCP 1.2.17 insecure (1.2.16 isn't affected though) and update immediately if you're already using it!

As always you'll find the packages at http://files.syscp.org. Direct link to the tarball is: http://files.syscp.org/releases/tgz/syscp-1.2.18.tar.gz. Debian users will get it with their next apt-get upgrade.

Flo and the SysCP-team

Hello SysCP-community,

today we are releasing the next version of SysCP. EleRas and I attended 24c3 over the last four days and we got quite productive, so here's the result:

This release features many bugfixes and new features. The biggest features we're introducing are: mod_fcgid, mod_log_sql, the support of dovecot, building real zonefiles, ips/ports with own vhost containers, reorganized and enhanced settings, wizard-style configuration, and much more. You can find the complete overview on http://www.syscp.org/milestone/1.2.17. At this place I also want to hint to our blog (http://blog.syscp.org) where we noted everything we did the last days.

Due to changes in the style the cronscript works you have to take care when updating: There isn't one big cronscript anymore. Instead you have to call scripts/cron_tasks.php and scripts/cron_traffic.php whenever you want to process tasks or calculate the traffic. This enables you to configure your system in a more flexible manner, e.g, you could calculate the traffic more than once a day if you want. Please change your /etc/cron.d/syscp accordingly. The complete file can be found in your panel, just click on "Configuration".

You'll find the packages at http://files.syscp.org. Direct link to the tarball is: http://files.syscp.org/releases/tgz/syscp-1.2.17.tar.gz. Debian users will get it with their next apt-get upgrade.

I also want to hint to our new snapshot service, which provides you with checkouts of the svn trunk. You'll find them at http://snapshot.syscp.org. Use the debian repository like the stable one, upgrading from stable to testing is just as simple as replacing the line in your sources.list with http://debian.snapshot.syscp.org/.

We wish you a happy new year,
Flo and the SysCP-team

Hello out there,

crowds are gettings smaller down here in the hackcenter at 24c3 but we are still here and coding for eternity (or so... :-P)

I just committed a patch that allows you to specify more than one host as access host from which your mysql users might access their accounts on the mysql server. This hopefully fixes now all the problems many of you had with localhost vs 127.0.0.1 - now you could just add both (which will also happen automatically if you're just trying to add one of them).

Greets, Flo