backup directory is NOT writable

  • WARNING: Your backup directory is NOT writable! We can not create the backup directory.
    /home/username/public_html/

    I noticed that ever since I change host, my blog can be backup haven’t been writable at 755. I still have a copy of the site on another host’s server and the back up can write at 755. I also noticed that when I made the folder to 777, the back up work on the new host’s server. I wonder what might be causing that problem? Isn’t changing a folder to 777 dangerous and let other people write in it?

Viewing 3 replies - 1 through 3 (of 3 total)

  • Best bet would be to contact your host as that’s really a question for them as we don’t have access to your box.

    For some reason the backup directory has changed from wp-content/backup/ to wp-content/backup-XXXXXX (with XXX stands for some random numbers).

    What helped me was to rename backup-XXXXXX to backup-XXXXXX-old and then creating a new directory with the old name (backup-XXXXXX).

    Sure, it would have been much easier to delete the old backup directory, but for some reason I wasn’t allowed to do so. Not a big deal, since this directory was empty anyway. I suppose all these problems result from the backup-plugin?

    I’m interested in this same information. If I did a temporary change to 777 so I could set the backup to provide a regular weekly backup, and then changed back to 755 would it then still operate or does that stop it?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘backup directory is NOT writable’ is closed to new replies.