Skip to main content

htaccess file is wiped out after running pkgacct

Optimizr
I am running a custom script for the backup schedule and transportation but the backup is handled by /scripts/pkgacct. I am having strange error that every time the schedule backup has ran, the htaccess file of a lo of sites are emptied. They all became 0kb. So I went ahead to check /scripts/pkgacct file and I found following block [CODE=perl]If the server is running EasyApache4, it may have added some clauses into vhosts' .htaccess files, which we want to strip out. The target server could be an EasyApache3 host, and won't have the same handlers set, or could be an EasyApache4 host, but may not have the same set of PHPs installed, and our PHP handler could very well cause the vhost to simply stop serving pages. Since we're using Archive::Tar::Builder to create the tar, and we can do any sort of mapping that we like, we'll copy our .htaccess files into the work directory, change their names, and return the remapping. The caller will need to alter the mapping, to send things into the $workdir/homedir tree, but this should be simple. If the server is not running EasyApache4, we will return without performing any action.
I am using EA4. I am mostly running WordPress sites and thus .htaccess file are needed with at least WordPress's default. For now, I run a script that find 0kb htaccess file and put the WordPress's default configurations back after the backup script. But this is unneeded extra step. Please tell me how can I fix this issue.

Comments

10 comments

Date Votes
  • andrew.n
    Make sure the htaccess files has the correct permissions and ownerships which in most of the cases causing the problem.
    0
  • Optimizr
    Make sure the htaccess files has the correct permissions and ownerships which in most of the cases causing the problem.

    Both of them are correct. Permission is 666 and the owner is the respective cPanel user. Any other possible reason?
    0
  • andrew.n
    @cPRex ? @Optimizr can you paste here or attach the full backup logs? so we can see what else it can be.
    0
  • George_Fusioned
    chmod 666 means that all users can read/write this file. The proper permissions are 644 for files, 755 for folders. You can perform a bulk change of permissions by running the following while in the public_html
    folder. find . -type d -exec chmod 0755 {} \; find . -type f -exec chmod 0644 {} \;
    (that said, I don't know why having the "wrong" permissions would empty your .htaccess file, so yeah definitely something that the cPanel techs need to take a closer look)
    0
  • cPRex Jurassic Moderator
    I haven't experienced this issue on my end. Could you provide us with a copy of the data in one of the .htaccess files that is being overwritten so I can do some testing with that on my side?
    0
  • Optimizr
    @Optimizr can you paste here or attach the full backup logs? so we can see what else it can be.

    I am sorry I am redirecting the log to > /dev/null 2>&1;
    since it has been running fine for a long time.
    0
  • Optimizr
    chmod 666 means that all users can read/write this file. The proper permissions are 644 for files, 755 for folders. You can perform a bulk change of permissions by running the following while in the public_html
    folder. find . -type d -exec chmod 0755 {} \; find . -type f -exec chmod 0644 {} \;
    (that said, I don't know why having the "wrong" permissions would empty your .htaccess file, so yeah definitely something that the cPanel techs need to take a closer look)

    Thank you for pointing out. When @andrew.n mentioned this I just had a quick check on other working file and they are also at 666 permission. That's why I though 666 was intentional for htaccess (although I know 644 is recommended for files). I will run a quick fix for all those htaccess file and will get back with the outcome. My backup is running on alternate days. Therefore, forgive me if my reply is taking a while.
    0
  • andrew.n
    Nice, keep us updated!
    0
  • Optimizr
    Looks like fixing the permission of .htaccess did the magic. I only have one emptied .htaccess file today which I must have left out while fixing the permission. Thank you all for your helps. Have a good day ahead!
    0
  • andrew.n
    Glad to hear!
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post