# \[SERVER\] Set FrontEnd IP on Worker Service

**URL:** <https://community.temporal.io/t/server-set-frontend-ip-on-worker-service/2489>\
**Category:** Community Support\
**Tags:** server\
**Created:** [July 2, 2021, 4:34am UTC](https://community.temporal.io/t/server-set-frontend-ip-on-worker-service/2489 "2021-07-02T04:34:34Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Shawn\_Lim](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/shawn_lim/32/1029_2.png) [@Shawn\_Lim](https://community.temporal.io/u/Shawn_Lim)\
**Post date:** [July 2, 2021, 10:26am UTC](https://community.temporal.io/t/server-set-frontend-ip-on-worker-service/2489/2 "2021-07-02T10:26:28Z")

</div>

> [@Error starting temporal-sys-tq-scanner-workflow workflow](https://community.temporal.io/t/error-starting-temporal-sys-tq-scanner-workflow-workflow/271):
>
> I’ve set-up a temporal cluster where I’m running 2 instances of each role (frontend, history, matching & worker) and able to successfully execute a workflow but I’ve come across lot of error messages from worker instances I’ve debugged a bit and figured out that it is trying to connect to front-end port on the same instance (which is running only worker service). Any idea why this is happening ? 172.16.29.254 is the ip of the same worker instance.

Apparently setting `PUBLIC_FRONTEND_ADDRESS` makes the problem go away. But why? I thought that the worker should automatically detect the private IP of the frontend service and talk to it.

---

_[View the full topic](https://community.temporal.io/t/server-set-frontend-ip-on-worker-service/2489)._