if you are writing ->
"git push master Heroku"
and getting error like->
error: src refspec master does not match any.
error: failed to push some refs to ‘git@heroku.com: etc’
then first type in hyper->
git commit -m 'Initial commit'
and then if there is an error like
email ,name is not found or something like that
then it might be possible that you could’nt sign in heroku page.
first write type in hyper commond line or whatever cmd line you are using
git config --global user.email "yourgmail address"
then hit enter then type
git config --global user.name "Your Name"
then it will work fine.
if you want to check that it is working fine then type
git commit -m 'initial commit'
it will take sometime and then write code
git push heroku master
————————-Now everything is solved-TADADAAAA—————————
Note-Please write your email address and username in above code…
I am trying to update the code from my application to my repository and an error appears.
How can I fix it?
C:Sitesecozap>git push heroku master
Enter passphrase for key '/c/Users/Diseño2/.ssh/id_rsa':
Fetching repository, done.
To git@heroku.com:ecozap.git
! [rejected] master -> master (non-fast-forward)
error: failed to push some refs to 'git@heroku.com:ecozap.git'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Merge the remote changes (e.g. 'git pull')
hint: before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.
asked Jan 13, 2014 at 9:40
Antonio MoralesAntonio Morales
1,0442 gold badges16 silver badges34 bronze badges
This error means that the master branch on Heroku contains commits that are not in your local branch.
You can either pull the missing commits from Heroku and merge them into your local copy:
git pull heroku master
Or, if you don’t care about the missing commits you can force push to Heroku. This will overwrite the remote repo on Heroku with your local commits.
git push --force heroku master
Make sure you really don’t care about them as you will lose them from Heroku by doing this. Normally this doesn’t matter as Heroku is not normally the canonical repo, somewhere else such as GitHub is.
answered Jan 13, 2014 at 10:00
Что я делаю:
1. Создал на Github репозитарий и залил туда файлы;
2. Создал ssh ключ и паблик добавил на Github;
3. Добавляю паблик ключ на heroku: heroku keys:add «id_rsa.pub»
3. Копирую репозитарий с Github: git clone git@github.com:Mor/exp.git
4. Перехожу в папку exp.
5. Захожу в heroku: heroku login — ввожу мою почту и пароль;
6. Создаю на хероку приложение: heroku apps:create exp(его также называю как и репозитарий);
7. Пытаюсь выложить на heroku файлы: git push heroku master
Вот тут и начинаются ошибки при выполнении команды «git push heroku master» вылетает ошибка:
error: failed to push some refs to ‘git@heroku.com:exp.git’
При выполнении команды «git pull heroku master»:
fatal: Couldn’t find remote ref master
1. Правильный ли у меня алгоритм действий?
2. Может нужно почистить все и попробывать еще раз?
Git.heroku.com doesn’t appear to be a Gitea server.
You’re pushing from a command line not using Gitea.
I suggest you read the error in your git message and look at heroku.com help pages:
remote: Building source:
remote:
remote: -----> App not compatible with buildpack: https://buildpack-registry.s3.amazonaws.com/buildpacks/heroku/java.tgz
remote: Could not find a pom.xml file! Please check that it exists and is committed to Git.
remote:
remote: More info: https://devcenter.heroku.com/articles/buildpacks#detection-failure
If Gitea is actually involved here somewhere please feel free to reopen but I cannot see the relevance of this issue to Gitea therefore I’m closing this as off-topic
Answer by Jianna Yates
Hello I try to deploy to Heroku but I still accept error code H81 I do git push heroku master and it still doesn’t work.,
Stack Overflow for Teams
Where developers & technologists share private knowledge with coworkers
,Also i do
git commit —allow-empty -m «Trigger deployment»
git push heroku HEAD:master,Thanks for contributing an answer to Stack Overflow!
This is the heroku logs -t
2020-01-21T17:14:25.962640+00:00 heroku[router]: at=info code=H81 desc="Blank app" method=GET
path="/favicon.ico" host=m-markets.herokuapp.com request_id=d9aca2e1-6629-43de-8e16-556d8d38812d
fwd="87.71.26.143" dyno= connect= service= status=502 bytes= protocol=https
2020-01-21T17:19:31.000000+00:00 app[api]: Build started by user [email protected]
2020-01-21T17:20:40.000000+00:00 app[api]: Build failed -- check your build output:
https://dashboard.heroku.com/apps/db636abf-1eaa-4a9d-a7d6-cba4cb98e1d0/activity/builds/2774cb20-2d8d-
4046-ad8c-6d722b2381f8
Angular project server.js file
//Install express server
const express = require('express');
const path = require('path');
const app = express();
// Serve only the static files form the dist directory
app.use(express.static(__dirname + '/dist/m-markets'));
app.get('/*', function (req, res) {
const fullPath = path.join(__dirname + '/dist/m-markets/index.html');
console.log(" Fetching from.." + fullPath);
res.sendFile(fullPath);
})
// Start the app by listening on the default Heroku port
app.listen(process.env.PORT || 8080);
And it gives me
Push rejected, failed to compile Node.js app.
Answer by Jessie Nunez
No code has been pushed to this application. To get rid of this message you need to do one deploy. This is not an error, but we give it a code for the sake of completeness.,
Identities & Authentication
,
Security
App Security
Identities & Authentication
Compliance
,This is not an error, but we give it a code for the sake of completeness. Note the log formatting is the same but without the word “Error”.
A crashed web dyno or a boot timeout on the web dyno will present this error.
2010-10-06T21:51:04-07:00 heroku[web.1]: State changed from down to starting
2010-10-06T21:51:07-07:00 app[web.1]: Starting process with command: `bundle exec rails server -p 22020`
2010-10-06T21:51:09-07:00 app[web.1]: >> Using rails adapter
2010-10-06T21:51:09-07:00 app[web.1]: Missing the Rails 2.3.5 gem. Please `gem install -v=2.3.5 rails`, update your RAILS_GEM_VERSION setting in config/environment.rb for the Rails version you do have installed, or comment out RAILS_GEM_VERSION to use the latest version installed.
2010-10-06T21:51:10-07:00 heroku[web.1]: Process exited
2010-10-06T21:51:12-07:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno= connect= service= status=503 bytes=
When HTTP requests arrive faster than your application can process them, they can form a large backlog on a number of routers. When the backlog on a particular router passes a threshold, the router determines that your application isn’t keeping up with its incoming request volume. You’ll see an H11 error for each incoming request as long as the backlog is over this size. The exact value of this threshold may change depending on various factors, such as the number of dynos in your app, response time for individual requests, and your app’s normal request volume.
2010-10-06T21:51:07-07:00 heroku[router]: at=error code=H11 desc="Backlog too deep" method=GET path="/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno= connect= service= status=503 bytes=
An HTTP request took longer than 30 seconds to complete. In the example below, a Rails app takes 37 seconds to render the page; the HTTP router returns a 503 prior to Rails completing its request cycle, but the Rails process continues and the completion message shows after the router message.
2010-10-06T21:51:07-07:00 app[web.2]: Processing PostController#list (for 75.36.147.245 at 2010-10-06 21:51:07) [GET]
2010-10-06T21:51:08-07:00 app[web.2]: Rendering template within layouts/application
2010-10-06T21:51:19-07:00 app[web.2]: Rendering post/list
2010-10-06T21:51:37-07:00 heroku[router]: at=error code=H12 desc="Request timeout" method=GET path="/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno=web.1 connect=6ms service=30001ms status=503 bytes=0
2010-10-06T21:51:42-07:00 app[web.2]: Completed in 37000ms (View: 27, DB: 21) | 200 OK [http://myapp.heroku.com/]
This error is thrown when a process in your web dyno accepts a connection but then closes the socket without writing anything to it.
2010-10-06T21:51:37-07:00 heroku[router]: at=error code=H13 desc="Connection closed without response" method=GET path="/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno=web.1 connect=3030ms service=9767ms status=503 bytes=0
This is most likely the result of scaling your web dynos down to 0 dynos. To fix it, scale your web dynos to 1 or more dynos:
$ heroku ps:scale web=1
Answer by Barrett Scott
You should git add {file}, git commit -am ‘added {file}’ and then git push heroku master.,When you push your code to Heroku, the build fails with a message like «Failed to detect app matching no buildpack» or «Failed to detect app matching Node.js.»,Engage with a community of passionate experts to get the answers you need,This error message means that Heroku was unable to automatically detect the type of app you’re trying to deploy: Ruby, Node, Python, PHP, Java, etc. We look for signatures for each language we support (like a pom.xml file or package.json file).
- Java: pom.xml
- Ruby: Gemfile
- Node.js: package.json
- Python: requirements.txt / setup.py / Pipfile
- PHP: composer.json / index.php
You should git add {file}, git commit -am 'added {file}' and then git push heroku master.
git add {file}- Java: pom.xml
- Ruby: Gemfile
- Node.js: package.json
- Python: requirements.txt / setup.py / Pipfile
- PHP: composer.json / index.php
You should git add {file}, git commit -am 'added {file}' and then git push heroku master.
git commit -am 'added {file}'- Java: pom.xml
- Ruby: Gemfile
- Node.js: package.json
- Python: requirements.txt / setup.py / Pipfile
- PHP: composer.json / index.php
You should git add {file}, git commit -am 'added {file}' and then git push heroku master.
git push heroku masterAnswer by Vanessa Atkinson
I ever deploy nodejs app with expressjs before on heroku and it still running.
I’m try to use google,adonis forum and search issues but no luck.
The app run on local machine. Thanks.
remote: > [email protected] start /app
remote: > node server.js
remote:
remote: info: serving app on http://crud-peta.herokuapp.com:59971
remote: events.js:183
remote: throw er; // Unhandled 'error' event
remote: ^
remote:
remote: Error: listen EADDRNOTAVAIL 34.251.216.39:59971
remote: at Object._errnoException (util.js:1022:11)
remote: at _exceptionWithHostPort (util.js:1044:20)
remote: at Server.setupListenHandle [as _listen2] (net.js:1334:19)
remote: at listenInCluster (net.js:1392:12)
remote: at GetAddrInfoReqWrap.doListen [as callback] (net.js:1501:7)
remote: at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:97:10)
remote: npm ERR! code ELIFECYCLE
remote: npm ERR! errno 1
remote: npm ERR! [email protected] start: `node server.js`
remote: npm ERR! Exit status 1
remote: npm ERR!
remote: npm ERR! Failed at the [email protected] start script.
remote: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
remote:
remote: npm ERR! A complete log of this run can be found in:
remote: npm ERR! /app/.npm/_logs/2018-10-17T16_39_13_233Z-debug.log
remote: Waiting for release.... failed.
Answer by Koda Trevino
Otherwise you need to Associate the Heroku app with your code repository by creating a remote to your git local repository. See associate
,
Associate the Heroku app with the repository by creating a git remote
, When you create an app, a git remote (called heroku) is also created and associated with your local git repository.
, If you don’t have an heroku app to host your application, you need to create one. See create
Create an heroku app (Heroku will generates a random name for your app if not passed)
heroku create [name]
heroku create [name]
Creating app... done, polar-everglades-86549
https://polar-everglades-86549.herokuapp.com/ | https://git.heroku.com/polar-everglades-86549.git
# The random name is polar-everglades-86549
-
When you create an app, a git remote (called heroku) is also created and associated with your local git repository.
git remote -v
git remote -v
heroku https://git.heroku.com/polar-everglades-86549.git (fetch)
heroku https://git.heroku.com/polar-everglades-86549.git (push)
origin https://github.com/yourname/yourproject.git (fetch)
origin https://github.com/yourname/yourproject.git (push)
Answer by Katie Park
Проблемы с » git push heroku master»
,
Git push — heroku
,
ошибка запуска git push heroku master
,однако я нашел решение этой проблемы здесь:
Я хочу сделать push и получить ошибку: src refspec master не соответствует ни одному
Я сделал простое веб-приложение Java, используя Maven, и пытаюсь его развернуть. Во-первых, у меня есть ошибка:
error: src refspec master does not match any.
error: failed to push some refs to '[email protected]: etc ...'
Через некоторое время я получаю следующую информацию в своем terminal:
remote: [INFO] BUILD SUCCESS
remote: [INFO] ------------------------------------------------------------------------
remote: [INFO] Total time: 11.039 s
remote: [INFO] Finished at: 2018-10-03T12:25:10+00:00
remote: [INFO] Final Memory: 24M/172M
remote: [INFO] ------------------------------------------------------------------------
remote: -----> Discovering process types
remote: Procfile declares types -> (none)
remote:
remote: -----> Compressing...
remote: Done: 63.5M
remote: -----> Launching...
remote: Released v3
remote: https://immense-falls-73440.herokuapp.com/ deployed to Heroku
remote:
remote: Verifying deploy... done.
Вот мои журналы heroku:
2018-10-02T20:55:00.135902+00:00 app[api]: Release v1 created by user [email protected]
2018-10-02T20:55:00.225698+00:00 app[api]: Enable Logplex by user [email protected]
2018-10-02T20:55:00.225698+00:00 app[api]: Release v2 created by user [email protected]
2018-10-02T20:55:00.135902+00:00 app[api]: Initial release by user [email protected]
2018-10-02T20:56:51.945196+00:00 heroku[router]: at=info code=H81 desc="Blank app" method=GET path="/" host=immense-falls-73440.herokuapp.com request_id=97651816-2e92-4196-add2-4cdd5325ca30 fwd="87.206.210.121"
dyno= connect= service= status=502 bytes= protocol=https
2018-10-02T20:56:52.583382+00:00 heroku[router]: at=info code=H81 desc="Blank app" method=GET path="/favicon.ico" host=immense-falls-73440.herokuapp.com request_id=ca3e65a7-6ef1-4253-a946-2d0cc2e99dc1 fwd="87.20
6.210.121" dyno= connect= service= status=502 bytes= protocol=https
2018-10-02T20:56:52.583849+00:00 heroku[router]: at=info code=H81 desc="Blank app" method=GET path="/favicon.ico" host=immense-falls-73440.herokuapp.com request_id=9ae591af-d87c-4224-9832-dff44ea68fd1 fwd="87.20
6.210.121" dyno= connect= service= status=502 bytes= protocol=https
2018-10-03T12:24:54.000000+00:00 app[api]: Build started by user [email protected]
2018-10-03T12:25:18.147522+00:00 app[api]: Release v3 created by user [email protected]
2018-10-03T12:25:18.147522+00:00 app[api]: Deploy 6d354e57 by user [email protected]
2018-10-03T12:25:20.000000+00:00 app[api]: Build succeeded
2018-10-03T12:26:45.829110+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/" host=immense-falls-73440.herokuapp.com request_id=8ebfefdc-d2a9-438d-a224-11f39ec21781 fwd="
87.206.210.121" dyno= connect= service= status=503 bytes= protocol=https
2018-10-03T12:26:46.544850+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/favicon.ico" host=immense-falls-73440.herokuapp.com request_id=2af704d0-9703-4fe6-a173-2691ca0
fdd39 fwd="87.206.210.121" dyno= connect= service= status=503 bytes= protocol=https
2018-10-03T12:26:46.538716+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/favicon.ico" host=immense-falls-73440.herokuapp.com request_id=11cd4e6d-f850-4687-bc6a-863f30e
667f8 fwd="87.206.210.121" dyno= connect= service= status=503 bytes= protocol=https