Help with tomcat reverse proxy

[francislavoie]

You could try this:

{
	debug
	http_port 8080
	https_port 8443
}

:8443 {
	tls /my_home/certs/server.pem /my_home/certs/server.key
	encode zstd gzip

	handle_path /apps* {
		reverse_proxy localhost:8888
	}

	handle {
		root * /my_home/web
		templates
		file_server browse
	}
}

Using handle blocks makes sure that reverse_proxy and file_server routes are mutually exclusive. And handle_path has built-in uri strip_prefix logic.

@CopyBilla

When I try https://hostname:8443/apps I get 404

That was because /apps doesn’t match /apps/* because your matcher expects at least a slash after /apps.

It’s worth mentioning though, not all backend apps are properly set up for, or configured to handle requests to a different base path. See this article for additional reading on the topic:

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…