Debian 11 with kernel 5.10.0-42-amd64 PHP 7.4.33 ISPConfig 3.3.1p1 Did an apt-get upgrade. Also upgraded the kernel to 5.10.0-42-amd64. After upgrade and reboot, cannot get acess to ispconfig. Getting a white screen. Got the following error. Code: Uncaught InvalidArgumentException: Please make sure the folder '/usr/local/ispconfig/interface/lib/classes/IDS/../../../temp' is writable in /usr/local/ispconfig/interface/lib/classes/IDS/Monitor.php:159 Tried changing the permission of temp to 777 and the files inside to 666 but did not work. The files are already owned by ispconfig user. Then did the solution from the following link. https://forum.howtoforge.com/threads/ispconfig-error-500.93106/ Commented out the following in /usr/local/ispconfig/security/security_settings.ini Code: [ids] #ids_anon_enabled=yes ids_anon_log_level=1 ids_anon_warn_level=15 ids_anon_block_level=20 #ids_user_enabled=yes And I can get access. Phew for now. I want to put it back to where it was. What do I need to do in Debian to bring back to where it was?
Have you tried to do an ISPConfig update with: ispconfig_update.sh --force and let the update reconfigure services?
I have not done this yet. Here is an email I got from another server. It is on auto update and it states something about hardening. Here is the email. ----------------- start ----------------------- php8.3 (8.3.31-2) unstable; urgency=medium * The systemd unit file has been hardened. Extra options from sapi/fpm/php-fpm.service.in has been used: PrivateTmp=true ProtectSystem=full PrivateDevices=true ProtectKernelModules=true ProtectKernelTunables=true ProtectControlGroups=true RestrictRealtime=true RestrictAddressFamilies=AF_INET AF_INET6 AF_NETLINK AF_UNIX RestrictNamespaces=true This should work in the default environments, but you might need to modify the systemd unit file if you are using less standard FPM configuration. -- Ondřej Surý <[email protected]> Sun, 10 May 2026 19:38:59 +0200 ------------------ end ----------------------- Could this option, "PrivateTmp=true", be causing the issue? Am I the only one having this issue? P V Anthony
Yes, this is probably the cause, see here: https://forum.howtoforge.com/thread...ids-temp-folder-becomes-read-only-syst.95140/