error500 after upgrade

[helihans]

After upgrading from 2.13.6 r237 to the latest version, I received an error 500, both front-end and back-end.
PHP is 8.3.

I went back to the previous version and everything worked again. Any ideas?

[sternchen8875]

Oh, sorry

do you use a .htaccess on this domain?  if YES, pls rename it for a test

now any questions... 
- do you work in a subfolder of the used domain?
- do you use the actual unzip.php to unpack the WB-package on your server?

Error 500 is a server-error, first file is a .htaccess (but not a htaccess.txt), next one is the config.php, check the datas there,
if you dont use the method with the unzip.php, everything its possible. Check also the index.php in the wb-root-folder

if you start a next try, please make a file-backup from the "new", updated files

[helihans]

Thanks, even renaming htaccess makes no difference.
wb is in the root, and I'm also using the latest unzip.php (even with the old one, it wouldn't work).
This is the second website; another one (exactly the same) updated fine.

 I'm currently downloading the files via FTP, which is taking a while, then I'll put the old one back.

[helihans]

Found it
There was insufficient disk space, but strangely enough, I didn't see any unusual messages during the extraction process.

The new version is now working without any problems, apologies for the inconvenience.

[sternchen8875]

Danke für die Rückmeldung und es gibt keinen Grund zur Entschuldigung, ganz im Gegenteil: es zeigt, das wir am unzip-Script noch eine Prüfung benötigen, ob der berechnete freie Festplattenplatz ausreichend ist und ob des anschließende Entpacken erfolgreich war. In der Theorie hätte das Erreichen des Limits eine Warnung auslösen sollen, die wäre aber abhängig von den Server- und WB-Einstellungen zum Fehler-Logging

Thank you for your feedback, and there is no need to apologise. On the contrary, it shows that we need to add a check to the unzip script to see whether the calculated free hard disk space is sufficient and whether the subsequent unpacking was successful. In theory, reaching the limit should have triggered a warning, but this would depend on the server and WB settings for error logging.