2024-06-19, 06:47 PM
Okay, cool, sounds like my thinking may be directionally correct! I've set up Nginx Proxy Manager just so that I have a frontend to configure the reverse proxy under the hood and I think the IPs are forwarding as expected. Here's a paste from my config which matches the JF docs.
# Proxy main Jellyfin traffic
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-Protocol $scheme;
proxy_set_header X-Forwarded-Host $http_host;
proxy_headers_hash_max_size 2048;
proxy_headers_hash_bucket_size 128;
In the JF logs, the right IPs are being captured, so I am assuming that those headers are correct. Subsequently F2B is extracting those IPs from the logs and using them to set the IPTables on the host. But, at the host level I'm not getting a match when I refresh the JF pages to test if the ban worked.... So so strange.
# Proxy main Jellyfin traffic
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-Protocol $scheme;
proxy_set_header X-Forwarded-Host $http_host;
proxy_headers_hash_max_size 2048;
proxy_headers_hash_bucket_size 128;
In the JF logs, the right IPs are being captured, so I am assuming that those headers are correct. Subsequently F2B is extracting those IPs from the logs and using them to set the IPTables on the host. But, at the host level I'm not getting a match when I refresh the JF pages to test if the ban worked.... So so strange.