Hello everyone, I’m encountering a configuration issue between my QNAP (QTS) and Nginx Proxy Manager (NPM), which is rendering my Fail2ban (or QTS access protection) ineffective against brute-force attacks. My configuration: QNAP (QTS): Local IP 192.168.10.10 (I changed it to a standard RFC1918 I…

Sounds like this [image] Qnap NAS hinter einem Reverse Proxy - NAS Hilfe und Support Forum Hallo zusammen, ich betreibe einen Caddy Reverse Proxy, über den ich mein NAS, samt SSL-Zertifikat erreichbar mache. Grundsätzlich funktioniert der Zugriff. Jedoch scheint jemand mich brute forcen…

Yes, that’s right, unfortunately no solution is provided. Actually, NPM does see the IP address, but when testing users with fake passwords, the failures aren’t visible in NPM. With QNAP, the failed attempts are visible, but they appear with NPM’s internal IP address. 2025-11-04T21:24:51+01:00 NAS…

If you have a firewall in place like opnsense/pfsense you can limit access coming in that way you get less potential attacks. IDK how to use npm to do what you want, but on the FW you can setup rules to block sets of IP and/or let in a certain set of ip etc. External attacks are reason why i dont …

This solution is too restrictive, which is a shame because QNAP offers solutions, but we hold back for fear of hacking. Adding VPNs to all QNAP clients would be unmanageable. I created a script that correlates the IP addresses in the QNAP logs with the IP address of the device trying to connect via …

[QTS + Nginx Proxy Manager] Source IP address lost

English Networking

dolbyman November 4, 2025, 8:38pm 2

Sounds like this

Same user ?