|
Hi! 👋 I'm a new user of godoxy. I'm trying to get
I initially tried to define this config via GoDoxy's UI but I can only define a route per domain so the followng is impossible: gitea.DOMAIN.com:
scheme: tcp
host: 192.168.x.y
port: 22:22
gitea.DOMAIN.com:
scheme: http
host: 192.168.x.y
port: :3000Is there a way to achieve the desired result with current GoDoxy? EDIT: Ideally, if there's a way to make this work, I'd also use GoDoxy to do TLS termination for the web ui |
Replies: 1 comment
|
Not as two routes on the same domain. Web UI (HTTP + TLS termination)One HTTP(S) route, alias Git SSHA 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
Because SNI-based TCP on the HTTPS port is only for TLS services (passthrough / |
Not as two routes on the same domain.
Web UI (HTTP + TLS termination)
One HTTP(S) route, alias
gitea(or FQDNgitea.DOMAIN.com) →192.168.x.y:3000. That’s what gets the cert andhttps://gitea.DOMAIN.com.Git SSH
A separate TCP/stream route, e.g.:
For non HTTP/TLS routes, the alias is just a label. Clients just hit the listen port on this machine.
How people connect
https://gitea.DOMAIN.comgit@gitea.DOMAIN.com(port 22) orssh -p 2222 git@gitea.DOMAIN.comBecause
*.DOMAIN.comalready points here,ssh git@anything.DOMAIN.comon that same port also lands on the same SSH backend. That’s expected, not a bug.S…