I set up an Ubuntu 16.10 server with the excellent tutorial for The Perfect Server. Now I try to run the cron job for the cms TYPO3 and I run into some problems. At first I attempt to run: php [web_root]/typo3/cli_dispatch.phpsh scheduler This results in the problem that absolutely no .ini files are loaded and PHP tries to run with zero extensions. I also tried php7.0 as the interpreter and various paths to php, but all with the same result. It could easily be demonstrated by running php -i as cron job. Since the script can also be run as a shell script I tried that too. The script starts with: #! /usr/bin/env php which should be a portable way of running php. Unfortunately the effect is that the cron error log shows: /bin/bash: /web/typo3/cli_dispatch.phpsh: /usr/bin/env: bad interpreter: No such file or directory The /usr/bin/env exists and works, but not for the cron user/environment. I read somewhere that ISPConfig 3 lets cron run in a "jailed environment". Is this the cause for this behaviour? If so, how can I release cron from jail and end its stay in the penitentiary institution?