Caddy and forgejo

IIRC there is a plugin for Caddy that can do what you are looking for.
Edit: here you go
- This would only work if there is no other traffic on the port being used (eg: port 22). If both the host SSH service and Forgejo SSH service expect traffic on port 22, then this would not work since server name indication (SNI) is not provided with SSH traffic and Caddy would not be able to identify the appropriate destination for multiple SSH services traffic.

Not really through Caddy but for my setup I have it so the ssh port for Forgejo is only accessible through tailscale. So for push/pulling updated my ssh config file to something like
Host git.mysite.com HostName tailscaleMachineName User git Port 1234
Then doing git pull git@git.mysite.com:user/project.git works just fine as long as I am connected to tailscale
Otherwise you could open the port for Forgejo's ssh so that you can access it without any vpn
- Ahh, thank you! I've been banging my head against a wall trying to figure out how to do this.
- I feel silly for not realizing that the SSH config would be used by Git!
  I thought if Forgejo's SSH service listened to a non-standard port that you would have to do commands with the port in the command similar to below (following your example). I guess I assumed Git did not directly use the client's SSH service.
  sh
  
  git pull git@git.mysite.com:1234:user/project.git

I dont know about caddy but nginx proxy manager does this very well. Also, if running in docker, you can expose the port that runs ssh for forgejo und a different port than the host machine‘s (eg 2222). In that case you just put the remote in with the port and call it a day.

Use something that can do TCP, i.e. HAProxy, NGINX or Apache

Afaik you can reverse proxy the ssh connection. I've been connecting to my server using the domain and tld (asudox.dev)
- Are you able to provide some details on how you are doing this? I don't think you can do much with reverse proxies and SSH beyond routing all traffic on port 22 (or the configured SSH port) to whichever port SSH is listening on. In other words, the reverse proxy cannot route SSH traffic for the host on port 22 to the host, route SSH traffic for Forgejo on port 22 to Forgejo's SSH process, and SFTP traffic on port 22 to the SFTP process - at least not via domain name like a HTTP/HTTPS reverse proxy would work.
  Instead, this would need to be done via IP address where the host SSH process listens on 192.168.1.2, the Forgejo SSH process listens on 192.168.1.3, and the SFTP process listens on 192.168.4. Otherwise, each of those services would need to use different ports.
  
  Upon more investigation, it seems more like caddy indeed can't. The only reason it works is because I directly point the A record to the VPS's IP.

I can't give you the technical explanation, but it works.
My Caddyfile only something like this

@forgejo host forgejo.pe1uca handle @forgejo { reverse_proxy :8000 }
and everything else has worked properly cloning via ssh with git@forgejo.pe1uca:pe1uca/my_repo.git
My guess is git only needs the host to resolve the IP and then connects to the port directly.
- I believe the reverse proxy settings in your post is just configured to handle the http/https connection, not the SSH connection. Instead, SSH connections are likely being routed to the machine running Foegejo via DNS and your reverse proxy is not involved with anything related to SSH.
  I assume you either have SSH disabled on your host or SSH on your host uses a port other than 22?

If both Caddy and Forgejo are running in Docker containers you could do SSH Container Passthrough.
Link is to Gitea docs but should work fine with Forgejo.
- It works but I don't think Forgejo plans to support it in the future. Gitea and Forgejo started to diverge and the documentation regarding docker is somewhat in a deprecated state.
  Edit: I also think the OP's question is different from this. So this might not be a solution.

There's really no need to reverse proxy ssh. What are you attempting to accomplish with the reverse proxy exactly? Http proxying allows you to add things like TLS encryption and modify headers. But ssh is a secure protocol already and you can't really modify much in transit.
- There are plenty of valid reasons to want to use a reverse proxy for SSH:
  Maybe there is a Forgejo instance and Gitea instance running on the same server.
  Maybe there is a Prod Forgejo instance and Dev Forgejo instance running on the same server.
  Maybe both Forgejo and an SFTP are running on the same server.
  Maybe Forgejo is running in a cluster like Docker Swarm or Kubernetes
  Maybe there is a desire to have Caddy act as a bastion host due to an inability to run a true bastion host for SSH or reduce maintenance of managing yet another service/server in addition to Caddy
  Regardless of the reason, your last point is valid and the real issue here. I do not think it is possible for Caddy to reverse proxy SSH traffic - at least not without additional software (either on the client, server, or both) or some overly complicated (and likely less secure) setup. This may be possible if TCP traffic included SNI information, but unfortunately it does not.

Learn NGINX that is the only answer, it’s a B!+€# to get configured but once you know how it will save you so much time, If you want cheat mode run the docker image and use the web interface but make sure to rtfm there are some gotch ya’s

I don't think you can with caddy

- There seems to be mixed reactions to this suggestion. I don't know enough to understand why.
  
  Because forgejo's ssh isn't for a normal ssh service, but rather so that users can access git over ssh.
  Now technically, a bastion should work, but it's not really what people want when they are trying to set up git over ssh. Since git/ssh is a service, rather than an administrative tool, why shouldn't it be configured within the other tools used for exposes services? (Reverse proxy/caddy).
  And in addition to that, people most probably want git/ssh to be available publicly, which a bastion host doesn't do.

There are a few ways to do it, but you don't use caddy for SSH.
host SSH on port 22, forgejo on a different port. Expose both ports to the internet
host SSH on a different port, forgejo on port 22. Expose both ports to the internet
host SSH on port 22. Forgejo on port 2222. Only 22 exposed to the internet. Change the authorized_keys user of the git user on host to automatically call the internal forgejo SSH app
Last option is how I run my Gitea instance, authorized keys is managed by gitea so you don't really need to do anything high maintenance.
~git/.ssh/authorized_keys:

command="/usr/local/bin/gitea --config=/data/gitea/conf/app.ini serv key-9",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty,no-user-rc,restrict ssh-rsa PUBLICKEYHASH
/usr/local/bin/gitea:

ssh -p 2222 -o StrictHostKeyChecking=no git@127.0.0.14 "SSH_ORIGINAL_COMMAND=\"$SSH_ORIGINAL_COMMAND\" $0 $@"
127.0.0.14 is the local git docker access where I expose the service, but you couldn't different ports, IPS, etc.

If you connect from outside your LAN, you would need to forward the ssh port to the server in your router settings. If you are inside the LAN, just use the ip address of the forgejo server.

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

Fewer Letters	More Letters
DNS	Domain Name Service/System
Git	Popular version control system, primarily for code
HTTP	Hypertext Transfer Protocol, the Web
HTTPS	HTTP over SSL
IP	Internet Protocol
SFTP	Secure File Transfer Protocol for encrypted file transfer, over SSH
SSH	Secure Shell for remote terminal access
SSL	Secure Sockets Layer, for transparent encryption
TCP	Transmission Control Protocol, most often over IP
TLS	Transport Layer Security, supersedes SSL
VPS	Virtual Private Server (opposed to shared hosting)
nginx	Popular HTTP server

[Thread #962 for this sub, first seen 10th Sep 2024, 12:25] [FAQ] [Full list] [Contact] [Source code]