Repository navigation
Replies: 1 comment
|
Since the hostname won't resolve, I'd start on a client that needs to clone and check DNS first. Resolve-DnsName git.example.internal
Test-NetConnection git.example.internal -Port 443If the name doesn't resolve, check that there's a record in the DNS zone those clients use. If it resolves but port 443 fails, check the IIS HTTPS binding and network path. Once the client can reach IIS, git ls-remote https://git.example.internal/path/repo.git can help separate TLS or authentication errors from Git's CGI configuration. For the backend itself, Git documents the CGI variables it expects, including GIT_PROJECT_ROOT and PATH_INFO. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
We "have to" have a private Git server, and need it serving https
I installed GIT for Windows and commit/push is a happy locally from my IDE to GIT.
I created my GIT user, gave them permissions to folders, activated IIS and the CGI and everything, and I can't resolve my host name.
I realize this is a really high level view, can anyone point me at a resource that isn't about Linux and Apache to serve GIT on http?
All reactions