Can't Push

Hi,

Can you try via the HTTPS authentication method and see if that works?
https://docs.revisr.io/article/13-remote-settings

I’m not sure if this is how it’s set up for all Bitnami hosting accounts, but I believe there was another user who had a similar issue and it turned out to be that the user running Apache (daemon) doesn’t have access to your user’s SSH keys.

Actually, I left out that I tried HTTPS first.

This is actually a Bitnami image on an AWS Instance. So I control the instance completely.

The HTTPS method had the same problem.

The keys authenticated with Github successfully.

Hi,

I tried putting in the HTTPS version. It failed, but the error detail was different.

To https://[username}:[password]@github.com/[organization]/[directory]
! [rejected] HEAD -> master (non-fast-forward)
error: failed to push some refs to ‘https://[username}:[password]@github.com/[organization]/[directory]’
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: ‘git pull …’) before pushing again.
hint: See the ‘Note about fast-forwards’ in ‘git push –help’ for details.

I don’t think this fixed the SSH problem, and file permissions still reads as “false”.

Maybe it sheds some light on the problem for you.

Acted on the hint above to do a ‘git pull’

Still failed. This is the error detail.

error: unable to create directory for .git/logs/refs/remotes/origin/master

Seems like this is a file permissions problem. I don’t get it though the .git directory is set to 777 note even 775.

The .git directory is in the same level as the index.php for the wordpress site.

Some headway. I was able to use the ‘git pull’ from the command line. This seems to have the local at the right point now. When I went into Revisr it read the push, so the HTTPS seems to be working. That resolves the remote.

This is from the dashboard. “Successfully pushed 2 commits to origin/master.“

However, when I tried to do a commit from Revisr, I got an error that it can’t write to the local. This is the error.

There was an error committing the files. Make sure that your Git username and email is set, and that Revisr has write permissions to the “.git” directory.

I did a “git config –global” on the username and email, and it still gets the same error.

What do you think is wrong with the permissions to write?

I added: define( ‘REVISR_GIT_PATH’, ‘/usr/bin/git’ ); to the wp-config.php already. Then I restarted Apace. Do I need to do something to WordPress to get it to read the config change?

I’ve continued to fiddle with this.

I have about 20 files staged, but when I try to commit. I get on the commit page:

There was an error committing the files. Make sure that your Git username and email is set, and that Revisr has write permissions to the “.git” directory.

On the dashboard the event reads:
Error committing the changes to the local repository.

Your help is appreciated.

What permission is lacking a group permission or something? The directory where the repo is located has write permissions set.

Any thoughts?

Hi,

Revisr checks for write permissions to both the .git directory, and the .git/config file. If either of those checks fail, it will register as “false” on the debug page as it seems to be doing for you.

If you set permissions recursively on the .git folder for 755 on directories, and 644 on files, that should be enough to work as long as the user running apache owns those files or is part of a group that has permissions.

You can run a quick “<?php echo exec( ‘whoami’ ); ?>” on the server to see who the files need to be owned by.

I made sure about the config file. I tried the commit, and it still failed.

This is what comes out in the error detail.

Unable to create ‘/[path]/.git/index.lock’: Permission denied

The whoami you suggested retrieved “daemon”

root owns the config file

Yes, definitely permissions then.

Are you running as root when using Git manually? I wonder if doing that may be overwriting any permissions changes that you’ve been making.

Aside from that, I’d that you chown the files to the correct user/group. It sounds like the files have the right numerical permissions, but being owned by root and run by daemon they’re still not writeable by the server.

Changed the permissions to the same as the rest of the wordpress install bitnami:daemon, but alas that’s not the answer. Getting the same error and the help screen still says false on permissions.

Do you get this any other time on AWS? Do I need to create one of these index.lock files manually?

Any other ideas?

You can create the index.lock file manually, but I don’t think that will fix the cause of your issue.

Going back through the threads, I see there was one user who was having permissions issues on a Bitnami AWS instance and was able to resolve them by setting permissions recursively on the “.git” directory to 775 for directories, and 665 for files. He also had the files in the bitnami:daemon grouping.

This is different and a little more permissive than what I recommended above (755 for directories and 644 for files), so that may be worth a try to see if that fixes the issue.

Failing that, there’s not much else I could do or recommend without having access to the server to troubleshoot further. If that’s something you’d be interested in, feel free to email [email protected] so we can look into this further.

Thank you.