• Resolved Tamara-IT

    (@tamara-it)


    Hello,
    I’ve found this error message showing today:
    Fatal error: Uncaught wfWAFStorageFileException: Unable to verify temporary file contents for atomic writing. in /var/www/clients/client5/web114/web/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php:52 Stack trace: #0 /var/www/clients/client5/web114/web/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(659): wfWAFStorageFile::atomicFilePutContents(‘/var/www/client…’, ‘<?php exit(‘Acc…’) #1 [internal function]: wfWAFStorageFile->saveConfig(‘livewaf’) #2 {main} thrown in /var/www/clients/client5/web114/web/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php on line 52

    I’ve entered the backend, were the error was showing as well, deactivated Wordfence, and the error disappeared.
    I’ve run some plugin updates, then reactivated Wordfence: the error was not showing anymore.
    I hope it does not shows again, but I’m wondering about this and if it may cause some major issues.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support WFAdam

    (@wfadam)

    Hello @tamara-it and thanks for reaching out.

    It’s good that the error disappeared but if you don’t mind, can you send a diagnostic report to wftest @ wordfence . com? You can find the link to do so at the top of the Wordfence Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

    I would like to review it and see if I can find something causing this.

    Thanks!

    Thread Starter Tamara-IT

    (@tamara-it)

    Hi, report sent as per your instructions. I’m looking forward to know more about it!

    Plugin Support WFAdam

    (@wfadam)

    Thanks for sending those diagnostic reports @tamara-it

    Looking at the errors a little deeper, this could be an issue with your host running low on free space. Can you verify that your host has enough free storage space?

    If that end is all good, then we could try renaming the /wp-content/wflogs/ to /wp-content/wflogs-backup/ to see if that changes anything? If this seems to remove the error, then you might need to reoptimize the firewall.

    You did mention that the error went away when you reactivated the plugin. I would make sure your scans are still working and the firewall is still optimized. If they are, just keep an eye out for this error again and follow the steps above to resolve.

    Let me know if this helps!

    Thanks!

    Thread Starter Tamara-IT

    (@tamara-it)

    Ha!
    I downloaded some old stuff from the root, for safety’s sake… then deleted the file from the server: everything worked fine!
    Before this, I’ve modified the max upload file size from .htaccess and, obviously, it did not work.
    Thanks for your help, I hope I didn’t waste too much of your time!

    Plugin Support WFAdam

    (@wfadam)

    Glad you were able to resolve the issue @tamara-it

    If you have any other issues or questions, as always, feel free to post another topic and we would be happy to assist!

    Thank you again for your support!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Fatal error’ is closed to new replies.