# Having proxy issues running docker compose

**URL:** <https://community.temporal.io/t/having-proxy-issues-running-docker-compose/1431>\
**Category:** Community Support\
**Created:** [February 2, 2021, 9:12pm UTC](https://community.temporal.io/t/having-proxy-issues-running-docker-compose/1431 "2021-02-02T21:12:49Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![kasi](https://avatars.discourse-cdn.com/v4/letter/k/e19b73/32.png) [@kasi](https://community.temporal.io/u/kasi)\
**Post date:** [February 3, 2021, 10:10pm UTC](https://community.temporal.io/t/having-proxy-issues-running-docker-compose/1431/21 "2021-02-03T22:10:38Z")

</div>

@maxim I am seeing all the services running with dev mode I am able to register namspace and run the program (we looked together), it is UI that fails to come up and throws error message

---

<div class="post-metadata">

**Author:** ![Ruslan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/ruslan/32/66_2.png) [@Ruslan](https://community.temporal.io/u/Ruslan)\
**Post date:** [February 3, 2021, 10:21pm UTC](https://community.temporal.io/t/having-proxy-issues-running-docker-compose/1431/22 "2021-02-03T22:21:49Z")

</div>

are you running web docker on Mac or linux/wsl ?

afaik on Macs you need to start docker passing `host.docker.internal` due to how docker works there [temporal/docker-compose.darwin.yml at 3e9e452d5b491bdaad6f8ed805edfa2b4f61584c · temporalio/temporal · GitHub](https://github.com/temporalio/temporal/blob/3e9e452d5b491bdaad6f8ed805edfa2b4f61584c/.development/docker-compose/docker-compose.darwin.yml#L19)

More info on mac docker networking:

> **[Temporal CLI - tctl | Temporal](https://docs.temporal.io/docs/tctl/#using-the-cli)**
>
> The Temporal CLI is a command-line tool you can use to perform various tasks on a Temporal server. It can perform

> **[Networking features in Docker Desktop for Mac](https://docs.docker.com/docker-for-mac/networking/#use-cases-and-workarounds)**
>
> Networking

---

<div class="post-metadata">

**Author:** ![kasi](https://avatars.discourse-cdn.com/v4/letter/k/e19b73/32.png) [@kasi](https://community.temporal.io/u/kasi)\
**Post date:** [February 3, 2021, 10:33pm UTC](https://community.temporal.io/t/having-proxy-issues-running-docker-compose/1431/23 "2021-02-03T22:33:40Z")

</div>

@Ruslan running on mac thanks will try it out

---

<div class="post-metadata">

**Author:** ![kasi](https://avatars.discourse-cdn.com/v4/letter/k/e19b73/32.png) [@kasi](https://community.temporal.io/u/kasi)\
**Post date:** [February 3, 2021, 10:44pm UTC](https://community.temporal.io/t/having-proxy-issues-running-docker-compose/1431/24 "2021-02-03T22:44:52Z")

</div>

@Ruslan tried it same error,

 ![Screen Shot 2021-02-03 at 2.43.49 PM](https://us1.discourse-cdn.com/flex016/uploads/temporal/original/1X/92b9fd9d07f3ce1983e57329a4183af2f4aa537f.png)

---

<div class="post-metadata">

**Author:** ![Ruslan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/ruslan/32/66_2.png) [@Ruslan](https://community.temporal.io/u/Ruslan)\
**Post date:** [February 3, 2021, 11:48pm UTC](https://community.temporal.io/t/having-proxy-issues-running-docker-compose/1431/25 "2021-02-03T23:48:21Z")

</div>

> [@kasi](#):
>
> temporal | Error Details: rpc error: code = Unavailable desc = connection error: desc = “transport: Error while dialing failed to do connect handshake, response: “HTTP/1.1 407 AuthorizedOnly\r\nContent-Length: 2826\r\nCache-Control: no-cache\r\nContent-Type: text/html\r\nDate: Wed, 03 Feb 2021 18:12:45 GMT\r\nProxy-Authenticate: NTLM\r\nProxy-Authenticate: Basic realm=\“[AEXP.COM](http://AEXP.COM)\”\r\nProxy-Connection: Keep-Alive\r\nX-Frame-Options: deny\r\n\r\n\n\n\n\n\n \n \<meta http-equiv=\“X-UA-Compatible\” content=\“IE=7\” /\>\n McAfee Web Gateway - Notification\n \n \<link rel=\“stylesheet\” href="/mwg-internal/de5fs23hu73ds/files/default/stylesheet.css" /\>\n\n\n\n\n \n \n \n \n

based on this error, it still seems that the McAfee Web Gateway is blocking the requests with the Proxy-Authenticate error. Could you confirm with your IT department and possibly whitelist the traffic?

[Previous page](https://community.temporal.io/t/having-proxy-issues-running-docker-compose/1431.md?page=1)
