Issue Permission problem - Invision power board - forum

[NITROFOX]

Server operating system version

AlmaLinux 8.10 (Cerulean Leopard)

Plesk version and microupdate number

Plesk Obsidian 18.0.73 Update #2

Hi,

I've been having a problem for some time, according to the "Diagnose & Repair" tool, there is a domain that is always with the error "There is incorrect ownership on some items in the WWW root directory of the domain".

I contacted Plesk, who informed me that after checking they concluded:

I’ve investigated the issue you described regarding unexpected changes to file permissions on your websites.
Based on my findings, this behavior is not caused by Plesk itself. Plesk does not modify file permissions within domain directories automatically.
Instead, these changes are likely triggered by scripts, plugins, or other processes running within the websites themselves.
During my review, I manually corrected the permissions for several affected files.
How to restore default permissions in virtual host directory on Plesk for Linux? – Plesk: How to restore default permissions in virtual host directory on Plesk for Linux?

However, shortly afterward, some of these files reverted to incorrect permissions again. This confirms that an internal process or script is actively modifying them. Here are a few examples of the affected files:

- /var/www/vhosts/site.com/public_html/forum/datastore/widget_stats_.....php
- /var/www/vhosts/site.com/public_html/forum/datastore/widget_achievements_.....php
- /var/www/vhosts/site.com/public_html/forum/datastore/widget_topContributors_.....php
- /var/www/vhosts/site.com/public_html/forum/datastore/leaderHashes_....php

I strongly recommend consulting with your website developer to identify the script or plugin responsible for these changes.
If these files are being created dynamically, the process should be adjusted to assign the correct permissions upon creation.

So I've been doing some research on invision, and all I found was this:

https://invisioncommunity.com/4guides/advanced-options/configuration-options/controlling-file-and-folder-permissions-r279/

/* Folders that will be written to later */
define( 'IPS_FOLDER_PERMISSION', 0777 );

/* Folders that will be created and not written to later */
define( 'FOLDER_PERMISSION_NO_WRITE', 0755 );

/* Files that will be written, and then later deleted or overwritten */
define( 'IPS_FILE_PERMISSION', 0666 );

/* Files that will be written once, and would not later be updated or deleted */
define( 'FILE_PERMISSION_NO_WRITE', 0644 );

But I still don't understand and how to solve it, and I can't support it with invision, even though I have an active license, they say they only support the forum and right now I'm having trouble getting into their forum.

Has anyone seen this problem before?

 

[Sebahat.hadzhi]

Hello, @NITROFOX . The recommended permissions are 755 for directories and 644 for files. What you can try is to adjust the code to:

/* Folders that will be written to later */
define( 'IPS_FOLDER_PERMISSION', 0755 );

/* Folders that will be created and not written to later */
define( 'FOLDER_PERMISSION_NO_WRITE', 0755 );

/* Files that will be written, and then later deleted or overwritten */
define( 'IPS_FILE_PERMISSION', 0644 );

/* Files that will be written once, and would not later be updated or deleted */
define( 'FILE_PERMISSION_NO_WRITE', 0644 );

However, I cannot guarantee the more restrictive permissions won't cause an issue with Invision community.

 

[NITROFOX]

Hello, @NITROFOX . The recommended permissions are 755 for directories and 644 for files. What you can try is to adjust the code to:

/* Folders that will be written to later */
define( 'IPS_FOLDER_PERMISSION', 0755 );

/* Folders that will be created and not written to later */
define( 'FOLDER_PERMISSION_NO_WRITE', 0755 );

/* Files that will be written, and then later deleted or overwritten */
define( 'IPS_FILE_PERMISSION', 0644 );

/* Files that will be written once, and would not later be updated or deleted */
define( 'FILE_PERMISSION_NO_WRITE', 0644 );

However, I cannot guarantee the more restrictive permissions won't cause an issue with Invision community.

Thank you, I'll try!