Skip to content
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

[ActionDispatch::HostAuthorization::DefaultResponseApp] Blocked host: XXX #56

Open
vmptk opened this issue Mar 17, 2023 · 1 comment
Open

Comments

@vmptk
Copy link

vmptk commented Mar 17, 2023

Mastodon web logs are full of blocking log entries:

[ActionDispatch::HostAuthorization::DefaultResponseApp] Blocked host: 10.1.149.159
[ActionDispatch::HostAuthorization::DefaultResponseApp] Blocked host: 10.1.145.207
[ActionDispatch::HostAuthorization::DefaultResponseApp] Blocked host: 10.1.154.2
[ActionDispatch::HostAuthorization::DefaultResponseApp] Blocked host: 10.1.174.212

Those addresses are the K8S node assigned private addresses. The whole subnet had been added in env variables:

  • TRUSTED_PROXY_IP : 10.0.0.0/8,
  • ALLOWED_PRIVATE_ADDRESSES : 10.0.0.0/8,

Any ideas on how to resolve that issue?

@ndebuhr
Copy link

ndebuhr commented Feb 23, 2024

Adding the following environment variable worked for me - seems the docker container will only accept requests from LOCAL_DOMAIN:

  extraEnvVars:
    LOCAL_DOMAIN: your.domain.example.com

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants