Unable to reverse proxy traffic from Caddy (Docker) to Host Machine (Code-Server as Systemd)

[francislavoie]

@PancakePuncher

I have been absolutely beating my head against a wall trying to understand if I can get Caddy which is running in a docker container to send traffic to a non-dockerized application on the host machine.

Yes, use host.docker.internal to point to the host (instead of an IP address). Google it.

The docker host IP is not guaranteed to stay the same, so that hostname is provided to make it work.

@PancakePuncher

	handle_path /code* {
		reverse_proxy 172.20.0.1:8080
	}

Keep in mind that you don’t have any routes for anything other than /code* so you’ll get empty responses instead.

In general, I recommend using subdomains instead of subpaths. So I’d suggest making a code.pancakepuncher.com subdomain for this.

See this article which explains:

The "subfolder problem", OR, "why can't I reverse proxy my app into a subfolder?"

Have you ever tried to reverse proxy an app into its own little subfolder of your domain name? Makes things neat, doesn’t it? Using example.com/foo/ for one app, example.com/bar/ for another. If you’re coming here from one of the selfhosted communities, you might be thinking along the lines of example.com/sonarr/, example.com/radarr/ etc. Chances are, you’ve tried some configuration along these lines: example.com { redir /sonarr /sonarr/ handle_path /sonarr/* { reverse_proxy localhost…