Can't make it work with reverse proxy

[roymcclure]

Hi,

In my home server I have set up a reverse proxy behind nginx so that I can access many applications from a single entry point.

For those apps who rely on another running service (like amule) I noticed that the service needs to generate its URLs with the same prefix used in the proxy_pass directive for a given location, like for instance:

`

aMule

# For all requests to this server, route to the backend
location /amuleweb/ {
    proxy_pass http://10.0.0.50:4711/amuleweb/;

    # Common proxy headers
    proxy_set_header Host $host;
    proxy_set_header Cookie amuleweb_session_id=$cookie_amuleweb_session_id;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_read_timeout 300;
    proxy_pass_header  X-Transmission-Session-Id;
    proxy_set_header   X-Forwarded-Host $host;
    proxy_set_header   X-Forwarded-Server $host;

}

`

In the amule.conf file there is a parameter called path which i initially thought would be said prefix, however after using curl i noticed that even the config is set to

[WebServer] path=amuleweb

The urls generated by the server are relative to the root.

What's more, I noticed that anything between the root and the file requested is discarded. In the server I can access:

10.0.0.50:4711/amuleweb-main-dload.php

just as well as

10.0.0.50:4711/amuleweb/amuleweb-main-dload.php

or even

10.0.0.50:4711/inmcdonaldsfarm/amuleweb-main-dload.php

And they will all work just fine, it doesn't really matter. But given that after bypassing the login screen we get a:

<META http-EQUIV="Refresh" CONTENT="0; url=amuleweb-main-dload.php">

html reply to our request, this sadly means that the proxy will send us to 10.0.0.50:4711/amuleweb-main-dload.php instead of 10.0.0.50:4711/amuleweb/amuleweb-main-dload.php which would definitely work.

Can the prefix be configured somewhere I'm missing or is there an alternative way that doesn't imply diving into the codebase?

[jehon]

I have the same problem: impossible to use behind a reverse proxy. Did you solve it?

[roymcclure]

Nope.

[jehon]

I managed to make it work like this in a special docker image from linuxserver.io

https://docs.linuxserver.io/general/swag/

The swag config:

location ^~ /amuleweb/ {
    include /config/nginx/proxy.conf;
    include /config/nginx/resolver.conf;

    set $upstream_proto http;
    set $upstream_app amule;
    set $upstream_port 4711;
    proxy_pass $upstream_proto://$upstream_app:$upstream_port;
}

Here is the full config:

server {
    listen 443 ssl default_server;
    listen [::]:443 ssl default_server;

    server_name _;

    ### FILE ssl.conf ###
    ssl_certificate /config/keys/cert.crt;
    ssl_certificate_key /config/keys/cert.key;
    ssl_session_timeout 1d;
    ssl_session_cache shared:MozSSL:10m; # about 40000 sessions
    ssl_session_tickets off;
    
    # curl https://ssl-config.mozilla.org/ffdhe2048.txt > /path/to/dhparam
    ssl_dhparam /config/nginx/dhparams.pem;
    
    # intermediate configuration
    ssl_protocols TLSv1.2 TLSv1.3;
    ssl_ecdh_curve X25519:prime256v1:secp384r1;
    ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-CHACHA20-POLY1305;
    ssl_prefer_server_ciphers off;
    ### FILE ssl.conf end ###

    ### FILE subfolder.conf ###
    location ^~ /amuleweb/ {
        ### FILE proxy.conf ### 
        # Timeout if the real server is dead
        proxy_next_upstream error timeout invalid_header http_500 http_502 http_503;
        
        # Proxy Connection Settings
        proxy_buffers 32 4k;
        proxy_connect_timeout 240;
        proxy_headers_hash_bucket_size 128;
        proxy_headers_hash_max_size 1024;
        proxy_http_version 1.1;
        proxy_read_timeout 240;
        proxy_redirect http:// $scheme://;
        proxy_send_timeout 240;
        
        # Proxy Cache and Cookie Settings
        proxy_cache_bypass $cookie_session;
        #proxy_cookie_path / "/; Secure"; # enable at your own risk, may break certain apps
        proxy_no_cache $cookie_session;
        
        # Proxy Header Settings
        proxy_set_header Connection $connection_upgrade;
        proxy_set_header Early-Data $ssl_early_data;
        proxy_set_header Host $host;
        proxy_set_header Proxy "";
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Forwarded-Method $request_method;
        proxy_set_header X-Forwarded-Port $server_port;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Server $host;
        proxy_set_header X-Forwarded-Ssl on;
        proxy_set_header X-Forwarded-Uri $request_uri;
        proxy_set_header X-Original-Method $request_method;
        proxy_set_header X-Original-URL $scheme://$http_host$request_uri;
        proxy_set_header X-Real-IP $remote_addr;
        ### FILE proxy.conf end ### 

        ### FILE resolve.conf ###
        resolver  127.0.0.11 valid=30s;
        ### FILE resolve.conf end ###
    
        set $upstream_proto http;
        set $upstream_app amule;
        set $upstream_port 4711;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;
    }
    ### FILE subfolder.conf end ###
}