Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'X-Forwarded-For' header #1514

Closed
HyperCriSiS opened this issue Mar 25, 2025 · 1 comment
Closed

'X-Forwarded-For' header #1514

HyperCriSiS opened this issue Mar 25, 2025 · 1 comment

Comments

@HyperCriSiS
Copy link

Description

Hi,

I saw this in the log when starting the docker container. (HA Addon).
What's the issue here?

Thanks
Hyper

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 (file:///usr/src/app/node_modules/express-rate-limit/dist/index.mjs:159:13)
    at wrappedValidations.<computed> [as xForwardedForHeader] (file:///usr/src/app/node_modules/express-rate-limit/dist/index.mjs:370:22)
    at Object.keyGenerator (file:///usr/src/app/node_modules/express-rate-limit/dist/index.mjs:643:20)
    at file:///usr/src/app/node_modules/express-rate-limit/dist/index.mjs:696:32
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async file:///usr/src/app/node_modules/express-rate-limit/dist/index.mjs:676:5 {
  code: 'ERR_ERL_UNEXPECTED_X_FORWARDED_FOR',
  help: 'https://express-rate-limit.github.io/ERR_ERL_UNEXPECTED_X_FORWARDED_FOR/'
}

TriliumNext Version

0.92.4

What operating system are you using?

Other Linux

What is your setup?

Local + server sync

Operating System Version

Trilium Notes as HA Addon

Error logs

No response

@eliandoran
Copy link
Contributor

If you are using Trilium behind a reverse proxy, you would have to configure trustedReverseProxy in config.ini.

@TriliumNext TriliumNext locked and limited conversation to collaborators Mar 25, 2025
@eliandoran eliandoran converted this issue into discussion #1522 Mar 25, 2025

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants