[Bug]: Gitea Source Control Provider Does Not Accommodate Custom Ports

[ryangurn]

Installation Type *

VPS

Vito Version *

3.21.3

Describe the Bug *

So I am torn between bug a feature. I see from the code that the port 22 is hardcoded which makes sense.

I am using that latest version of Gitea in a homelab setup running via a set of containers, and most of them are running from two devices, so I have to manually prevent port conflicts within a machine. In most cases what that means is the SSH for the VM or specific virtualized system normally does not use port 22.

Gitea is a great example, it is running on a linux box inside of a docker container, I need to be able to access the linux machine via SSH and that is via port 22, so Gitea gets 222, but that is where it causes unintended consequences. Vito does not allow for handling this.

Steps to Reproduce *

1. Setup a source control provider like gitea on an external system on a non-standard ssh port
2. Attempt to use Vito with that non-standard git instance to deploy a site.

Expected Behavior *

Vito can handle non-standard ssh ports for gitea

Logs *

{
"msg": "SSH command failed with an error",
"log": {
"App\Models\ServerLog": {
"server_id": 1,
"name": "1-1778559264-clone-repository.log",
"type": "clone-repository",
"disk": "server-logs",
"site_id": 5,
"updated_at": "2026-05-12T04:14:24.000000Z",
"created_at": "2026-05-12T04:14:24.000000Z",
"id": 81
}
}
}

Screenshots

None of importance, just failures in the UI, but successful SSH connections via the non-standard port in terminal.

Additional Context

I am working on a potential PR for this but at this point mainly investigating options.

[ryangurn]

The UX side of this is also problematic, it seems that it only checks the HTTP endpoint provided when setting up the gitea provider, and does not test SSH connectivity which could show an error before attempting to deploy a site.