MacOS – Can OS X users get locked on OS X similar to on ubuntu when using git

gitmacospermission

I have gitlab connected to my mac but when I do git push -u origin master I get 'Permission denied. Please try later' message which is what pops up when the user gets locked it seems.

But here in this post users have used usermod in linux to unlock the user. I need to do something similar. Or if there is any other solution

Best Answer

I just had to delete the entry from known_hosts file on my MAC(client) to remove the traces of old config for that particular gitlab server. And also I regenerated my ssh keys back which seemed to work! :)

I used githubs awesome article to regenerate the ssh-keys.

Related Solutions

MacOS – Problems saving changes to /etc/sshd_config

Using sudo on the open command doesn't do anything particularly useful -- the actual program still gets run under the user's regular identity. To solve this, make sure TextEdit isn't running, then do:

sudo /Applications/TextEdit.app/Contents/MacOS/TextEdit &
open -a "TextEdit" /etc/sshd_config

The first command runs TextEdit as root; the second tells it to open the file. After this, you should be able to edit & save changes. When you're done, be sure to quit TextEdit (or it'll keep editing files as root).

Alternately, use TextWrangler (or its even-more-capable-but-not-free sibling, BBEdit). It handles saving files as root automatically, as well as having easy ways to edit invisible files. I much prefer it for editing config files and the like.

EDIT: Be sure to get the version of TextWrangler from the Bare Bones Software web site, not the version from the Mac App Store -- the App Store version has the save-as-root feature removed to comply with Apple's rules.

Why is Keychain behaving erratically

Sounds like this was due to them creating a new user (502) and naming it the same as the old user, and copying all your old files in. The problem is that the new user account ID doesn't match the old user ID. What needed to be done was a chown -R 502 on your whole user directory. Too bad you started afresh. Sidenote: Trying to restore in this fashion almost never works well. Wipe the disk, re-install a good OS, and then restore from a TM or other backup if available. I've never had a problem using that method, but I've definitely had problems using the method you describe. Better luck next time.

Best Answer

Related Solutions

MacOS – Problems saving changes to /etc/sshd_config

Why is Keychain behaving erratically

Related Question