# Worker trying to connect to old frontend?

**URL:** <https://community.temporal.io/t/worker-trying-to-connect-to-old-frontend/6884>\
**Category:** Community Support\
**Created:** [January 10, 2023, 12:06am UTC](https://community.temporal.io/t/worker-trying-to-connect-to-old-frontend/6884 "2023-01-10T00:06:31Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![RichRM](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/richrm/32/3640_2.png) [@RichRM](https://community.temporal.io/u/RichRM)\
**Post date:** [January 10, 2023, 12:06am UTC](https://community.temporal.io/t/worker-trying-to-connect-to-old-frontend/6884/1 "2023-01-10T00:06:31Z")

</div>

Our worker services are struggling to start with errors like:

```auto
{"level":"fatal","ts":"2023-01-09T23:45:59.585Z","msg":"error creating sdk client","service":"worker","error":"failed reaching server: last connection error: connection error: desc = \"transport: Error while dialing dial tcp 10.0.11.207:7233: connect: connection refused\"","logging-call-

```

That looks like an old IP address of a frontend service. The actual running frontend is on a different IP address.

Running the following tcl (I think) indicates that 356 services are registered (only 3 are running, heh). I think these are old registrations from where I was trial-and-erroring getting the services stood up:

```auto
tctl admin membership list_db | grep role | wc -l
     356

```

Is there some way to “purge” the list of registered servers, so that the worker can connect to one that’s actually alive? Or do I need to wait for them to timeout?

Many thanks

---

<div class="post-metadata">

**Author:** ![RichRM](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/richrm/32/3640_2.png) [@RichRM](https://community.temporal.io/u/RichRM)\
**Post date:** [January 10, 2023, 12:17am UTC](https://community.temporal.io/t/worker-trying-to-connect-to-old-frontend/6884/2 "2023-01-10T00:17:57Z")

</div>

Although not 100% on that theory, because I also see this in the logs, which is the correct IP of the frontend 🤔

```auto
{"level":"info","ts":"2023-01-10T00:16:02.876Z","msg":"Current reachable members","service":"worker","component":"service-resolver","service":"frontend","addresses":["10.0.11.215:7233"],"logging-call-at":"rpServiceResolver.go:283"}

```

Not sure what its missing as matcher/history connect OK.

I think it’s trying to connect to a frontend service on its own IP (even tho its not running a frontend) instead of using the one that’s already running 🤔

---

<div class="post-metadata">

**Author:** ![RichRM](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/richrm/32/3640_2.png) [@RichRM](https://community.temporal.io/u/RichRM)\
**Post date:** [January 10, 2023, 12:47am UTC](https://community.temporal.io/t/worker-trying-to-connect-to-old-frontend/6884/3 "2023-01-10T00:47:52Z")

</div>

nvm, setting the PUBLIC\_FRONTEND\_ADDRESS var helped steer this.

The only strange thing now is the worker says this

```auto
"service":"worker","component":"worker","address":"10.0.12.188:7239",

```

But refuses all TCP connections on port 7239