index.lock: permission denied

  • Hi Revisr team,

    Still loving your plugin, even though having a bit of trouble with it right now.

    There were big files under the .git folder. So we had to deinitialize the repo by deleting the .git folder.

    Current error we’re having is:
    ‘fatal: Unable to create ‘/home/drive4evans/public_html/.git/index.lock’: Permission denied’

    This happened after we removed the .git folder to de-initialize the repo.
    Manual git push works but for some reason revisr is no longer working.

    Any ideas?

    Thanks so much

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

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Expanded Fronts

    (@expandedfronts)

    Hi,

    Can you remove the “.git/index.lock” file and see if the issue persists?

    Thread Starter Jon of the Wood

    (@jon-of-the-wood)

    Thanks so much for your help. Actually, I checked in the .git directory and don’t see that file. When my server admin and I were troubleshooting, we may have already removed it.

    What if I just reinstall the plugin? I’m wondering if the two different server environments are causing the problem?

    I tried reinstalling, but it appeared to maintain settings even though I thought WordPress said it would delete everything.

    Is there a way to do a truly clean re-installation?

    Thanks

    Plugin Author Expanded Fronts

    (@expandedfronts)

    Hi,

    That makes sense – rereading this thread with a fresh set of eyes I see that it’s actually failing to create the index.lock in the first place.

    When you deleted and recreated the “.git” folder, did you recreate it manually?

    If pushing works manually but not via Revisr it’s definitely just a permissions issue – I would make sure that the files are owned by the same user as your Apache user and have the correct numerical permissions.

    Failing all that, you could try deleting just the “.git” folder one last time and reinitializing it through Revisr.

    Sorry the permissions, etc. are giving you trouble, but it’s a problem with using the Git installation on your server. This will ultimately be addressed in a later version of the plugin.

    Thread Starter Jon of the Wood

    (@jon-of-the-wood)

    Thanks for your response. Let’s see… some follow up questions…

    1. when you say “I would make sure that the files are owned by the same user as your Apache user and have the correct numerical permissions.” can you clarify which files you’re referring to?
    2. one thing I noticed when examining previously successful commits (from this new server) in Bitbucket is that sometimes user listed in BitBucket was the one associated with the email of the WordPress admin account I was logged in with at the time rather than the one I had specified in the Revisr settings. Any idea why?
    3. I’d really like to try a clean installation of Revisr now that we’re on this new server. I’ve tried to do that through the Plugins menu, but after reinstalling I see that the settings are still there, so it’s not been a completely fresh install. How do I completely get rid of the old install of the plugin?

    thanks so much

    Plugin Author Expanded Fronts

    (@expandedfronts)

    Marking this resolved as it was resolved externally, but please don’t hesitate to let me know if you run into any further issues. Thanks!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘index.lock: permission denied’ is closed to new replies.