Hey @browse,
I can provide you with the steps that I use for testing but it should be considered as just a test environment and for something that you plan to use in production it would be worth investigating a safer configuration.
This assumes you have your SSL certificate under ~/squidcert.pem, If you plan to use a self signed certificate there is more risk involved.
squid.conf
http_port 3128
https_port 3129 cert=/etc/squid/proxy.pem
dns_v4_first on
acl localnet src 10.0.0.0/8 # RFC1918 possible internal network
acl localnet src 172.16.0.0/12 # RFC1918 possible internal network
acl localnet src 192.168.0.0/16 # RFC1918 possible internal network
acl localnet src fc00::/7 # RFC 4193 local private network range
acl localnet src fe80::/10 # RFC 4291 link-local (directly plugged) machines
acl CONNECT method CONNECT
http_access allow localnet
http_access allow localhost
Docker Compose
version: '3.8'
services:
squid:
image: sysdignathan/secure-squid:latest
ports:
- "3128:3128"
- "3129:3129"
volumes:
- ~/squid.conf:/etc/squid/squid.conf
- ~/squidcert.pem:/etc/squid/proxy.pem
- ~/squidlogs:/var/log/squid
n8n Env
http_proxy=http://squid:3128
http_proxy=https://squid:3129