XF 2.2 File health check failure

Recently moved from vBulletin to Xenforo, and things are going well overall. Having said that, I have begun getting this message every night:

File health check results
Check completed on 5,443 files. The files listed below have contents different from those originally downloaded.

If you have edited these files yourself, you may ignore this message, otherwise you should investigate further as this may be evidence of corrupted or altered files.
XenForo Redirects for vBulletin
src/addons/XF301VB/SourceLocation/index.php Unexpected contents

This is the original contents of that file:

<?php

// Enter the full path to your XenForo directory here:
$dir = '/home/username/public_html/xenforo2';

require($dir . '/src/XF.php');

XF::start($dir);
XF::runApp('XF301VB\Pub\App');

And here are the contents of my file:
<?php

// Enter the full path to your XenForo directory here:
$dir = '/home/XXXXX/public_html/forum';

require($dir . '/src/XF.php');

XF::start($dir);
XF::runApp('XF301VB\Pub\App');


I feel this is a false positive, however I'm not sure how to mark this file as safe.
Is there a way to tell File Health to chill?
 
Solution
Is there a way to tell File Health to chill?
No. The check depends on some hash code.

What you can do is download the file again from source and overwrite your file.
The other way is to generate a hash code yourself so the issue will be gone.

Or Xenforo needs to fix it.

Or you can generate a code yourself.
Is there a way to tell File Health to chill?
No. The check depends on some hash code.

What you can do is download the file again from source and overwrite your file.
The other way is to generate a hash code yourself so the issue will be gone.

Or Xenforo needs to fix it.

Or you can generate a code yourself.
 
Solution
Thank you very much.

Uploading the original files would not have worked in this situation, as that file is intended to be edited (as far as I understand).

However running
php cmd.php xf-addon:build-release XF301VB

Allowed me to create / export a new hashes.json that fixed the problem.
 
Back
Top Bottom