Skip to content
Discussion options

You must be logged in to vote

Not as two routes on the same domain.

Web UI (HTTP + TLS termination)

One HTTP(S) route, alias gitea (or FQDN gitea.DOMAIN.com) → 192.168.x.y:3000. That’s what gets the cert and https://gitea.DOMAIN.com.

Git SSH

A separate TCP/stream route, e.g.:

gitea-ssh:
  scheme: tcp
  host: 192.168.x.y
  port: 22:22       

For non HTTP/TLS routes, the alias is just a label. Clients just hit the listen port on this machine.

How people connect

  • Browser: https://gitea.DOMAIN.com
  • Git SSH: git@gitea.DOMAIN.com (port 22) or ssh -p 2222 git@gitea.DOMAIN.com

Because *.DOMAIN.com already points here, ssh git@anything.DOMAIN.com on that same port also lands on the same SSH backend. That’s expected, not a bug.

S…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by toqueteos
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants