Configuration Help

[mholt]

Configuration Help

[gt2416]

Sure, I had to add another matcher so that it knows what subdomain to listen for.
So the config ended up being

"layer4": {
			"servers": {
				"srv0": {
					"listen": [
						":443"
					],
					"routes": [
						{
							"match": [
								{
									"host": [
										"ssh.mydomain.com"
									]
								}
							],
							"match": [
								{
									"ssh": {}
								}
							],
							"handle": [
								{
									"handler": "proxy",
									"upstreams": [
										{
											"dial": [
												"192.168.0.11:22"
											]
										}
									]
								}
							]
						}
					]
				}
			}
		}

[ThisIsTenou]

NVM, I figured it out, You can close this !

Mind sharing the solution with us in case others stumble upon the same issue?

[gt2416]

NVM, I figured it out, You can close this !

[mholt]

@gt2416 Hmm, that's odd. There is no host matcher in layer4, without the http matcher first. And you have two match keys where one is overriding the other (second is kept).

I suspect you did something else different to make it work.

[gt2416]

If I remove that matcher it stops working, however I know it is not matching anything. Its just that the ssh.mydomain.com isnt there anywhere else in the file.
If I try adding a second block with ssh2.mydomain.com to proxy to ip2, it lets me ssh but goes to proxy ip1 (the one defined for ssh.mydomain.com) so yea Im def doing something weird.
Like I said I don't know how to use json, what I do is write my caddy file, copy the json from the autosave location and add this layer4 code block at the end. My json file is 650lines, I dont plan to learn to use it completely lol, caddyfile is a lot easier.
How would I go about doing this, ssh.mydomain.com -- IP1, ssh2.mydomain.com --IP2 ?

[mholt]

If I remove that matcher it stops working, however I know it is not matching anything. Its just that the ssh.mydomain.com isnt there anywhere else in the file.

Sure, but that shouldn't affect SSH, which doesn't use HTTP or TLS.

Like I said I don't know how to use json, what I do is write my caddy file, copy the json from the autosave location and add this layer4 code block at the end.

Instead of using autosave, use the caddy adapt command.

ssh.mydomain.com -- IP1, ssh2.mydomain.com --IP2 ?

I'm not sure what you mean. SSH doesn't distinguish hostnames like HTTP does.