Cannot fetch repository when the SSH port is something other than 22

[natto1784]

I have (had) a gitea instance with SSH open at port 22001 which makes the SSH clone URI
ssh://git@website.xyz:22001/user/repo.git
instead of the normal
git@website.xyz:user/repo.git which only works with port 22.
The resource can't fetch the repository if the url is in the former style, it works fine with the latter one. For now I have changed the port 22001 to 22 but it can cause me problem in the long run. I would like to keep using 22001.
Note that HTTPS works fine too.

[cozyGalvinism]

I have the same issue at the moment. Would love to see a fix

[HackXIt]

Same issue here, using bitbucket repository host. Sadly no fix since February.

[GCHQDeveloper475823]

What are you seeing when you have this issue?

Identity added: /tmp/git-resource-private-key (key-name)
Cloning into '/tmp/git-resource-repo-cache

Then just hanging forever and never erroring out?

[taylorsilva]

I'd like more info here, specifically what error you're getting.

It's a bit of work for me to setup a local git forge that I can test this against. I'm surprised it's an issue at all because I believe we just pass in the URI as-is to git. I wonder if the issue is actually network related? Again, errors would be helpful!

[natto1784]

Don't think it was network related, but then again I stopped self hosting CI ages ago lol