The SSH clone url is guessed by OneDev at its best and you may change the root url at administration / security setting / ssh setting

I've changed the SSH URL to be an actual URL.

That does not work. I've tested it internally and externally, and I get fatal: repository does not exist. However, adding :6610 to the end of the URL when pulling internally does at least get me to the password prompt (and that's all).

Have you configured some sort of port forwarding? OneDev by default listeners on 6610 (for http) and 6611 (for ssh), and you may setup some form of port forwarding outside of OneDev to forward 80/22 traffic to OneDev's 6610/6611 port.

This is not a bug of OneDev.

On my router, I have ports 80, 443, and 22 all directing that traffic to the Hypervisor. On the Hypervisor, I am running nginx reverse proxy and I've literally copied and pasted the config from the manual.

Please describe your case in more detail. Like how you are running OneDev (docker, bare metal), what is the role of Hypervisor here etc.

Bare Metal, on a guest machine. The hypervisor has nginx installed. I am using virt-manager to handle all the guest machines. I have multiple guest machines, and nginx reverse proxy directs the traffic correctly (I can view the sites on 80/443, I cannot access via SSH)

Using the internal IP:Port as remote allows me to pull and push repos internally via SSH, but externally, I can only pull using HTTPS.

On a separate note, because my router cannot handle loopbacks, I have BIND9 split DNS enabled so I can access the guest machines as though external (instead of using their internal IP).

I am not familiar with these techs. OneDev is no different than other services. To access OneDev SSH service via port 22, you need to set up some form of port forwarding to forward TCP traffic from 22 on some node to 6611 on node running OneDev.

Or you may set up OneDev to serve SSH via port 22 directly by running it as root and configure property "sshPort" of "conf/server.properties" as 22. But that will conflict with the SSHD service, and is not recommended.

Okay.

So how can I fix the issue of not being able to push with HTTP?

Are you able to push via port 6610 directly? If yes, you may need to check your proxy/frontend setup.

When the SSH url is set to the (internal) IP:Port, but not when it's the resolved domain.

When it's the domain, the closest I can get to is asking for a password, but the username is wrong (I'm not sure if it's pulling from my Windows username).

When trying to clone on the same network fatal: unable to access 'https://[username]@[domain:6610/TestProject/': error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol; without the port, it just hangs.

When trying to clone externally, I get error:0A00010B:SSL routines::wrong version number

Both, HTTP (not SSH).

Update:

I've got the SSH URL set to the same subdomain as when viewing the site "onedev.[domain]".

git remote -v produces:

origin  ssh://onedev.[domain]/newProj (fetch)
origin  ssh://onedev.[domain]/newProj (push)

It asks for a password for user, but this isn't the username used in OneDev. I believe this is my Windows account username. I have tried in multiple Terminals. All return the same.

I've tried setting git's global and local user.name's, and it doesn't seem to work.

When I've updated the remotes to include the correct username ssh://[username]@onedev.[domain]/[project] all I get back is that "[project] does not appear to be a git repository"

If you can access internal 6611 port via SSH directly without any issue, it should be a problem of port forwarding. To narrow down the issue, you may first make sure port forwarding to a plain old SSHD service works, then change the target port to point to OneDev's SSH service.

@robin so what's the issue with the project not being a git repo?

These are some new projects I've created; one on OneDev and added some commits, and one local "pre-existing" to push. Both return the same issue.

On other git-services, I've had .git files, i.e. [email protected]:matomo-org/matomo-for-wordpress.git

I guess the traffic is not going to OneDev 6611 port all all.

You may run telnet <host> <port> to see if it prints out SSHD welcome message.

Okay... it all seems to be working now. Not sure if restarting the PC actually did the trick, but I can push and pull with ease now. Could have been changing the port forwarding (probably most likely).

I've had a look at the log file, but nothing really stands out to me as the cause.

Glad to see it is working now. So I guess this can be closed now?

Dear me (or anyone who does find this for reference). The solution is simple.

Router port forwarding: any external host:22 internal onedev:6611

((I post this simply because I had a ISP issue, and had to reset the router, and forgot what the solution was))