Hi @stumur
This is actually a bit strange. There’s quite a lot of warnings/notices in the log but those don’t seem related in any way to the crash and shouldn’t really affect Forminator/update also.
There is, however, a single Fatal Error reported – and that would cause crash.
That Fatal Error is a memory allocation error, meaning that code on site tries to use more memory than it has available. The error points to this file of WordFence plugin
/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php
but I would hesitate to put the blame on WordFence. Quite often (in most cases actually) such errors are the direct cause of the site crash but are not cause of the actual issue. In other words – site crashes because of that error but the error happens “because of something” and is what we need to find out.
That being said, I checked and the line 50 of that file (to which error poins) is this code
$tmpContents = file_get_contents($tmpFile);
This is trying to read temporary file (entire file at once) in order to – I quote from the code comment – “verify file has finished writing (sometimes the disk will lie for better benchmarks)”.
All in all, it would mean that upon update there’s an issue with reading some/one of the files (that may in happen to be related to Forminator) that causes this code to “go wild” and use up all the memory. I’m not sure what exact Wordfence feature (aside the fact that it’s WAF) this code is related too and what are the settings of your server PHP but it is possible that simply increasing PHP memory limit would help – that is, if this is happening only due to the complexity of the site and/or size of some file
That said, this all is under assumption that the error in log matches Forminator update time.
But I’d also suggest making sure that the server has free storage space available, and double-checking file/folder permissions.
You also mentioned that you have disabled all the plugins – but was Wordfence for sure entirely disabled? If you are using Wordfence for a long time (years) you may still have a “lefover” configuration – back in the days plugin used to use additional file and call it via .htaccess/.user.ini file directly (so it was executed even if the plugin was disabled) – this would be worth checking as well.
Kind regards,
Adam
