[{"_1":2,"_160":-5,"_161":-5},"loaderData",{"_3":4,"_17":18,"_25":26,"_139":140},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7,"_13":14,"_15":16},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","theme","system","contrast","normal","routes/_layout",{"_19":-5,"_20":21,"_22":21,"_23":11,"_24":21},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_27":28,"_29":-5,"_30":11,"_31":11,"_32":33,"_34":35,"_36":-5,"_37":11,"_38":39,"_88":-5,"_89":90,"_128":-5,"_129":11,"_130":21,"_131":11,"_132":-5,"_133":11,"_134":-5,"_135":136,"_137":91,"_138":-7},"canonicalUrl","https://hub.docker.com/r/nurzhanme/nginx_proxy/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","nurzhanme","reponame","nginx_proxy","cloudBuildSource","isAutobuildsAvailable","repo",{"_40":41,"_42":43,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":55,"_57":35,"_32":33,"_58":59,"_60":44,"_61":62,"_63":64,"_65":66,"_67":-5,"_68":62,"_69":70,"_71":11,"_72":33,"_73":74,"_79":11,"_80":81,"_85":33,"_86":87},"categories",[],"content_types",[44],"image","date_registered","2021-03-31T06:04:49.015347Z","description","","is_private","last_updated","2021-04-02T12:59:40.751552Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[56],"application/vnd.docker.container.image.v1+json","name","pull_count",224,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","# Nginx forward proxy\n\n[Nginx](https://nginx.org/en/) is a very fast HTTP and reverse proxy server. \nUsually, Nginx is used to serve and cache static assets or as proxy or load balancer for incoming traffic to application servers. In this repository, it is used as forward proxy. \n\n## Use Case\n\nAssume you have a network where you want to control outgoing traffic. \nYou either want to: \n\n - Deny all outgoing calls by default and only allow HTTP(S) calls to whitelisted URLs.\n - Allow all outgoing calls by default and only block HTTP(S) calls to blacklisted URLs.\n\nThe Docker daemon can be configured that way that it routes all traffic through an proxy. This proxy can be an Nginx which is configured as forwarding proxying.\n\n## ngx\\_http\\_proxy\\_connect\\_module\n\nNginx can be configured for forwarding proxying. \nUnfortunately, that doesn't work very well with HTTPS connections. \nAs soon the user is calling a URL via https, Nginx will throw errors. \nThere is a [StackOverflow issue](https://superuser.com/questions/604352/nginx-as-forward-proxy-for-https)\nto that topic. Luckily there is a solution for that problem. \nThe [ngx\\_http\\_proxy\\_connect\\_module](https://github.com/chobits/ngx_http_proxy_connect_module)\nis solving this issue. If Nginx is compiled with that module, \nthe proxying will work with SSL connections as well. \n\n## Docker Build\n\nThe Dockerfile in this repository is assembling an Nginx with the [ngx\\_http\\_proxy\\_connect\\_module](https://github.com/chobits/ngx_http_proxy_connect_module)\nand an nginx.conf file which blocks all outgoing traffic by default, \nbut allows access to some whitelisted domains like google.com.\nThe Docker image can be built like this: \n\n```\ndocker build -t reiz/nginx_proxy:0.0.3 . \n```\n\nOr simply download it from [Docker Hub](https://hub.docker.com/r/reiz/nginx_proxy/) with: \n\n```\ndocker pull reiz/nginx_proxy:0.0.3\n```\n\n## Whitelist certain domains\n\nThis repository contains two nginx configuration files. \nThe `nginx_whitelist.conf` file is built for the use case that you want to deny all outgoing traffic by default and only allow some whitelisted domains. \nIn the first server section domains can be whitelisted by simply adding a \n`server_name *` line for each whitelisted domain. Here an example: \n\n```\n # Whitelist Google\n server {\n listen 8888;\n server_name google.com;\n server_name *.google.com;\n server_name google.de;\n server_name www.google.de;\n proxy_connect;\n proxy_max_temp_file_size 0;\n resolver 8.8.8.8;\n location / {\n proxy_pass http://$http_host;\n proxy_set_header Host $http_host;\n }\n }\n```\n\nRegex can be used to describe a domain. This `*.google.com` for example is whitelisting all subdomains of google.com. In the above example, google.com and all subdomains of it are whitelisted. Beside that google.de and www.google.de are whitelisted. Subdomains of google.de are **not** whitelisted. \nThe proxy would allow outgoing calls to this domains: \n\n - google.com\n - www.google.com\n - mail.google.com\n - api.google.com\n - google.de\n - www.google.de\n \nThis domains are blocked with the above configuration: \n \n - mail.google.de\n - api.google.de\n\nBy starting the Docker container the file can be mounted into the running container. \n\n```\ndocker run -d -p 8888:8888 -v ${PWD}/nginx_whitelist.conf:/usr/local/nginx/conf/nginx.conf reiz/nginx_proxy:0.0.3 \n```\n\nNow the Docker container is running with the mounted configuration.\n\n## Blacklist certain domains\n\nThis repository contains two nginx configuration files. \nThe `nginx_blacklist.conf` file is built for the use case that you want to allow all outgoing traffic by default and only block traffic to some domains. \nIn the first server section domains can be blacklisted by simply adding a \n`server_name *` line for each blacklisted domain. Here an example: \n\n```\n server {\n listen 8888;\n server_name google.com;\n server_name *.google.com;\n return 404;\n }\n```\n\nIn the example above all pages would be accessible, but google.com and all subdomains of it would be blocked. Regex can be used here in the same way as in the whitelist example. \nBy starting the Docker container the file can be mounted into the running container. \n\n```\ndocker run -d -p 8888:8888 -v ${PWD}/nginx_whitelist.conf:/usr/local/nginx/conf/nginx.conf reiz/nginx_proxy:0.0.1 \n```\n\nNow the Docker container is running with the mounted configuration.\n\n## Testing\n\nYou can test your configuration by pointing your Browser to the Nginx proxy in the running Docker container. \nIf you run the Docker container on your localhost, then you can point your Browser to `localhost:8888`. \nHere is an example how it looks like in Firefox: \n\n![Firefox Proxy Settings](images/Firefox-Proxy-Settings.png)\n\n## Configuring Docker and Kubernetes with a Proxy\n\nAssuming you have a cluster of Docker machines (Kubernetes cluster)\nand you would like to route all outgoing traffic to your proxy. \nThat can be achieved by setting some global ENV variables on each Docker machine. \n\nFor RedHat/CentOS version 6:\n\n```shell\ncat <\nEOF\n \nsudo service docker restart\n```\n\nFor RedHat/CentOS version 7, remove export:\n\n```shell\ncat <\nEOF\n \nsudo sed -i '/\\[Service\\]/a EnvironmentFile=/etc/sysconfig/docker' /usr/lib/systemd/system/docker.service\nsudo systemctl daemon-reload\nsudo service docker restart\n```\n\nFor Ubuntu 14.04:\n\n```shell\ncat <\nEOF\n \nsudo restart docker\n```\n\nFor Kubernetes it works the same way. \nThe `http_proxy` ENV has to be set before the K8S processes are starting.\nMinikube can be started with proxy params directly.\nHere an example: \n\n```shell\nhttps_proxy=http://:80 minikube start --docker-env HTTP_PROXY=http://:80 --docker-env HTTPS_PROXY=http://:80 --docker-env NO_PROXY=192.168.99.0/24\n```\n\nAlternatively the Proxy can be set by Container start as well: \n\n```shell\ndocker run -e \"http_proxy=http://myproxy.example.com:8888\" \\\n -e \"https_proxy=https://myproxy.example.com:8888\" \\\n -d liveperson\\app run.sh\n```\n\n\n\n","has_starred","hub_user","immutable_tags_settings",{"_75":11,"_76":77},"enabled","rules",[78],".*","is_automated","permissions",{"_82":21,"_83":11,"_84":11},"read","write","admin","user","storage_size",324518147,"orgData","recentTags",[91],{"_92":44,"_93":94,"_95":96,"_97":98,"_99":100,"_50":117,"_118":94,"_119":33,"_120":56,"_57":121,"_122":123,"_124":108,"_125":117,"_126":66,"_127":21},"content_type","creator",3725388,"full_size",176535454,"id",143703727,"images",[101],{"_102":103,"_104":105,"_106":48,"_107":108,"_109":110,"_111":112,"_113":48,"_114":-5,"_115":96,"_63":66,"_116":-5},"architecture","amd64","digest","sha256:3d12043b3c4706d5f66f073857223326c8466aec88adbaa0369da69adc72ac9a","features","last_pulled","2026-09-26T15:17:52.72066486Z","last_pushed","2021-04-02T10:33:34Z","os","linux","os_features","os_version","size","variant","2021-04-02T12:59:40.476299Z","last_updater","last_updater_username","media_type","latest","repository",12016513,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"selectedTag","attestationsUrl","routes/_layout.r.$namespace.$reponame.tags",{"_38":141,"_148":149,"_135":158,"_159":11},{"_40":142,"_42":143,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":144,"_57":35,"_32":33,"_58":59,"_60":44,"_61":62,"_63":64,"_65":66,"_67":-5,"_68":62,"_69":70,"_71":11,"_72":33,"_73":145,"_79":11,"_80":147,"_85":33,"_86":87},[],[44],[56],{"_75":11,"_76":146},[78],{"_82":21,"_83":11,"_84":11},"tags",{"_150":64,"_151":-5,"_152":-5,"_153":154},"count","next","previous","results",[155],{"_92":44,"_93":94,"_95":96,"_97":98,"_99":156,"_50":117,"_118":94,"_119":33,"_120":56,"_57":121,"_122":123,"_124":108,"_125":117,"_126":66,"_127":21},[157],{"_102":103,"_104":105,"_106":48,"_107":108,"_109":110,"_111":112,"_113":48,"_114":-5,"_115":96,"_63":66,"_116":-5},[],"canDeleteTags","actionData","errors"]

nurzhanme/nginx_proxy

Tags for nurzhanme/nginx_proxy