- A bug in the updater for multiserver setups has been fixed.
- A bug in the apache rewrite rule setup has been fixed.
- A bug in jk_init.ini has been fixed which affects only jailkit 2.9 installations.

Jailkit 2.8 is broken on 64Bit systems. This is independant if you use ISPConfig or not and thats the reason why the jailkit developer released jailkit 2.9 a few days ago. See jailkit homepage for details.

* Restarting web server apache2
* We failed to correctly shutdown apache, so we're now killing all running apache processes. This is almost certainly suboptimal, so please make sure your system is working as you'd expect now!
apache2: Syntax error on line 281 of /etc/apache2/apache2.conf: Syntax error on line 32 of /etc/apache2/sites-enabled/000-ispconfig.conf: </Directory>NameVirtualHost> directive missing closing '>'
... waiting .... ...fail!

@mcharlet
I assume you mean from 3014 to 3016, which is what I did, my firewall rules are fully intact here - just checked em to be sure

@till
Yeah, I added the newline, restarted apache2 and all was fine.. Will the rest of the script have completed as normal?

BUT....
@whoever!

I usually have a subdomain redirected to webmail, this suddenly stopped working...

I figured this out, but in the process, I discovered that the vhost files in sites-enabled became corrupt, after the upgrade they are intact, but if the redirect is changed, the RewriteCond lines end up garbled, resulting in an error..

To reproduce (unless this just on my system - which is why I have not filed bug report):

As stated, I already had a subdomain that has a redirect.

In the webbrowser GUI goto:
Sites/Subdomain
Redirect path (change it to anything you like)/save
try the domain, here the result was 404
check the vhost file in sites-enabled

Also, even if redirect is changed back, it still garbles the vhost file entry.

Yeah, I added the newline, restarted apache2 and all was fine.. Will the rest of the script have completed as normal?

Click to expand...

yes.

Is it just me? if not, it's easily fixed anyways

Click to expand...

Please post the redirect rule that ispconfig generated in the vhsot file. ISPConfig 3.0.1.6 is expanding the path in the rewrite rule to be the full system path, this was neede to fix a problem in debian. Maybe this change causes problems on your system. And I need to know which linux distribution you use and the apache version.

Ok, so your original redirect line that you entered in the interface was /var/www/webmail ?

Then it is relateively clear for me what happened. ISPConfig does not accept redirects anymore that point to a absolute path outside of the website directory for security reasons since this release. The reason for this is that your clients are able to create redirects and if ispconfig would allow absolute paths then it would be possible that someone creates redirects that point to directorys where he should not have access to.

ISPConfig does not accept redirects anymore that point to a absolute path outside of the website directory for security reasons since this release. The reason for this is that your clients are able to create redirects and if ispconfig would allow absolute paths then it would be possible that someone creates redirects that point to directorys where he should not have access to.

Click to expand...

I would like to use my new ISPConfig3 server for TYPO3 webhosting as i did with my ISPConfig2 server. One TYPO3 source within the folder /var/www/typo3src-4.2.8/ and the dummy files within the web of the clients, synchronised with a symbolic link as described here: http://www.howtoforge.com/typo3_on_ispconfig

I would like to use my new ISPConfig3 server for TYPO3 webhosting as i did with my ISPConfig2 server. One TYPO3 source within the folder /var/www/typo3src-4.2.8/ and the dummy files within the web of the clients, synchronised with a symbolic link as described here: http://www.howtoforge.com/typo3_on_ispconfig

Does that mean such setup is not possible anymore?

Click to expand...

This is something different and has nothing to do with apache redirects. Typo3 uses symlinks and not apache rewrite rules.

Symlinks are disabled too by default as your clients can misuse the setup to access data from your other clients but you can enable symlinks by commenting out the php open_basedir directive in the vhost template.