-
Notifications
You must be signed in to change notification settings - Fork 411
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Travis Login Fails #794
Comments
I also encountered the same problem... System
Ruby: Ruby 2.6.3-p62
Operating System: Mac OS X 10.15.4
RubyGems: RubyGems 3.0.3
CLI
Version: 1.10.0
Plugins: none
Auto-Completion: yes
Last Version Check: 2021-01-13 19:46:34 +0800
Session
API Endpoint: https://api.travis-ci.com/
Logged In: as "alvin0216"
Verify SSL: yes
Enterprise: no
Endpoints
com: https://api.travis-ci.com/ (access token, default, current)
org: https://api.travis-ci.org/ ()
Last Exception
An error occurred running `travis login --pro`:
RuntimeError: Not Found
from /Library/Ruby/Gems/2.6.0/gems/travis-1.10.0/lib/travis/tools/github.rb:212:in `rescue in basic_auth'
from /Library/Ruby/Gems/2.6.0/gems/travis-1.10.0/lib/travis/tools/github.rb:208:in `basic_auth'
from /Library/Ruby/Gems/2.6.0/gems/travis-1.10.0/lib/travis/tools/github.rb:216:in `login'
from /Library/Ruby/Gems/2.6.0/gems/travis-1.10.0/lib/travis/tools/github.rb:81:in `possible_tokens'
from /Library/Ruby/Gems/2.6.0/gems/travis-1.10.0/lib/travis/tools/github.rb:50:in `each_token'
from /Library/Ruby/Gems/2.6.0/gems/travis-1.10.0/lib/travis/tools/github.rb:37:in `with_token'
from /Library/Ruby/Gems/2.6.0/gems/travis-1.10.0/lib/travis/cli/login.rb:31:in `login'
from /Library/Ruby/Gems/2.6.0/gems/travis-1.10.0/lib/travis/cli/login.rb:50:in `run'
from /Library/Ruby/Gems/2.6.0/gems/travis-1.10.0/lib/travis/cli/command.rb:200:in `execute'
from /Library/Ruby/Gems/2.6.0/gems/travis-1.10.0/lib/travis/cli.rb:64:in `run'
from /Library/Ruby/Gems/2.6.0/gems/travis-1.10.0/bin/travis:18:in `<top (required)>'
from /usr/local/bin/travis:23:in `load'
from /usr/local/bin/travis:23:in `<main>' Even though I took this approach |
I am facing the same issue:
|
See #788 (comment) for an interim workaround. |
I have the same issue and can confirm that the workaround proposed by BanzaiMan worked for me.
|
I am also afflicted, and the workaround referenced by @BanzaiMan does not work (specifically, point no.2 in the referenced post). Unless, of course, I am doing it wrong.
|
Hello! I'm running into the same set of issues. I realized that I have 2FA activated for my account, and the way that the This error also occurs to me when I try to push to a GitHub repository with the remote set to HTTPS instead of my SSH keys. That is to say, due to the recent changes that Github wants to deprecate the git CLI for the simple HTTPS login feature, in favor of the permission key generated as per security grants on the repository It would be a better move to let us, and a possible solution as well to circumvent this, that we could somehow feed Another partial helping method would be to generate a more helpful error message that lets the user know whether the error was due to the 2FA issue, or something else. Currently, the error logs generated are not helpful to trace the problem too. For the record, one of the current options available via |
I was able to fix my issue by changing the repository endpoints in my I had recently started using Note that I still needed to do this even though I had already changed the |
Thanks for the update, @SturmB ! I'll get back to trying this in 2-3 days' time. Appreciate the feedback. |
STILL BROKEN |
@Rubix982 I was able to login with 2FA by using a Github Personal access token and passing it via
|
still broken |
i can't appreciate you any more! i succeed in logining in by token successfully,but i still fail to login in by my username and password. |
+1. Broken for me as well. I can't do |
This is the only solution that worked for me. |
Finally! After 10 months, I can finally finish my Jenkins tutorial. Thanks, @ephraimilunga, @suxur! |
I cannot login using the travis CLI. I looked around and this seems to be a know issue, but I really couldn't be sure! π€·π»ββοΈ
Here is the
travis report --pro
:The text was updated successfully, but these errors were encountered: