<p>Sure, you put in as many proxies as you need. You don't want to over-complicate things, but it seems you have a good reason for your architecture.</p>

CC BY-SA 4.0
2018-12-18T06:58:47.490Z
2018-12-18T06:58:47.490Z
Xiong Chiamiov
<p>Production configurations often involve multiple levels of proxies.  Each should provide a place for gathering stats.  Proxies can also hide backend failures if you have a pool of nodes behind the proxy, which doesn't seem to be what you're going for here.</p>

<p>Your comment that you wouldn't be able to renew certificates with extra proxies is not correct.  You can update certs via DNS auth then deploy to your proxies through whatever mechanism you're already happy with.</p>

CC BY-SA 4.0
2018-12-18T19:45:40.027Z
2018-12-18T19:45:40.027Z
chicks
<p>One nginx server on host machine with renewable certificate (via certbot).
And another nginx server inside docker container.
First one should redirect all traffic to the second one.</p>

<p>Currently I have one nginx service inside container and I connect certificates that stored on host to that server via volumes. But with this kind of setup I can't renew certificates automatically...</p>

<docker><nginx>
Is this okay to use double proxy-server setup (on host and in container) on one machine?
aiven
# Is this okay to use double proxy-server setup (on host and in container) on one machine?

(Asked by: username_0 on 2018-12-17)

One nginx server on host machine with renewable certificate (via certbot).
And another nginx server inside docker container.
First one should redirect all traffic to the second one.

Currently I have one nginx service inside container and I connect certificates that stored on host to that server via volumes. But with this kind of setup I can't renew certificates automatically...

**Tags:** docker, nginx


---

## 2 answers

### Answer by username_1 on 2018-12-18. Score: 1

Sure, you put in as many proxies as you need. You don't want to over-complicate things, but it seems you have a good reason for your architecture.


---

### Answer by username_2 on 2018-12-18. Score: 1

Production configurations often involve multiple levels of proxies. Each should provide a place for gathering stats. Proxies can also hide backend failures if you have a pool of nodes behind the proxy, which doesn't seem to be what you're going for here.

Your comment that you wouldn't be able to renew certificates with extra proxies is not correct. You can update certs via DNS auth then deploy to your proxies through whatever mechanism you're already happy with.


---

