Title: Can't Push Last modified: August 22, 2016 --- # Can't Push * [edfullman1](https://wordpress.org/support/users/edfullman1/) * (@edfullman1) * [11 years, 1 month ago](https://wordpress.org/support/topic/cant-push/) * Sorry for being dense, but I’m pulling my hair out on this one. * I’m a Git newbie as well 🙁 * This is a brand new WordPress install. * Here is the Help screen Revisr settings. * Operating System Linux Exec() Enabled true Git Install Path /usr/bin/git Git Version git version 1.9.1 MySQL Install Path /opt/bitnami/mysql/bin/mysql File Permissions false Repository Path /opt/bitnami/apps/wordpress/htdocs Repository Status Click here to view. * I installed git and initialized it. * The error I get is: **Error pushing changes to the remote repository.** * Here are the Error Details: **fatal: ‘origin’ does not appear to be a git repository fatal: Could not read from remote repository. * Please make sure you have the correct access rights and the repository exists. * What I’ve done. 1) Installed Revisr 2) Entered the username and email. The same as the Github repository. 3) I have Github with a repo on it with just a Readme. I’ve setup the SSH keys, and tested them per the instructions they work. 4) On the Remote Tab: I left the Remote name as origin. I entered in my SSH from Github: [git@github.com](https://wordpress.org/support/topic/cant-push/git@github.com?output_format=md):[ name]/[directory].git 5) Added: define( ‘REVISR_GIT_PATH’, ‘/usr/bin/git’ ); to the wp-config.php 6) Set the .git directory from 775 to 777 (thinking this might clear the file permissions problem). 7) Tried deleting and reinstalling the Revisr plugin. The data remained, so it didn’t really reset anything. 🙂 8) I committed a change from the command line on the WordPress server to test that repository. * Question: 1) I don’t understand why the file permissions reads “false”. This obviously doesn’t sound good. * [https://wordpress.org/plugins/revisr/](https://wordpress.org/plugins/revisr/) Viewing 15 replies - 1 through 15 (of 15 total) * Plugin Author [Expanded Fronts](https://wordpress.org/support/users/expandedfronts/) * (@expandedfronts) * [11 years, 1 month ago](https://wordpress.org/support/topic/cant-push/#post-5922509) * Hi, * Can you try via the HTTPS authentication method and see if that works? [http://docs.revisr.io/article/13-remote-settings](http://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. * Thread Starter [edfullman1](https://wordpress.org/support/users/edfullman1/) * (@edfullman1) * [11 years, 1 month ago](https://wordpress.org/support/topic/cant-push/#post-5922541) * 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. * Thread Starter [edfullman1](https://wordpress.org/support/users/edfullman1/) * (@edfullman1) * [11 years, 1 month ago](https://wordpress.org/support/topic/cant-push/#post-5922543) * The HTTPS method had the same problem. * The keys authenticated with Github successfully. * Thread Starter [edfullman1](https://wordpress.org/support/users/edfullman1/) * (@edfullman1) * [11 years, 1 month ago](https://wordpress.org/support/topic/cant-push/#post-5922550) * Hi, * I tried putting in the HTTPS version. It failed, but the error detail was different. * To [https://[username](https://[username)}:[password]@github.com/[organization]/[ directory] ! [rejected] HEAD -> master (non-fast-forward) error: failed to push some refs to ‘[https://[username](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. * Thread Starter [edfullman1](https://wordpress.org/support/users/edfullman1/) * (@edfullman1) * [11 years, 1 month ago](https://wordpress.org/support/topic/cant-push/#post-5922553) * 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. * Thread Starter [edfullman1](https://wordpress.org/support/users/edfullman1/) * (@edfullman1) * [11 years, 1 month ago](https://wordpress.org/support/topic/cant-push/#post-5922561) * 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? * Thread Starter [edfullman1](https://wordpress.org/support/users/edfullman1/) * (@edfullman1) * [11 years, 1 month ago](https://wordpress.org/support/topic/cant-push/#post-5922576) * 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. * Thread Starter [edfullman1](https://wordpress.org/support/users/edfullman1/) * (@edfullman1) * [11 years, 1 month ago](https://wordpress.org/support/topic/cant-push/#post-5922702) * What permission is lacking a group permission or something? The directory where the repo is located has write permissions set. * **Any thoughts?** * Plugin Author [Expanded Fronts](https://wordpress.org/support/users/expandedfronts/) * (@expandedfronts) * [11 years, 1 month ago](https://wordpress.org/support/topic/cant-push/#post-5922710) * 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 “” on the server to see who the files need to be owned by. * Thread Starter [edfullman1](https://wordpress.org/support/users/edfullman1/) * (@edfullman1) * [11 years, 1 month ago](https://wordpress.org/support/topic/cant-push/#post-5922721) * 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 * Thread Starter [edfullman1](https://wordpress.org/support/users/edfullman1/) * (@edfullman1) * [11 years, 1 month ago](https://wordpress.org/support/topic/cant-push/#post-5922724) * The whoami you suggested retrieved “daemon” * Thread Starter [edfullman1](https://wordpress.org/support/users/edfullman1/) * (@edfullman1) * [11 years, 1 month ago](https://wordpress.org/support/topic/cant-push/#post-5922725) * root owns the config file * Plugin Author [Expanded Fronts](https://wordpress.org/support/users/expandedfronts/) * (@expandedfronts) * [11 years, 1 month ago](https://wordpress.org/support/topic/cant-push/#post-5922728) * 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](http://www.computerhope.com/unix/uchown.htm) 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. * Thread Starter [edfullman1](https://wordpress.org/support/users/edfullman1/) * (@edfullman1) * [11 years, 1 month ago](https://wordpress.org/support/topic/cant-push/#post-5922730) * 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? * Plugin Author [Expanded Fronts](https://wordpress.org/support/users/expandedfronts/) * (@expandedfronts) * [11 years, 1 month ago](https://wordpress.org/support/topic/cant-push/#post-5922732) * 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 [support@expandedfronts.com](https://wordpress.org/support/topic/cant-push/support@expandedfronts.com?output_format=md) so we can look into this further. * Thank you. Viewing 15 replies - 1 through 15 (of 15 total) The topic ‘Can't Push’ is closed to new replies. * ![](https://s.w.org/plugins/geopattern-icon/revisr_ecf0f1.svg) * [Revisr](https://wordpress.org/plugins/revisr/) * [Frequently Asked Questions](https://wordpress.org/plugins/revisr/#faq) * [Support Threads](https://wordpress.org/support/plugin/revisr/) * [Active Topics](https://wordpress.org/support/plugin/revisr/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/revisr/unresolved/) * [Reviews](https://wordpress.org/support/plugin/revisr/reviews/) * 15 replies * 2 participants * Last reply from: [Expanded Fronts](https://wordpress.org/support/users/expandedfronts/) * Last activity: [11 years, 1 month ago](https://wordpress.org/support/topic/cant-push/#post-5922732) * Status: not resolved