This question might be considered duplicate of this: Unable to use heroku gem cli after password changes, but it is not.
In my case I have the latest Mac OS X 10.8.3 and I've installed brand new Heroku tool belt. First thing I've tried is to authenticate by issuing this:
heroku login
I was asked for my Heroku credentials, which I've entered (many-many times), but I got "Authentication Failed" message.
I've tried signing in with my credentials to Heroku website multiple times from different browsers - it all works, but I can't authenticate with Heroku CLI.
I don't have ~/.netrc file, I don't have any fancy firewall software on my Mac. What am I possibly doing wrong?
Thanks,
Alex.
Update 03/18/2013 9 PM Mountain:
This is the Heroku issue and they are looking into it:
Sounds like it might be an SSH key issue.
Here is a good guide to resolving it.
https://devcenter.heroku.com/articles/keys
Heroku engineers have fixed it and I was able to authenticate. Thank you, Heroku!
Related
Im working on a project with Ruby on Rails language, deployed to Heroku everything is working fine
I had Mailgun addon installed in my Heroku app
at one point I tried to change it to another mailing Addon
so I unlinked the Mailgun addon and connected another Addon
after a little research, I wanted to connect back the Mailgun addon.
when I tried to connect Mailgun again, it said that my app has an account and I cant reconnect it
I cant access my account by the email written in the Heroku's error notification.
what should I do at this point?
In that link below, there is an image of the error I get in my terminal.
Heroku Error for command: " heroku addons:create mailgun:starter"
Another link for an image of the error I get when trying to add Mailgun addon through my heroku app dashboard.
Heroku Error from Heroku dashboard
If you think I should use another mailer addon, I would love to hear about it.
Thank you in advance
While updating my client's application on Heroku, I received the following warning message:
The Heroku Legacy Platform API will be Sunset on April 15th 2017. Please update your client access or the Heroku CLI to the latest version. See https://blog.heroku.com/sunsetting_heroku_s_legacy_platform_api_v2 for more details.
The link it provides explains why its sunsetting but not how to migrate to remove this warning message. The links that site take you to the API documentation but I couldn't find any docs on migration from v2 to v3 Heroku API.
Can someone point me in the right direction?
For some reason, updating heroku toolbelt wasn't working. Removing the link to the repository and then following the steps to install heroku again in the link I've provided fixed my problem.
https://devcenter.heroku.com/articles/heroku-cli
Our company wants to build a Rails-based backend website and we chose the OpenShift platform to host and deploy. To connect the two, all the guides lead to the installation of the ruby rhc gem and then setup it.
I'm fresh to OpenShift and I'm trying to setup the rhc toolkit on a remote Ubuntu server. Now I ran gem install rhc and everything went fine. Since I have to configure rhc through rhc setup, I ran this command afterwards and just after asking which server I want to use (I left it blank to use openshift.redhat.com) it comes to the login part.
At this moment, OpenShift Online allows you to login only with your GitHub account, so I gave in the GitHub credentials and... voilà! Username or password is not correct. Tried this both on PuTTy and ConEmu.
I swear I checked the login data more than 1000 times, and I'm totally lost.
Thank you a lot in advance
If you want to use OpenShift Online NextGen Developer Preview, you do not use the rhc client. You need to use the oc client. So anything you read where it says rhc is the wrong documentation.
Once you are logged in through the new web console, select on the '?' in circle top right and select command line tools. It will give you links to the 'oc' tools to download, plus the command you need to run to login from the command line using a session access token.
The link to that page should be:
https://console.preview.openshift.com/console/command-line
Also suggest you get down and use the free eBook for the new platform at:
https://www.openshift.com/promotions/for-developers.html
It uses a VM, but ignore the client login step from that and use that from page above instead and then follow examples in the book against the Online NextGen Developer Preview instead.
Trying to add SendGrid functionality to my heroku rails app by running heroku addons:create sendgrid:starter from my app's directory, but getting an error message each time:
Error Provisioning User - Whitelabel domain could not be located when creating customer
I'm also getting the exact same error when trying to add SendGrid Starter add-on directly through the Heroku web interface for my app.
My heroku account does have a credit card on file, so that shouldn't be the issue. This heroku app is on the free heroku tier, but I believe all the add-ons are supposed to be supported even for free heroku apps.
Has anyone run into this before? If so, any pointers on how to fix it?
It just worked. I believe it may have been the result of temporary service outage on the part of SendGrid (even though their system status pages indicated all services were up and running).
Sorry for the false alarm.
We use git for version control. Right now only my account seems to be able to deploy successfully to a remote server for several apps, but I don't know why. I would like to set it up so that deploying works for other people at my company, but I don't really have the full picture laid out in my head so I don't know what needs to be done.
To me it seems like whoever wants to deploy needs a: user account on the server, an account on github, and permission to pull...? However, other users seem to have the notorious Permission denied (publickey). fatal: The remote end hung up unexpectedly and other errors.
Can anyone provide a short list of what I need to do on the server (make an account, add ssh keys or something?) and git (ssh keys again? not sure) to get the deploy to work?
Capistrano assumes you can ssh into the server you are deploying to. You are probably using a communal apps, deployer, or some other app-specific user to deploy your app. This will be the user that is set in your deploy.rb file.
You will need to copy everyone's public key into the authorized_keys of whatever your deploying user is. That is just how Capistrano works.