Login not possible behind reverse proxy

Can you please give an example on how to use this application behind a reverse proxy? I’ve tried a lot of combinations, and none seem to work, I’m currently using this config:

location / {
        proxy_pass http://127.0.0.1:1624/;

        proxy_http_version 1.1;
        proxy_set_header Host $host:$server_port;
        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;
    }

If I don’t use the X-Forwarded-For header, the webfront always logins automatically as CONSOLE, otherwise I can’t seem to login. It does reject invalid passwords, and seems to accept valid ones, but the menubar still shows the user as unauthenticated…

Any help would be appreciated.

[RaidMax]

It does work, but there is a special rule setup to give root access to local host IP https://github.com/RaidMax/IW4M-Admin/blob/release/pre/SharedLibraryCore/BaseController.cs#L82

This is to make it easy to administrate from the same machine IW4MAdmin is running on. There is also protection against accidentally proxying the console user on localhost which checks the X-Fowarded-For header.

Make sure to use either a different loopback address (eg 127.0.0.2), the internal (NAT) address or WAN address of the machine and you should be able to log in properly.

[mjkzy]

Late bump to this issue, but came across this last night. The fix I found was using proxy_bind in your headers. Also, making sure X-Forwarded-For IS DEFINED or people will have root (console) access.

Here’s my configuration for nginx that works with IW4MAdmin: