Our server is sat behind an IIS reverse proxy, entirely within a local network. The IIS deals with https requests and just sends http requests to the server.
Client is on the local network
Fetch works, vscode can download the git and history
Trying to push opens the oauth dialog
the git credential manager is then added to the server
but then push hangs?
The logs appear to tell a story of the client being authorized
router: completed POST /login/oauth/grant for [134.219.128.90:11810]:0,
but every time the push command is run after cancelling the prompt to add an oauth application pops up again.
The redirect url could be wrong? could one of the firewalls on the server be incorrectly set up?
The server was setup following the reverse proxy guide and the setup is as follows
[server]
SSH_DOMAIN = localhost
DOMAIN = localhost
HTTP_PORT = 3000
ROOT_URL = https://git.our.domain/
where git.our.domain is actually the correct domain name that has self signed certificates that are trusted locally
Once “authorize application” is clicked it redirects to my login landing screen, and the push just sits there,
digging deeper in to the client logs -
trace: run_command: 'git credential-manager get'
begins and I assume sits and awaits a response from the server but potentially never gets any? I am unsure of how to test this?
Ideas on a fix would be very appreciated