I have added a key also.
I tried adding username and password in url as: root:password#ssh://10.10.14.119//home/pk/user_app.git.
I tried making file containing login and password and added that from windows 10 cmd prompt.
Nothing is working. Its asking password for every push and pull
Thanks all for your responses.
Finally I got the answer.
I used the global key (id_rsa.ppk) of my git server and its working very well now.
Related
I have Tortoisehg set up with a clone of a remote repository on Bitbucket, using https protocol. I turned on the mercurial_keyring extension, and it took care of password handling just fine. Until one day it didn't. Every time I commit now, on push-after-commit it pops up and asks me for a password.
I carefully changed the password on the server, and started typing in that password when asked. IT DOESN'T HELP! It doesn't accept that password.
I hit cancel when asked for the password. Then I go and press the Push green arrow button at the top right of the screen. After asking for confirmation – IT GOES! No password required!
There are three computers that connect to this particular Bitbucket repository. For a while two of the three were working fine without asking a password. Then another one started asking! And then a third popped up asking for something different: "You need to identify yourself to the server." Once again, cancel, use the Push button, works fine!
I am so confused. Has anyone seen this, has anyone fixed it?
BTW, the remote repository is nowhere mentioned in my tortoisehg settings, but it is in my hgrc file:
[paths]
default = https://joymaker3#bitbucket.org/joymaker3/my-repo-name
I yjink, you have to re-read at least section 3.2. "Repository configuration (HTTP)" of extension wiki and check related settings of all repos:
good (full) URL in [paths]
only needed data (if needed) in [auth] (no password for configured remote repository)
you can also enable debug in TortoiseHG and inspect output on failed push
I am using node v0.18.4 on a raspberry pi 3 Jessie. I want to secure the node-red editor, for which i followed the security.html page provided by node red and also I watched a video on youtube. I did the exact same steps, which are:-
1) Go to ~/.node-red/settings.js
2) Uncomment adminAuth
3) Install node-red-admin - sudo npm install -g node-red-admin
4) Generate hash password using, node-red-admin hash-pw
5) Paste the hashed password to adminAuth password field.
6) Save and restart node red
However I do not get the login prompt. The editor just loads without asking me for the username and the password.
I looked it up online, and all I found were httpNodeAuth. I am not trying to secure the UI, I am trying to secure the editor. Also I found a post that said sessions.json file would be written by node-red which was empty when I checked. It said that, it was because on when running node red on images, this file is not writable.
So I even followed the steps to placing the settings.json file to a writable location, and then created a shortcut for it in the node-red folder. This also didn't work out for me.
I also found a post where it said that the hashed password must have a correct format. I got a link to a hash password generator site. I copied the hash password from there but even that didn't result in the login prompt.
Please suggest why I might be getting this problem.
Thanks in advance.
I had somewhat similar problem on PC - asked for login at first, then didn't ask again. Shift with reload didn't change it either.
I did log out, then it asked for password, so you might try that. Also switching from Chrome to IE, I got a login as well.
I am trying to avoid typing the password every time I want to pull or push from a gitlab repository. Therefore I followed https://docs.gitlab.com/ee/ssh/ but still, now every time I want to pull something it still asks me to provide the password for my remote gitlab repository.
Any clue on how to fix this issue?
Are you sure you are using the SSH link for your repository? It is like: git#gitlab.com:YOUR-USER/YOUR PROJECT.git
I am trying out Github for Windows and I am getting the following error when I try to publish a newly created repository.
Authentication failed
Your credentials may be out of date. Please log out of the application and then log back in before retrying the operation.
Needless to say I've logged out and back in multiple times without success. I've also uninstalled and installed the latest version to no avail.
The repository is a new one I created within the application and contains only the .gitattributes, .git and README files.
I am a complete newbie to Github so it's quite possible I've messed something up during the setup process.
I was able to solve this by:
Press Settings - Open in GitShell.
git status
git push (or pull)
introduce credentials (here is the most important step, somehow git client messed up or forgot your credentials).
After giving correct credentials you can exit from git shell and use git client again.
It turns out that the problem was Github for Windows was having a problem with the password it had stored. Github support's instructions were as follows:
Log out of Github for Windows.
Change my password on github.com
Log back into Github for Windows.
I was then able to publish my changes.
Did you setup your ssh keys?
https://help.github.com/articles/generating-ssh-keys#platform-windows
I have this issue, that I have to put this in every time I push or pull. I think this is new. Any ideas?
You are probably using the https url. Switch over to ssh and make sure your keys are setup fine ( and if you have empty pass phrase ) you should not have to enter the username and password.
Did you had this problem before? It most probably means you got something wrong in your public key setup. Make sure to not set a pass phrase while generating your public key. Also, make sure that you first try to login to GitHub using
ssh -T git#github.com
This should work without any passphrase. If it doesn't, check again the setup instructions for the operating system you are using.
Switch from https to ssh - instructions from GitHub's help docs are here.