Solved X-Forwarded-For Header

[Mastadamus]

I have a NGINX reverse proxy in front of Cloudron due to the fact I have multiple VM's to proxy to and only one Public IP. Everything is working correctly. I am using NGINX proxy manager. I can visit all my Cloudron sites. My only problem is this.. In the NGINX logs on my Cloudron box, it shows the source IP of traffic as the internal IP address of my external NGINX Proxy manager. Nginx proxy manager should be configured for x-forwarded for headers but it seems like the NGINX on the cloudron box isn't using the x-forwarded for header as the source. Do you guys have any idea why or how to fix it?

[Mastadamus]

Nevermind I fixed it by doing the following.

1. Added this configuration to the HTTP{} section of the nginx.conf file in /etc/nginx/nginx.conf

log_format main '$http_x_forwarded_for - $remote_user [$time_local] '
'"$request" $status $body_bytes_sent "$http_referer" '
'"$http_user_agent"' ;

access_log /var/log/nginx/access.log main;

[Mastadamus]

Nevermind I fixed it by doing the following.

1. Added this configuration to the HTTP{} section of the nginx.conf file in /etc/nginx/nginx.conf

log_format main '$http_x_forwarded_for - $remote_user [$time_local] '
'"$request" $status $body_bytes_sent "$http_referer" '
'"$http_user_agent"' ;

access_log /var/log/nginx/access.log main;

[mehdi]

@Mastadamus This will probably be lost at each cloudron update, be aware

[robi]

@girish should this be added as default for Cloudron?

[girish]

@robi this is set for app but not for the dashboard itself which OP was trying to fix. I think we have to add it to dashboard's nginx config when we look into supporting reverse proxy setups properly.

[Mastadamus]

@girish Any update on support reverse proxy or adding this logging config as default?

[girish]

@Mastadamus yes, reverse proxy is implemented in next release (7.3) - https://forum.cloudron.io/topic/6655/what-s-coming-in-7-3/21