@pitaj said in Login seems succesfull but does not actually logs user in.:
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;
proxy_set_header Host $http_host;
proxy_set_header X-NginX-Proxy true;
Using this config does not solve the "login, welcome back as guest" issue.
It does revert to the issue that the wrong client IP addresses are used in log files, though. This is why my config diverts from the recommended one. Bear in mind, I'm using ssl stream proxying here which requires a slightly different setup.
Edit: Following the documentation you referenced I moved my proxy config inside the location / {}
block and it is working now. I'll be da... Why isn't the location block inheriting the the server {}
-wide block settings as one would expect? Do I need to provide the proxy settings inside the location /assets
et al. blocks as well?
To summarize: my config as specified above, used in a ssl-stream-proxy setup, provided inside the location / {}
block seems to be working fine, login is working again as it should. It is however insufficient to globally specify those proxy settings in the server {}
block (still ssl-stream-proxy setup).
Thank you!