Hello everyone. I'm resuming work on a little addon I've maintained for a number of years.
Apparently the old svn+ssh method is no longer supported. I created a new git repo and attempted to push the code, but I keep getting authentication errors. I had just merged my curseforge account with Twitch a couple days ago, so I'm wondering if that's what's causing my issues?
Can anyone confirm that a twitch-linked account can be used with the curse git server to push code?
Here's the verbose output from git if that's any help.
$ GIT_CURL_VERBOSE=1 git push origin master * Couldn't find host repos.curseforge.com in the _netrc file; using defaults * timeout on name lookup is not supported * Trying 104.16.85.211... * TCP_NODELAY set * Connected to repos.curseforge.com (104.16.85.211) port 443 (#0) > GET /wow/howmany/info/refs?service=git-receive-pack HTTP/1.1 Host: repos.curseforge.com User-Agent: git/2.12.2.windows.1 Accept: */* Accept-Encoding: gzip Pragma: no-cache
When you linked your account, still use your previous CF username/password for repository access for now. The easiest way to do that on Windows is to use the Git Credentials Manager, which comes with recent versions of Git For Windows.
PS:
svn+ssh has been discontinued with the move to the new platform. All repository access is through HTTPS now.
Hello everyone. I'm resuming work on a little addon I've maintained for a number of years.
Apparently the old svn+ssh method is no longer supported. I created a new git repo and attempted to push the code, but I keep getting authentication errors. I had just merged my curseforge account with Twitch a couple days ago, so I'm wondering if that's what's causing my issues?
Can anyone confirm that a twitch-linked account can be used with the curse git server to push code?
Here's the verbose output from git if that's any help.
$ GIT_CURL_VERBOSE=1 git push origin master
* Couldn't find host repos.curseforge.com in the _netrc file; using defaults
* timeout on name lookup is not supported
* Trying 104.16.85.211...
* TCP_NODELAY set
* Connected to repos.curseforge.com (104.16.85.211) port 443 (#0)
> GET /wow/howmany/info/refs?service=git-receive-pack HTTP/1.1
Host: repos.curseforge.com
User-Agent: git/2.12.2.windows.1
Accept: */*
Accept-Encoding: gzip
Pragma: no-cache
< HTTP/1.1 401 Unauthorized
< Date: Sun, 02 Apr 2017 15:29:25 GMT
< Content-Type: text/plain; charset=utf-8
< Content-Length: 24
< Connection: keep-alive
< Set-Cookie: __cfduid=d34196ecce6ff186f7c818ecf7115d8ce1491146965; expires=Mon, 02-Apr-18 15:29:25 GMT; path=/; domain=.curseforge.com; HttpOnly
< Www-Authenticate: Basic realm="CurseForge Repositories"
< X-Content-Type-Options: nosniff
< Server: cloudflare-nginx
< CF-RAY: 3494d2d3c8b82537-ORD
<
* Connection #0 to host repos.curseforge.com left intact
(this is where I enter my credentials)
* Couldn't find host repos.curseforge.com in the _netrc file; using defaults
* Found bundle for host repos.curseforge.com: 0x17398d0 [can pipeline]
* Re-using existing connection! (#0) with host repos.curseforge.com
* Connected to repos.curseforge.com (104.16.85.211) port 443 (#0)
> GET /wow/howmany/info/refs?service=git-receive-pack HTTP/1.1
Host: repos.curseforge.com
User-Agent: git/2.12.2.windows.1
Accept: */*
Accept-Encoding: gzip
Pragma: no-cache
< HTTP/1.1 401 Unauthorized
< Date: Sun, 02 Apr 2017 15:30:12 GMT
< Content-Type: text/plain; charset=utf-8
< Content-Length: 24
< Connection: keep-alive
< Set-Cookie: __cfduid=df017cff604eda98503ae2405bbc968841491147012; expires=Mon, 02-Apr-18 15:30:12 GMT; path=/; domain=.curseforge.com; HttpOnly
< Www-Authenticate: Basic realm="CurseForge Repositories"
< X-Content-Type-Options: nosniff
< Server: cloudflare-nginx
< CF-RAY: 3494d3fb9aed2537-ORD
<
* Connection #0 to host repos.curseforge.com left intact
remote: Authorization required.
fatal: Authentication failed for 'https://repos.curseforge.com/wow/howmany/'
When you linked your account, still use your previous CF username/password for repository access for now. The easiest way to do that on Windows is to use the Git Credentials Manager, which comes with recent versions of Git For Windows.
PS:
svn+ssh has been discontinued with the move to the new platform. All repository access is through HTTPS now.
In reply to Nevcairiel: