Use multiple server management tools on the same domain

[nitanmarcel (Nitan Alexandru Marcel)]

1. The problem I’m having:

Is it possible to have multiple reverse proxies related to server management on the same domain?

I tried different things as:

admin.example.com {
        route {
        authorize with guests_policy
handle_path /stats/* {
        reverse_proxy localhost:8080 {
        import custom_404
        }
        import serve_fonts
        import serve_ohno
        }
}
}

This runs monotorix and doesn’t seem to work at all, going into /stats/monotorix shows a blank page

With the following usage it works but there are some issues

admin.example.com/stats {
        route {
        authorize with guests_policy

        reverse_proxy localhost:8080 {
        import custom_404
        }
        import serve_fonts
        import serve_ohno
        }
}

Going to stats/monotorix works, this is just an entry endpoint where you can select for which date range to have the logs. After you click OK, it redirects to /monitorix-cgi which breaks. Maybe there is a way to override this from caddy configuration?

2. Error messages and/or full log output:

n/a

3. Caddy version:

v2.7.4 h1:J8nisjdOxnYHXlorUKXY75Gr6iBfudfoGhrJ8t7/flI= (from caddy-security repo)

4. How I installed and ran Caddy:

From caddy-security repo

a. System environment:

Ubuntu 20.04

b. Command:

PASTE OVER THIS, BETWEEN THE ``` LINES.
Please use the preview pane to ensure it looks nice.

c. Service/unit/compose file:

PASTE OVER THIS, BETWEEN THE ``` LINES.
Please use the preview pane to ensure it looks nice.

d. My complete Caddy config:

PASTE OVER THIS, BETWEEN THE ``` LINES.
Please use the preview pane to ensure it looks nice.

5. Links to relevant resources:

[francislavoie]

@nitanmarcel

This runs monotorix and doesn’t seem to work at all, going into /stats/monotorix shows a blank page

Are you sure you didn’t get your two config examples backwards?

@nitanmarcel

admin.example.com/stats {

This wouldn’t work because it would only match exactly /stats and nothing else. It would need to be /stats*.

But anyway, path matchers in the site address is deprecated and should not be used.

@nitanmarcel

handle_path /stats/* {

This will match /stats/monotorix, but it will strip /stats from the request before proxying. If you need to keep that part of the path, you should be using handle, not handle_path.

---

Please completely fill out the help topic template, as per the forum rules. Show your logs, as explained in the template.

Show your full config, not just one part. Things in your import snippets can affect behaviour.

[nitanmarcel (Nitan Alexandru Marcel)]

@francislavoie

/stats/monotorix

Ah yeah sorry, I got the path backward wrong. No I want to strip the /stats| so /stats/monitorixsends me tolocalhost:8080/monotorix, but after going further in monotorix it completly gets rid of /stats`.

So what happens with handle_path:

• Going to example.com/stats/monitorix

  • Works fine, I can see the monotorix webpage

• After clicking OK on the site it rewrites the url with example.com/monotorix-cgi

  • This is expected behaivour from the website, but since I’m serving localhost:8080 at example.com/stats it breaks. Manually going to example.com/stats/monotorix-cgi works fine, except some missing assets, probably because it still looks at them at example.com/monitorix-cgi/…
  • I’m getting an white page while it redirects to example.com/monotorix-cgi

The imports are just some 404 handles, and most things in the config is the caddy-secure configuration. Also the logs all it prints are logs related to caddy-secure.

[francislavoie]

That’s a classic case of the “subfolder problem”:

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…

Your app needs to be aware of the subpath. If it doesn’t have a “base path” config of somekind, your best option is to use a subdomain instead.

[nitanmarcel (Nitan Alexandru Marcel)]

Thanks. I found that handle_path worked, monitorix was broken, it was breaking the /monitorix-cgi to /monitorix-cgi/monitorix-cgi.

Anyway using handle /stats/* and setting the base url in monitorix configuration worked.