Github - The Unauthenticated Git Protocol On Port 9418 Is No Longer Supported - Stack Overflow. After a bit of googling i found this stackoverflow answer which suggested running. The unauthenticated git protocol on port 9418 is no longer supported.
And doing so indeed fixed the issue. This issue occurred as a result of github's most recent improving git protocol security, which was released on january 11, 2022, final brownout. Or similar failure message from another git host. You should see the progress of your. We’re changing which keys are supported in ssh and removing unencrypted git protocol. Improving git protocol security on github. After a bit of googling i found this stackoverflow answer which suggested running. So i was trying to use the cli to checkout a pull request but i kept getting this error. You should see something like this appear as a response. Could some other git config file really be in play here that still has git://.?
The unauthenticated git protocol on port 9418 is no longer supported. The unauthenticated git protocol on port 9418 is no longer supported. If you’re an ssh user, read on for the details and timeline. The unauthenticated git protocol on port 9418 is no longer supported. This change affects packages in buildroot and yocto releases that are still using the mentioned protocol for github resulting in the following error message: The unauthenticated git protocol on port 9418 is no longer supported occurs because github has stopped accepting the deprecated key and signature types, ciphers, and macs, and the unencrypted git protocol from march 15, 2022. Only users connecting via ssh or git:// will be affected. Make a slight change to the git repository uri (e.g. The unauthenticated git protocol on port 9418 is no longer supported. The unauthenticated git protocol on port 9418 is no longer supported. Please see improving git protocol security on github | the github blog for more information.
