The 'X-Forwarded-For' header is set but the Express 'trust proxy'

[DenverOps]

Checklist

• [x] I am not using Home Assistant. Or: a developer has told me to come here.
• [x] I have checked the troubleshooting section and my problem is not described there.
• [x] I have read the changelog and my problem is not mentioned there.

Deploy method

Home Assistant Add-on

Z-Wave JS UI version

10.6.1

ZwaveJS version

15.6.0

Describe the bug

I started seeing these error messages come in the zwave js us logs. If this isn’t the correct place to post this issue, please let me know and I will put it in the correct spot..

ValidationError: The 'X-Forwarded-For' header is set but the Express 'trust proxy' setting is false (default). This could indicate a misconfiguration which would prevent express-rate-limit from accurately identifying users. See https://express-rate-limit.github.io/ERR_ERL_UNEXPECTED_X_FORWARDED_FOR/ for more information. at Object.xForwardedForHeader (/opt/node_modules/express-rate-limit/dist/index.cjs:167:13) at Object.wrappedValidations. [as xForwardedForHeader] (/opt/node_modules/express-rate-limit/dist/index.cjs:362:22) at Object.keyGenerator (/opt/node_modules/express-rate-limit/dist/index.cjs:617:20) at /opt/node_modules/express-rate-limit/dist/index.cjs:669:32 at /opt/node_modules/express-rate-limit/dist/index.cjs:649:5 { code: 'ERR_ERL_UNEXPECTED_X_FORWARDED_FOR', help: 'https://express-rate-limit.github.io/ERR_ERL_UNEXPECTED_X_FORWARDED_FOR/' }

To Reproduce

I started seeing this after a recent update.

Expected behavior

No errors

Additional context

No response