Heroku and facebook - cannot even clone my application to start working - facebook

Recently I've started working on a facebook app using Heroku and their tutorial is really extensive on the matter. However, when trying to clone my application to my machine, i get the following error:
Permission denied (publickey)
fatal: The remote end hung up unexpectedly
I tried every solution I could find, resetting my key, uploading a new one, editting the key archive, but none of them seemed to solve my problem.
Does anyone have a different alternative to this?
Thanks
Im running Windows 7 Enterprise and my application is set to run on PHP.

Wherever you hold your keys try
heroku keys:add
Without an argument, it will look for the key in the default place (~/.ssh/id_rsa.pub or ~/.ssh/id_dsa.pub). If you wish to use an alternate key file, specify it as an argument. Be certain you specify the public part of the key (the file ending in .pub). The private part of the key should never be transmitted to any third party, ever.
https://devcenter.heroku.com/articles/keys

just wondering if you are Starting Command Prompt with Ruby? I had some problems with this aswell double check your ssh

Related

Github still asking for credentials despite successful creation of deploy key?

I have created a deploy key according to the windows instructions here
But instead of using the deploy key that has just been set up, git push instead asks for credentials, first with a pop up, then with an SSH pop up, then in the git bash command line itself! This is quite shocking because the whole purpose of a deploy key is to avoid having to provide access to an entire github account
Given I have followed github's own instructions precisely and this isn't working, I am lost as to what to do next.
Notes
Some time ago, somehow, I set up a deploy key successfully on the same (windows) server. So perhaps the > 1 key on the machine is confusing some part of the process. I am not sure this has anything to do with it though.
I can see here that github expects keys to be named id_rsa and id_rsa.pub, but given this is my second deploy key running on this particular server, I named the second set differently so as to avoid overwriting the original set (the original set are still there, there are just two more files in C:\Users\[YOUR-USER-NAME]\.ssh\)

VSCode Remote Server stuck on initializing server

I'm currently trying to access a remote server using VS Code's Remote SSH extension. I haven't had a problem when using it before (that was around a month ago) but today when I tried to access the server I ran into some trouble.
I have the hostname and everything configured in a config file, and so I just click on that option and type in the password. However, VS Code seems to be stuck on "Opening Remote..." for the past hour or so. The dialogue I get in the terminal is as follows:
username#host's password:
Running remote connection script
Acquiring lock on /home/username/.vscode-server/bin/abcdefghijklmnop1234567989/
vscode-remote-lock.abcdefghijklmnop1234567989
Installing to /home/username/.vscode-server/bin/abcdefghijklmnop1234567989...
Downloading with wget
Does anybody know what the problem might be? Is this normal?
EDIT
As soon as I posted this the connection was successfully made. However, I would also like to still know what the problem was and if it normally takes around an hour, and what this process might be doing. I also believe it would be helpful to the community overall.
Thank you.
I've faced the same issue just now and realized that firewall protection has something to do with it.
As soon as I disabled it, the remote connection was established and I managed to see my code again.

How to ssh with Amonite supplying the password in advance

Problem: I need to access a command line API on a Remote machine.
I am playing with Scala Amonite libs, i wonder if there is a way to ssh and supply the password, so that i can do it from within an application and not have to enter the pass in the middle of it.
It's best to use public key authentication not passwords. It's a best practice regardless, & solves your problem of ssh from inside a script without having to provide a password.

Unable to connect to my GAE account through appcfg

I was surprized not to be able to connect to my account through appcfg my password was right, butthe app ansered it's not.
When I change the google setting : https://www.google.com/settings/security/lesssecureapps to make Access for less secure apps enabled, it worked.
Is there something I'm missing or must i have this security hole open to be able to use appcfg?
Please notice I'm using eclipse to publish my apps, and the eclipse plugin connects with even if the accont security is safe, but calling appcfg from the command line for roll back was the operation that failed...
I thought eclipse uses the command line to upload my app? I'm obviously wrong.
So the question is: is there something I have to do to be able to have Access for less secure apps disabled and use appcfg ?
Workaround is to use an OAuth2 token instead of using password based authentication.It is more convenient.
just add the option --oauth2 before the update, you get a key which you paste in for appcfg
I recommend you to try uploading your GAE app from the command line by:
Open CMD
Going to the GAE \ BIN directory
Enter the following command:
appcfg.exe update PATH_YOUR_APP_WAR
After that you will be required to enter your GAE email address and password, that's it

GitLab - Cannot push or pull. It seems to be a permission issue

Hope someone will be be able to help: I've installed GitLab and for a few days it seems that worked ok (I could push and pull only from a client but not from the machine that runs GitLab itself), however that's no longer the case. I have been working on the server (its my own server that I've setup for development/learning/personal stuff but I don't believe I've changed anything that could affect Gitlab, so I'm don't know what to do.
At the moment I can't push or pull from either my local machine (OS X 10.8.3) not from my server (Ubuntu 12.0.4). I've run the test several times and all is green. When I do git config user.name or git config user.email it comes back with my name and email respectively. I've also searched online but couldn't find anyone in exactly the same situation, however I did try many of the approaches suggested: I've deleted and generated more ssh keys, changed config in /home/git/gitlab/config.yml to reflect my setup (I'm running apache). My GitLab is 5.2 and I've followed the instruction on GitLab's homepage. In order to make it working with apache instead of nginx I've followed the instructions here:. This question seems the closest to describe my problem, however the solution is not clearly described, so I couldn't follow. The web ineterface works fine and I can commit either from my local machine (using sshfs) and my server. I just can't push or pull. The error I get is:
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
I'd appreciate any help. I've been struggling with this for days now and I'm on the brink of give GitLab up...
Many thanks
EDIT: On my server I've got three accounts: user1 (main, first user, root), user2 a sudoer that also has admin privileges and git which also is a sudoer. After more investigating, I'm pretty sure this is a problem of me messing up with permission and the ssh key. Can someone point me out: when I generate the ssh key, which user should I be logged in as? In which computer should I generate this key? On my server or my Mac? Also, when I've tried push from my server directly (I was physically logged in the server rather than sshed to server via my Mac) GitLab was asking for git's password. I then generated a key logged as git on the server and added to GitLab through the web interface and the error appeared again (the same as before). Still not fixed.
The problem in my case was that I changed the git credentials on my local machine (when you create a new repo, you set the user name and email Git and git#localhost respectively) that I had changed and didn't realise. That's why every time I was trying to either push or pull I got the error. Once that was changed back to the correct settings, Gitlab started working again. Leaving as it might be helpful to someone.