<![CDATA[Forwarding the true client IP Address]]>I have an NPM that helps to manage traffic to my NAS, Cloudron and other services.

It appears that Cloudron is reporting the client IP Address as my NPM address.
For my NAS, I’ll just need to indicate my Trusted Proxy IP Address and it’ll start reporting the true client IP Address.

Where can I do the same for Cloudron? TIA!

]]>https://forum.cloudron.io/topic/8321/forwarding-the-true-client-ip-addressRSS for NodeMon, 11 May 2026 17:51:57 GMTSun, 01 Jan 2023 16:41:33 GMT60<![CDATA[Reply to Forwarding the true client IP Address on Tue, 03 Jan 2023 21:46:26 GMT]]>FWIW, as a workaround - Cloudron itself can act as a NPM . https://docs.cloudron.io/apps/#app-proxy

]]>https://forum.cloudron.io/post/59175https://forum.cloudron.io/post/59175Tue, 03 Jan 2023 21:46:26 GMT<![CDATA[Reply to Forwarding the true client IP Address on Tue, 03 Jan 2023 21:45:17 GMT]]>In this setup, NPM makes the actually client call and thus Cloudron picks up that as the IP address. As you said, this requires us to change Cloudron's nginx configs to have a trusted proxy server setting and also then forward the X-Forwarded-For from the request to the apps.

I will move this as a feature request since we don't have this feature.

]]>https://forum.cloudron.io/post/59174https://forum.cloudron.io/post/59174Tue, 03 Jan 2023 21:45:17 GMT<![CDATA[Reply to Forwarding the true client IP Address on Mon, 02 Jan 2023 10:10:03 GMT]]>Possibly the mastodon package then has to be adjusted to pick up the forwarded-for headers from the reverse proxy. Where in mastodon are the originating IP addresses used so we can validate a potential fix?

]]>https://forum.cloudron.io/post/58976https://forum.cloudron.io/post/58976Mon, 02 Jan 2023 10:10:03 GMT