mjhjmtu

Here is a link to my relevant configuration
https://github.com/TheGlitchr/acidbox
I'm trying to create a deployable webstack for my own user that's easy to migrate and recreate without data loss while being really secure. So what I am doing is creating a network in docker, where each container is labeled in dns (managed by docker).

I have already tried specifying differing IPs in my caddyfile, the only one that seems to work is my public ip, that is the only way caddy can reach the container (despite being within the same docker subnet)

Specific Error

2018-05-03T15:21:48.050103440Z 03/May/2018:15:21:48 +0000 [ERROR 502 /] dial tcp 172.18.0.8:8080: connect: connection refused
2018-05-03T15:21:50.103522028Z 03/May/2018:15:21:50 +0000 [ERROR 502 /] dial tcp 172.18.0.8:8080: connect: connection refused
2018-05-03T15:21:50.351625626Z 03/May/2018:15:21:50 +0000 [ERROR 502 /index.php] dial tcp 172.18.0.8:8080: connect: connection refused
2018-05-03T15:21:50.841226782Z 03/May/2018:15:21:50 +0000 [ERROR 502 /] dial tcp 172.18.0.8:8080: connect: connection refused
2018-05-03T15:21:51.030022667Z 03/May/2018:15:21:51 +0000 [ERROR 502 /index.php] dial tcp 172.18.0.8:8080: connect: connection refused
2018-05-03T15:21:51.320559407Z 03/May/2018:15:21:51 +0000 [ERROR 502 /] dial tcp 172.18.0.8:8080: connect: connection refused
2018-05-03T15:21:51.453915152Z 03/May/2018:15:21:51 +0000 [ERROR 502 /index.php] dial tcp 172.18.0.8:8080: connect: connection refused

By the log above, I can tell the dns is working, because I have the containers listed by their dns name, and here it's shown resolved as the ip, I believe it's a communication error either between docker containers themselves or the way caddy is trying to proxy these services.