failure to push to heroku on git deploying node server - node.js

Im using heroku for testing a server I have followed other examples about this but I keep getting the same error that I dont see anywhere. I have even tried deleting my repo and my heroku app and starting again but i get the same error when using
git push heroku master.
$ git push heroku master
fatal: unable to access 'https://git.heroku.com/football-app-development.git/': Could not resolve host: git.heroku.com
`
$ cat .git/config
[core]
repositoryformatversion = 0
filemode = false
bare = false
logallrefupdates = true
symlinks = false
ignorecase = true
hideDotFiles = dotGitOnly
[remote "heroku"]
url = https://git.heroku.com/football-app-development.git
fetch = +refs/heads/*:refs/remotes/heroku/*
`
Any help would be great!

If anyone else has this issue I got it to work by uninstall got and the heroku tool belt and install both again.

Related

Beginning with Heroku. Problem with authetication

I'm noob in git/heroku etc. I work according to the tutorial https://devcenter.heroku.com/articles/getting-started-with-nodejs#deploy-the-app .
I run commands in cmd:
heroku login
cd node-js-getting-started
heroku create (runned in past)
heroku auth:token
git push heroku master
After last command possibly window show where I put username "" and password heroku token that I get.
But after, this is displayed:
C:\Users\Administrátor\node-js-getting-started>git push heroku master
git: 'credential-managerd' is not a git command. See 'git --help'.
The most similar command is
credential-manager
remote: ! WARNING:
remote: ! Do not authenticate with username and password using git.
remote: ! Run `heroku login` to update your credentials, then retry the git command.
remote: ! See documentation for details: https://devcenter.heroku.com/articles/git#http-git-authentication
fatal: Authentication failed for 'https://git.heroku.com/afternoon-fjord-61446.git/'
I'm really don't know what I should do now.
I finally solved it.
I changed my .gitconfig file from default
[credential]
helper = managerd
to
[credential]
helper = manager
and I used username "blank" instead "" (empty string) and its working.

fatal: 'user/test.git' does not appear to be a git repository

I created a repo in gitlab and set the user.name in a global way.
When I try to push my project, after inserting my password, I get the following error:
fatal: 'user/test.git' 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.
My .git/config:
[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
[remote "origin"]
url = git#gitlab.domain.tld:user/test.git
fetch = +refs/heads/*:refs/remotes/origin/*
output from "git remote -v:
origin git#gitlab.domain.tld:user/test.git (fetch)
origin git#gitlab.domain.tld:user/test.git (push)
What could be the problem?
Try using this:
git push https://username:password#gitlab.com/user/test.git
I've seen some issues in the newer versions of git that give me trouble when I don't specify the username and password every time. I'm sure there's a way around it but I haven't figured it out yet. Git recommends rolling back to older versions, but I'm sure there is a less drastic way.
In Settings you want to add with
git push https://yourusername:yourpassword#gitlab.com/user/test.git

Heroku reports "no app specified" on Windows command line

I have a node.js application running on Heroku. I've used the (Windows) command line to initialize the app with heroku create, and I can hit the production website and see that it's running correctly. All's good.
But when I try to run simple commands, like heroku ps, from the directory in which the app lives, Heroku responds with a "no app specified" error:
C:\dev\iq>heroku ps
! No app specified.
! Run this command from an app folder or specify which app to use with --app APP.
I've read in other posts that you can avoid having to use the --app APP syntax with every command if you configure git like so:
git config heroku.remote heroku
However, after doing so, Heroku still complains that the app wasn't specified for simple command line requests. I've verified that .git/config has been updated appropriately:
C:\dev\iq>type .git\config
[core]
repositoryformatversion = 0
filemode = false
bare = false
logallrefupdates = true
symlinks = false
ignorecase = true
hideDotFiles = dotGitOnly
[remote "heroku"]
url = git#heroku.com:aqueous-mountain-xxxx.git
fetch = +refs/heads/*:refs/remotes/heroku/*
[heroku]
remote = heroku
I've just reinstalled the latest version of Heroku:
C:\dev\iq>heroku --version
heroku/toolbelt/3.2.2 (i386-mingw32) ruby/1.9.3
What am I missing?
The 'heroku' command requires the '--app' parameter to target a given application, unless you run it from a application folder (clone of the Git repo containing your application).
From my experience, this error occurs when the code is not pushed to heroku (git push heroku master) before running heroku ps.

System ask password when push project to github

I setup gitlab on Centos 6x . Webserver : nginx .
I installed my gitlab follow link .
And i have a problem : when i push my project on client to gitlab#mydomain.com , system ask password :
git push -u origin master
git#gitlab.mydomain.com's password:
Then i show config file of my project on client :
cat ../.git/config
[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
[branch "master"]
[remote "origin"]
url = git#gitlab.mydomain.com:myusename/myproject.git
fetch = +refs/heads/*:refs/remotes/origin/*
System showed log When i check :
bundle exec rake gitlab:check RAILS_ENV=production
/usr/local/lib/ruby/gems/2.0.0/gems/bundler-1.3.5/lib/bundler/runtime.rb:216: warning: Insecure world writable dir /usr/bin in PATH, mode 040777
/usr/local/lib/ruby/gems/2.0.0/gems/bundler-1.3.5/lib/bundler/runtime.rb:216: warning: Insecure world writable dir /usr/bin in PATH, mode 040777
Checking Environment ...
..
..
I want to turn off the password requirement .
Some body help me , thanks a lot .
I assume you have checked you public keys are valid and installed on client and server/gitlab and that ssh is working with public keys for another user on that machine.
Have you checked file permissions on the git users ~/.ssh directory (should be 700) and ~/.ssh/authorised_keys (600).
Also is selinux enabled? You may have an issue with security contexts - see https://serverfault.com/a/564824/204206

Private Git repo - freezes at pulling

I just setup git on my linux server and configured SSH - I want to create private repository to work with my friends. When I'm pulling or cloning that repo everything works fine (LAN), but when my friend tries pull or clone it (over Internet),
git hangs at:
remote: Compressing objects: x
where x is always lower than 17%.
What's wrong with it or how could I fix it?
PS: I not using gitosis, I initialized that remote repo with: git --bare init.
Thanks in advance.
Update:
The results commands:
$ cat .git/config
[core]
repositoryformatversion = 0
filemode = false
bare = false
logallrefupdates = true
symlinks = false
ignorecase = true
hideDotFiles = dotGitOnly
[remote "origin"]
url = ssh://git#server:port/~/repo_name.git
fetch = +refs/heads/*:refs/remotes/origin/*
$ git fetch -v
Enter passphare for key '/c/Users/dev/.ssh/id_rsa':
remote: Counting objects: 76, done.
remote: Compressing objects: 21% (12/55)
However, when my friend got ZIP with sources and he pushed it, everything worked fine.
So he is able to push. I added an empty file and pushed it, he successfully downloaded (pulled) it.
Get your friend to try:
git fetch -v
If that doesn't give you the answer then get him to do this:
cat .git/config
If your server is secure then update your question to include the output of that command. If it's not secure then change the IP and other identifying details to a fake IP and fake details, but try not to alter anything else as you may end up providing misleading info.
Edit based on update:
The url should start with "ssh://" not "ssh/". Although I'm about to go double check that.
If Git push/pull freeze using a config that previously worked, try restarting the computer.
It sounds strange yet I have experienced this on Windows and Linux.
I had the same problem until I went into my Ethernet adapter settings and changed the Jumbo Packet size from 1514 bytes to 9014 bytes.

Resources