FTP credentials don't allow to write to file – Continuous notification

  • gr33nman

    (@gr33nman)


    10 years, 10 months ago

    All wordpress configurations are up-to-date and current.

    I’m getting this message now from W3 Total Cache

    FTP credentials don’t allow to write to file /home/myname/mysite.com/.htaccess

    W3 Total Cache Error: Files and directories could not be automatically created to complete the installation.
    Please execute commands manually
    or use FTP form to allow W3 Total Cache make it automatically.

    There’s an image, linked below. Regardless of whether I manually add in the content as directed to my .htaccess file or not, I get this message. I wonder if it may be conflicting with BulletProof Security, but cannot be sure, since other people are having similar problems and may not also have BPS.

    http://www.flickr.com/photos/71276004@N04/sets/72157634212351379/with/9084543975/

    http://wordpress.org/extend/plugins/w3-total-cache/

Viewing 6 replies - 1 through 6 (of 6 total)
  • scoobydooo9r

    (@scoobydooo9r)

    10 years, 9 months ago

    I am having the same problem, and it seems like it started right after I upgraded BPS. The problem goes away if I put BPS in default mode. I can’t be entirely sure that it is BPS, but it sure seems like it is the cause.

    BuyManThings

    (@buymanthings)

    10 years, 9 months ago

    I would definitely say it’s your Bulletproof Security settings. This is also applicable to WP Better Security.

    There is a setting/tweak related to removing write permissions from .htaccess and wp-config.php, turn that off and you should be good to go.

    http://http://buymanthings.com/

    AITpro

    (@aitpro)

    10 years, 9 months ago

    BPS has a lock and unlock root .htaccess file buttons on the BPS Edit/Upload/Download Tab page. If you would like to let another plugin write to your .htaccess file and it is locked you would need to unlock it to allow the other plugin to write its htaccess code to the root .htaccess file.

    There was a previous issue with the BPS AutoLock and file permissions checks during upgrade auto-updating that was fixed in BPS .48.9. What was occurring is that the root .htaccess file permission was being cached so the check whether to automatically lock the root .htaccess file again after the auto-update completed was failing. So now that it is working correctly you would need to choose Turn AutoLock On or Turn AutoLock Off on the BPS Edit/Upload/Download page. Most hosts allow you to lock your root .htaccess file with 404 Read-Only permissions, but a few do not. If you lock your root .htaccess file and your website crashes you will need to FTP to your website and change the permissions of the root .htaccess file from 404 to 644 file permisssions.

    AITpro

    (@aitpro)

    10 years, 9 months ago

    Typo/correction made above: had 403 on the brain. changed “403” to 404 above. 😉

    mbrighton

    (@mbrighton)

    10 years, 9 months ago

    Thanks for info. Yes, I did what AIT Pro said with Bulletproof security and it worked to fix WP3cache.

    Thread Starter gr33nman

    (@gr33nman)

    10 years, 8 months ago

    I’ve removed the lock on BPS. This part of W3TC works properly now. Thank you.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘FTP credentials don't allow to write to file – Continuous notification’ is closed to new replies.