Request: Static files with relative paths

[Georg-Git]

I would like to use fail2ban-ui in a sub subdirectory of my domain.
Together with other applications.
In front of this I have my own app for user authentification and accessmenagement.

For example:

https://example.com/login/my-app1/
https://example.com/login/my-app2/
https://example.com/login/fail2ban-ui/

Fail2ban-ui is starting, but then requesting his subdirectories straight under root, e.g.:
https://example.com/static/...

So my request is to change the subirectories/urls of fal2ban-ui from absolute pathes to relative pathes:

https://example.com/login/fail2ban-ui/static/
https://example.com/login/fail2ban-ui/locales/
https://example.com/login/fail2ban-ui/api/
and socket:
wss://example.com/login/fail2ban-ui/api/ws

[swissmakers]

Why not to do with the reverse proxy config?

E.g. for Apache:

<VirtualHost *:443>
    ServerName example.com
    
    # Fail2ban UI in subdirectory
    ProxyPreserveHost On
    
    # Proxy all requests under /login/fail2ban-ui/ to the backend
    ProxyPass /login/fail2ban-ui/ http://127.0.0.1:8080/
    ProxyPassReverse /login/fail2ban-ui/ http://127.0.0.1:8080/
    
    # Important: Strip the prefix when forwarding to backend
    # This requires mod_rewrite
    RewriteEngine On
    RewriteRule ^/login/fail2ban-ui/(.*)$ /$1 [L]
    
    # Or use ProxyPassMatch for more control
    # ProxyPassMatch ^/login/fail2ban-ui/(.*)$ http://127.0.0.1:8080/$1
    # ProxyPassReverse /login/fail2ban-ui/ http://127.0.0.1:8080/
</VirtualHost>

Or Nginx:

location /login/fail2ban-ui/ {
    proxy_pass http://127.0.0.1:8080/;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    
    # Rewrite paths - remove the prefix
    rewrite ^/login/fail2ban-ui/(.*)$ /$1 break;
}

Note: The rewrite rule strips the prefix, so the backend receives /static/... and /api/... as if it were at the root. The browser still requests /login/fail2ban-ui/static/..., but the proxy then forwards /static/... to the backend.

[Georg-Git]

Thanks for suggestions - but no luck.
Neither ProxyPass nor ProxyPassMatch.
App html is loaded, but nothing else => 404.

As intermediate solution I am using:

RewriteRule ^\/api\/ws ws://127.0.0.1:8080/api/ws [P,L]

RewriteCond %{REQUEST_URI} ^\/(static|locales|api)\/ [NC] 
RewriteRule ^\/(.*) http://127.0.0.1:8080/$1 [P]

RewriteRule ^\/login\/fail2ban$ /login/fail2ban/ [R,L]
RewriteRule ^\/login\/fail2ban/(.*) http://127.0.0.1:8080/$1 [P,L]

[kramttocs]

I'll also chime in on this enhancement. Hitting the same wall (static paths) but I am wanting to see about using it within Home Assistant via the ingress integration.
It gives me a text only page with a lot of 404s in dev tools.

The project is this: https://github.com/lovelylain/hass_ingress

My yaml entry is:

fail2ban_ui:
  title: Fail2Ban UI
  icon: mdi:shield-lock
  url: http://192.168.1.153:8436
  require_admin: true

This is just me playing around so not anything critical if making it sub-path safe natively isn't on the roadmap.

The integration itself can do rewrites though admittedly I haven't made an attempt at that.