An old problem is back? https://forum.howtoforge.com/threads/i-get-some-errors-after-upgrading-to-ispconfig-3-2.85384/ I installed a new Ubuntu 24.04 Apache webserver (multi server environment), using the autoinstaller for the first time. All seemed to work just fine and as expected. That is until I configured backup for a website. Database backups are working OK (using gzip) But website backup doesn't when compression options is set to Default: zip (deflate) or tar (gzip) It does work when I change it to tar (gzip). Log output: Code: 07.10.2024-09:49 - DEBUG [plugins.inc:155] - Calling function 'check_phpini_changes' from plugin 'webserver_plugin' raised by action 'server_plugins_loaded'. 07.10.2024-09:49 - DEBUG [plugins.inc:155] - Calling function 'make_backup_callback' from plugin 'backup_plugin' raised by action 'backup_web_files'. 07.10.2024-09:49 - DEBUG [backup plugin.inc:159] - Triggered backup routine for domain id 1, action name backup_web_files 07.10.2024-09:49 - DEBUG [backup.inc:1537] - Performing web files backup of /var/www/clients/client1/web1 in format zip, mode userzip 07.10.2024-09:49 - DEBUG [system.inc:2436] - safe_exec cmd: cd '/var/www/clients/client1/web1' && zip -b '/tmp' --symlinks -r '/var/backup/web1/manual-web1_2024-10-07_09-49.zip' . -x './backup*' -x './bin' -x './dev' -x './etc' -x './lib' -x './lib32' -x './lib64' -x './opt' -x './sys' -x './usr' -x './var' -x './proc' -x './run' -x './tmp' -x './backup*/*' -x './bin/*' -x './dev/*' -x './etc/*' -x './lib/*' -x './lib32/*' -x './lib64/*' -x './opt/*' -x './sys/*' -x './usr/*' -x './var/*' -x './proc/*' -x './run/*' -x './tmp/*' - return code: 18 07.10.2024-09:49 - ERROR - Backup of web files for domain domain.tld failed using path /var/www/clients/client1/web1 failed. 07.10.2024-09:49 - DEBUG [server:224] - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock Code 18 should be a permission issue Code: Zip could not open a specified file for reading; either it doesn't exist or the user running Zip doesn't have permission to read it. but that can't be when using /tmp
A 2nd new webserver, installed the same way on the same OS but with Nginx instead of Apache, doesn't have this problem.
