How to bypass Cloudflare security with HTTP Request

Questions
5

:white_check_mark: [SOLVED] Use Dockerized Squid Proxy with n8n to Bypass Cloudflare in http get node

:warning: Problem

When using HTTP Request node in n8n to access APIs protected by Cloudflare (e.g., AbuseIPDB, HaveIBeenPwned, etc.), requests often fail with:

403 Forbidden / Access Denied / Cloudflare DDoS Challenge

:light_bulb: Solution

You can route your requests through a lightweight, Dockerized Squid proxy server to bypass rate limiting and bot protection.

:wrench: Setup Instructions

1. Create squid.conf

http_port 3128

acl localnet src 172.0.0.0/8
acl localnet src 192.168.0.0/16
acl localnet src 10.0.0.0/8
acl localnet src 172.18.0.0/16
acl localhost src 127.0.0.1/32

acl SSL_ports port 443
acl Safe_ports port 80
acl Safe_ports port 443
acl Safe_ports port 1025-65535

acl CONNECT method CONNECT

http_access deny !Safe_ports
http_access deny CONNECT !SSL_ports

http_access allow localnet
http_access allow localhost

http_access deny all

icp_port 0
access_log /var/log/squid/access.log squid

Save it to:
:file_folder: /root/squid/squid.conf

2. Run Squid in Docker

docker run -d --name squid-proxy   -p 3128:3128   -v /root/squid/squid.conf:/etc/squid/squid.conf:ro   sameersbn/squid

Confirm it’s running:

docker ps

3. Test Proxy

From n8n container test with curl (in my case im testing on abuseipdb cloudflare protected) :

curl -x http://<YOUR-HOST-IP>:3128 https://api.abuseipdb.com

You can also use this in your HTTP Request node by setting the Proxy field:

http://<YOUR-HOST-IP>:3128

:white_check_mark: Tips

  • Make sure your Docker subnet (e.g. 172.18.0.0/16) is included in the ACLs.
  • Host IP can be found via: ip addr show eth0
  • Adjust logging for debugging via Squid logs:
docker logs squid-proxy

:speech_balloon: Community Note

This helped me bypass Cloudflare API blocks on abuseipdb in my n8n workflow running on a Hostinger KVM. Let me know if you face any issues!

i’ve found it via googling and lilbit chatgpt.