• I keep seeing error

    Unable to write to your .htaccess or nginx.conf file. If the problem persists contact support.

    the log file is simply the header information so no information on what is causing it.

    I am on a Amazon hosted system, so this may be the cause, it would be useful if the output would tell me what changes are required to the .htaccess then I can manually update as required ?

    https://www.ads-software.com/plugins/better-wp-security/

Viewing 15 replies - 46 through 60 (of 61 total)
  • UPDATE: “Disable file locking” only worked to make it SEEM like backups were running. iThemes Security’s backup features are still not working on my 3 sites, even after WP 3.9 updates — 2 on different DreamHost accounts and one on GoDaddy. Closest they come are emails claiming that backups are attached but with zero attachments.

    iThemes Security’s other features are still super-useful, so I’ve disabled its malfunctioning backup settings and installed “UpdraftPlus – WordPress Backup and Restoration” which works like a charm sending scheduled backups — not just of the database but of the entire site if I so choose!

    https://www.ads-software.com/plugins/updraftplus/

    I had the same issue. Tried Wombat’s first solution (delete htacess, delete iThemes, reinstall) which didn’t work.

    His second fix “disable file locking” seemed to work, but sent me an empty email. Probably going to use a different plugin. What a shame.

    Evertytime I make a change to the plugin settings and then try to save I get the same message:

    WordPress was unable to save the your options to .htaccess or nginx.conf file. It looks like another process might already be working on the file. Please wait a few minutes and try again or contact support if the problem persists.

    Also, my first login attempt always fails!! Always! It’s becoming very annoying.

    I have the same problem. Thanks for the suggestions for fixing this, but they’re not working. It’s frustrating because I rely on error messages to resolve problems like these, and when iThemes reports that nginx.conf couldn’t be written, that’s less than helpful. The file exists and is chmod 777.

    An update was just released for iThemes, but it does not address this issue…

    I am happy to pay for premium plugins, but it seems that many of us have this core problem, that even with updates, goes unresolved. Makes me MUCH less likely to pay for the plugin unless this is addressed.

    Well, we’re now at Vn. 4.1.5 and the problem is STILL there. I find this very discouraging. I just created a new WP site, everything virgin, iTS the only plugin, the first I do is hide the admin user – works fine – and the second I do is to rename the wp-content directory. Same old problem: Unable to write to your .htaccess or nginx.conf file.

    The symptom remains, that .htaccess mtime gets updated but not the content. And yes, I have disabled file locking. All to no avail.

    Hosting details: Ubuntu 12.04 LTS with Plesk 11.5, using mod_fcgid – could there be a problem here with FastCGI???

    There is a repeated error in my PHP error log: mod_fcgid: stderr: PHP Warning: mb_strpos(): Empty delimiter in /var/www/vhosts/{hidden}/plugins/better-wp-security/core/class-itsec-files.php on line 1196, referer: {hidden}/wp-admin/plugins.php?deleted=true&plugin_status=all&paged=1&s=

    But that goes away when I remove “mbstring.func_overload = 7” from the php.ini. Otherwise all default php settings in Plesk.

    Only real solution seems to be to turn Global Settings | Write to Files off and manually edit .htaccess und wp-config.php.

    Chris, can’t you DO something – this is getting beyond a joke…

    AHA – now it’s writing .htaccess and wp-config.php

    What did I change? Enabled Permalinks.

    I can hardly believe that that’s causing the problem, but maybe it really is – and IF it is, then we need a more specific error message, like “Unable to write to your .htaccess or nginx.conf file – please activate Permalinks in your WordPress Settings”.

    I checked that – re-enabled permalinks, and still get the error.

    I have a possible SOLUTION for you guys! After much trial and error, the plugin magically started working correctly and wrote to my nginx.conf without issue.

    I changed the “NGINX Conf File” in the plugin’s settings to a new, blank file. The plugin immediately began writing to the new file, so I reverted the field back to the nginx.conf path and all was well.

    No idea what caused this, but it’s probably some kind of bug. I hope this fixes it for you guys.

    I have a similar problem. the message I receive is:

    Unable to write to your .htaccess or nginx.conf file. If the problem persists contact support.

    The file path entered does not appear to be valid. Please ensure it exists and that WordPress can write to it.

    where is nginx.conf file? I can not locate it?

    BTW I also have another access or ownership problem with wp-content directory which I have posted here:
    https://www.ads-software.com/support/topic/unable-to-upload-pictures-6

    Unable to write to your .htaccess or nginx.conf file. If the problem persists contact support.

    When I try to save a backup… help?
    Hasnt this issue been solved after two months. Hmm.

    Im using the latest version, please advice; thank you.

    Can’t even uninstall iThemes. Permission denied.
    Nor new plugins can be installed.
    I think one should stay away from iTheme security.At least until it is resolved.

    Hmm. Last post 2 months ago…

    Is there a solution yet?

    Here’s another question: went to download my wp-content file via FTP and cannot. Same message error every time, for every item in the file:
    Error: Failed to open “/wp-***.php” for writing
    Error: File transfer failed
    I have verfied with the server that this is not a server issue. Have made every correction mentioned and still nothing works! Would love to know if ANYONE has a suggestion as I need to migrate this site and domain to another server. Have database backups (made with iThemes so who knows whether they will work!) but no content backup.

    Don’t know if this helps anyone, but encountering the error with a brand new install, Ubuntu Server 10.x. I tried changing the permissions via ftp to 644, and still no luck. SSH into the server and used root to change to 664 and that fixed the error. Will leave like that a bit, once I’ve configured it, then change back to 644.

Viewing 15 replies - 46 through 60 (of 61 total)
  • The topic ‘Unable to write to your .htaccess or nginx.conf file.’ is closed to new replies.