# 502 bad gateway when I have directory bind mounted volume **URL:** \ **Category:** PMM 1.x\ **Created:** [October 4, 2018, 12:27pm UTC](https://forums.percona.com/t/502-bad-gateway-when-i-have-directory-bind-mounted-volume/6614 "2018-10-04T12:27:33Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![bplegend](https://avatars.discourse-cdn.com/v4/letter/b/fbc32d/32.png) [@bplegend](https://forums.percona.com/u/bplegend)\ **Post date:** [October 4, 2018, 12:27pm UTC](https://forums.percona.com/t/502-bad-gateway-when-i-have-directory-bind-mounted-volume/6614/1 "2018-10-04T12:27:33Z")
Hi, This is the first time installing PMM. I setup PMM using directory bind mounted volume but it didn’t work. Here is what I did. However if I remove the directory bind mounted volumes. It worked successfully. Does anyone know what I did wrong? * * * $ docker create -v /u01/prometheus/data:/opt/prometheus/data -v /u01/consul-data:/opt/consul-data -v /u01/mysql:/var/lib/mysql -v /u01/grafana:/var/lib/grafana –name pmm-data percona/pmm-server:latest /bin/true 3c3c01a936021646d3a84e239634e044db68d152e79a31a9567d15e00904f7f1 $ docker run -d -p 80:80 –volumes-from pmm-data –name pmm-server –restart always percona/pmm-server:latest 868800a9f2e8c32fd2cc883847c4a81bafa97e794c1344aeb43b1e2f3ea26e9c $ curl [url][http://localhost/ping[/url]](http://localhost/ping%5B/url%5D) 502 Bad Gateway # 502 Bad Gateway * * * nginx ---
**Author:** ![Michael\_Coburn](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/michael_coburn/32/18_2.png) [@Michael\_Coburn](https://forums.percona.com/u/Michael_Coburn)\ **Post date:** [October 8, 2018, 11:55am UTC](https://forums.percona.com/t/502-bad-gateway-when-i-have-directory-bind-mounted-volume/6614/2 "2018-10-08T11:55:45Z")
Hi [bplegend](https://percona.vanillacommunities.com/profile/x/x/27748) Can you load the Prometheus dashboard at all? if so, please share with us the logs.zip file If you cannot, can you get the contents from /var/log/nginx.log , then we can troubleshoot what is going on with the proxy web instance. I’d encourage you also to look through the other logs in /var/log - there might be a clue there.