Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
GitHub no longer supports unauthenticated installation protocol
See original GitHub issueThe command for installing via pip no longer works due to changes in security protocols.
Changing the URL to an HTTPS address fixed this issue for me, i.e. pip install git+git://github.com/psf/black->pip install git+https://github.com/psf/black
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
The unauthenticated git protocol on port 9418 is no longer ...
GitHub has dropped support for all unencrypted protocols, which only includes the Git protocol (those that uses the git:// prefix). Thus, the ...
Read more >Tell HN: GitHub no longer supporting unauthenticated `git://`
Either the Git repository is available for everyone to clone, or it isn't. This means that there is generally no pushing over this...
Read more >"unauthenticated git protocol on port 9418" error when installing
This error happens either in GitHub Actions CI (the automated tests on each PR) or when running rails webpacker:install && rails ...
Read more >Installation Error: Unauthenticated git protocol on port 9418 #27
'Unauthenticated git protocol on port 9418 is no longer supported' while installing via luarocks api7/lua-resty-radixtree#107.
Read more >The unauthenticated git protocol on port 9418 is no longer ...
Issue description The unauthenticated git protocol on port 9418 is no longer supported when installing lua-resty-dns-client. package ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This has been fixed on main very very recently by PR #2761, if you’re referencing the stable documentation, well, it won’t see changes until we do another release which we’re targetting for the end of the month.
#2761 Might have already solved this!