# Deploying Portainer behind nginx reverse proxy ## Deploying in a Docker Standalone scenario To deploy Portainer behind an nginx proxy in a Docker standalone scenario you must use a Docker Compose file. In the following docker-compose.yml you will find the configuration of the nginx proxy and the Portainer Server. {% hint style="info" %} This example uses the excellent [nginxproxy/nginx-proxy](https://hub.docker.com/r/nginxproxy/nginx-proxy) image as the proxy container, which requires no additional configuration beyond the two environment variables added to the `portainer` container's definition. {% endhint %} {% tabs %} {% tab title="Business Edition" %} ``` version: "2" services: nginx-proxy: image: nginxproxy/nginx-proxy restart: always ports: - "80:80" volumes: - "/var/run/docker.sock:/tmp/docker.sock:ro" portainer: image: portainer/portainer-ee:sts command: -H unix:///var/run/docker.sock restart: always environment: - VIRTUAL_HOST=portainer.yourdomain.com - VIRTUAL_PORT=9000 ports: - 8000:8000 volumes: - /var/run/docker.sock:/var/run/docker.sock - portainer_data:/data volumes: portainer_data: ``` {% endtab %} {% tab title="Community Edition" %} ``` version: "2" services: nginx-proxy: image: nginxproxy/nginx-proxy restart: always ports: - "80:80" volumes: - "/var/run/docker.sock:/tmp/docker.sock:ro" portainer: image: portainer/portainer-ce:sts command: -H unix:///var/run/docker.sock restart: always environment: - VIRTUAL_HOST=portainer.yourdomain.com - VIRTUAL_PORT=9000 ports: - 8000:8000 volumes: - /var/run/docker.sock:/var/run/docker.sock - portainer_data:/data volumes: portainer_data: ``` {% endtab %} {% endtabs %} To start working with this recipe, change the `VIRTUAL_HOST` value then deploy Portainer by running the following: ``` docker-compose up -d ``` When this has finished, run `docker ps` . You should see an output similar to this: ``` CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 8c8f2eac7c9a portainer/portainer-ee:sts "/portainer -H unix:…" 4 minutes ago Up 4 minutes 9000/tcp, 0.0.0.0:8000->8000/tcp, :::8000->8000/tcp, 9443/tcp portainer_portainer_1 3e7c8b5d71d7 nginxproxy/nginx-proxy "/app/docker-entrypo…" 4 minutes ago Up 4 minutes 0.0.0.0:80->80/tcp, :::80->80/tcp portainer_nginx-proxy_1 ``` Once the deployment has finished you can browse `portainer.yourdomain.com`. ## Deploying in a Docker Swarm scenario Deploying Portainer in Docker Swarm behind nginx has similar steps to the Docker Standalone scenario. Before deploying, you need to create two elements: networks and volumes. {% hint style="warning" %} This deployment assumes you are running one manager node. If you are using multiple managers we advise [reading this article](/faqs/installing/how-can-i-ensure-portainers-configuration-is-retained.md) before proceeding. {% endhint %} First, create two networks: * One for the agent and the communication with the Portainer Server. * One to 'expose' the Portainer container to the same network as the reverse proxy. ``` docker network create -d overlay proxy ``` ``` docker network create -d overlay agent_network ``` Next, create the volume: ``` docker volume create portainer_data ``` And finally, save the following recipe as `portainer.yml`: {% tabs %} {% tab title="Business Edition" %} ``` version: '3.2' services: nginx-proxy: image: nginxproxy/nginx-proxy networks: - proxy ports: - "80:80" volumes: - "/var/run/docker.sock:/tmp/docker.sock:ro" - "./vhost.d:/etc/nginx/vhost.d:ro" agent: image: portainer/agent:sts environment: # REQUIRED: Should be equal to the service name prefixed by "tasks." when # deployed inside an overlay network AGENT_CLUSTER_ADDR: tasks.agent # AGENT_PORT: 9001 # LOG_LEVEL: DEBUG volumes: - /var/run/docker.sock:/var/run/docker.sock - /var/lib/docker/volumes:/var/lib/docker/volumes networks: - agent_network deploy: mode: global placement: constraints: [node.platform.os == linux] portainer: image: portainer/portainer-ee:sts command: -H tcp://tasks.agent:9001 --tlsskipverify volumes: - data:/data environment: - VIRTUAL_HOST=portainer.yourdomain.com - VIRTUAL_PORT=9000 ports: - 8000:8000 networks: - proxy - agent_network deploy: mode: replicated replicas: 1 placement: constraints: [node.role == manager] networks: proxy: external: true agent_network: external: true volumes: data: ``` {% endtab %} {% tab title="Community Edition" %} ``` version: '3.2' services: nginx-proxy: image: nginxproxy/nginx-proxy networks: - proxy ports: - "80:80" volumes: - "/var/run/docker.sock:/tmp/docker.sock:ro" - "./vhost.d:/etc/nginx/vhost.d:ro" agent: image: portainer/agent:sts environment: # REQUIRED: Should be equal to the service name prefixed by "tasks." when # deployed inside an overlay network AGENT_CLUSTER_ADDR: tasks.agent # AGENT_PORT: 9001 # LOG_LEVEL: DEBUG volumes: - /var/run/docker.sock:/var/run/docker.sock - /var/lib/docker/volumes:/var/lib/docker/volumes networks: - agent_network deploy: mode: global placement: constraints: [node.platform.os == linux] portainer: image: portainer/portainer-ce:sts command: -H tcp://tasks.agent:9001 --tlsskipverify volumes: - data:/data environment: - VIRTUAL_HOST=portainer.yourdomain.com - VIRTUAL_PORT=9000 ports: - 8000:8000 networks: - proxy - agent_network deploy: mode: replicated replicas: 1 placement: constraints: [node.role == manager] networks: proxy: external: true agent_network: external: true volumes: data: ``` {% endtab %} {% endtabs %} To start working with this recipe, change the `VIRTUAL_HOST` value then deploy Portainer by running the following: ``` docker stack deploy portainer -c portainer.yml ``` To check the deployment, run `docker service ls`. You should see an output similar to the following: ``` ID NAME MODE REPLICAS IMAGE PORTS gy2bjxid0g4p portainer_agent global 1/1 portainer/agent:sts jwvjp5bux4sz portainer_nginx-proxy replicated 1/1 nginxproxy/nginx-proxy:latest *:80->80/tcp 5nflcvoxl3c7 portainer_portainer replicated 1/1 portainer/portainer-ee:sts *:8000->8000/tcp ``` Once the services are running, you will be able to access Portainer from the URL you defined earlier, for example: `portainer.yourdomain.com`. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.portainer.io/advanced/reverse-proxy/nginx.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.