# Adding port to Intercept or Host adds another terminator

**URL:** <https://openziti.discourse.group/t/adding-port-to-intercept-or-host-adds-another-terminator/852>\
**Category:** General Questions\
**Created:** [November 5, 2022, 7:55pm UTC](https://openziti.discourse.group/t/adding-port-to-intercept-or-host-adds-another-terminator/852 "2022-11-05T19:55:08Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![gooseleggs](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/gooseleggs/32/450_2.png) [@gooseleggs](https://openziti.discourse.group/u/gooseleggs)\
**Post date:** [November 5, 2022, 7:55pm UTC](https://openziti.discourse.group/t/adding-port-to-intercept-or-host-adds-another-terminator/852/1 "2022-11-05T19:55:08Z")

</div>

I have a ziti overlay where I have a controller, console, edge router, edge tunnel and ZEDW. For this, I have an edge tunnel running on linux (dont think this is relevant).

I have a service pointing to the terminator on Linux, which will go through edge router. On the service (pointing to the linux edge tunnel) I have SSH and HTTP enabled. That is fine and all works. However, when I add a port to the intercept or if I have a port to the host configuration, I end up with another terminator (additional two when configuring all up). However, if I delete the service, and then recreate after I add the configs, I get one terminator for all the services (it deletes the three and then creates one). I was expecting that the terminator would be modified or replaced with an updated version as opposed to adding more. For this, I did this through the ZAC so may be different on the command line.

So, here, is the result after I added 9392 to the bind/intercept configurations

```auto
ziti@f39c5a9a35ef:/openziti$ ziti edge list terminators
╭──────┬──────────────────┬────────────────────────────────┬─────────┬─────────────────────────────────────────────┬──────────┬──────┬────────────┬──────────────╮
│ ID │ SERVICE │ ROUTER │ BINDING │ ADDRESS │ IDENTITY │ COST │ PRECEDENCE │ DYNAMIC COST │
├──────┼──────────────────┼────────────────────────────────┼─────────┼─────────────────────────────────────────────┼──────────┼──────┼────────────┼──────────────┤
│ 8YXO │ ltvulscan01.svc │ zitiedgerouter.thesmithcave.nz │ edge │ hosted:9b25d875-e423-468e-8d33-8ce58110db3f │ │ 0 │ default │ 2 │
│ de4n │ ltvulscan01.svc │ zitiedgerouter.thesmithcave.nz │ edge │ hosted:909c7ea3-2d4f-48b9-ae14-0204853ccda6 │ │ 0 │ default │ 20 │
│ dl28 │ ltvulscan01.svc │ zitiedgerouter.thesmithcave.nz │ edge │ hosted:2ed6baeb-a105-4b36-b13b-3fc67a6ffd7f │ │ 0 │ default │ 2 │
╰──────┴──────────────────┴────────────────────────────────┴─────────┴─────────────────────────────────────────────┴──────────┴──────┴────────────┴──────────────╯

```

```auto
ziti@f39c5a9a35ef:/openziti$ ziti edge list services   
╭────────────┬──────────────────┬────────────┬─────────────────────┬────────────╮
│ ID │ NAME │ ENCRYPTION │ TERMINATOR STRATEGY │ ATTRIBUTES │
│ │ │ REQUIRED │ │ │
├────────────┼──────────────────┼────────────┼─────────────────────┼────────────┤
│ av6FtKfKTW │ ltvulscan01.svc │ true │ smartrouting │ │
╰────────────┴──────────────────┴────────────┴─────────────────────┴────────────╯

```

I cannot find the other commands I want, so here are some screenshots. Now I first came across this issue when I added port 80 alongside of port 22, so I deleted the service and re-created and then only got one terminator. So, all of this post shows what happens when I added 9392 into the Intercept/Host configs

 ![image](https://global.discourse-cdn.com/free1/uploads/netfoundry/original/1X/e0a597d36f93f26b9b468fd687b639e9453bbfac.png)

 ![image](https://global.discourse-cdn.com/free1/uploads/netfoundry/original/1X/ad9672e3b03ec485db0c90a941bb1cf425346c89.png)

 ![image](https://global.discourse-cdn.com/free1/uploads/netfoundry/original/1X/cbe34e399ee7e16dfad900b053836eaa34aa8ab8.png)

Is this expected behaviour?

On a slight (un)related note - you can add a service name with a space ( ) at the beginning and this is allowed. I had not noticed as I was cutting/pasting. It was only when I was dumping some command line results from there that I noticed the indentation. This is on ZAC 2.3.4. I will log a bug for this.

---

<div class="post-metadata">

**Author:** ![TheLumberjack](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thelumberjack/32/113_2.png) [@TheLumberjack](https://openziti.discourse.group/u/TheLumberjack)\
**Post date:** [November 5, 2022, 10:59pm UTC](https://openziti.discourse.group/t/adding-port-to-intercept-or-host-adds-another-terminator/852/2 "2022-11-05T22:59:19Z")

</div>

Just so I understand, other than the apparent odd terminator behavior, nothing is malfunctioning, right? You’ve just noticed an oddity and are looking to understand ‘why’. Right? This probably needs @plorenz to comment on the terminator behavior.

I just want to make sure there’s not a problem happening in there.

As for the space at the begging thing, in the UI those should probably be trimmed. Thanks for the issue.

---

<div class="post-metadata">

**Author:** ![gooseleggs](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/gooseleggs/32/450_2.png) [@gooseleggs](https://openziti.discourse.group/u/gooseleggs)\
**Post date:** [November 5, 2022, 11:25pm UTC](https://openziti.discourse.group/t/adding-port-to-intercept-or-host-adds-another-terminator/852/3 "2022-11-05T23:25:28Z")

</div>

Yeah. No problem - justify oddness and wanting to understand why:-). And that issue for space was also logged 16 days ago as well.

---

<div class="post-metadata">

**Author:** ![TheLumberjack](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thelumberjack/32/113_2.png) [@TheLumberjack](https://openziti.discourse.group/u/TheLumberjack)\
**Post date:** [November 5, 2022, 11:26pm UTC](https://openziti.discourse.group/t/adding-port-to-intercept-or-host-adds-another-terminator/852/4 "2022-11-05T23:26:30Z")

</div>

Yeah, I noticed when I looked at it. I’ve asked @jeremy.tellier to give some of those ZAC issues some thought. Should have some updates in ZAC soon

---

<div class="post-metadata">

**Author:** ![jeremy.tellier](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/jeremy.tellier/32/17_2.png) [@jeremy.tellier](https://openziti.discourse.group/u/jeremy.tellier)\
**Post date:** [November 5, 2022, 11:28pm UTC](https://openziti.discourse.group/t/adding-port-to-intercept-or-host-adds-another-terminator/852/5 "2022-11-05T23:28:40Z")

</div>

I will trim the inputs in the UI but the service should probably kick that back too.

---

<div class="post-metadata">

**Author:** ![plorenz](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/plorenz/32/54_2.png) [@plorenz](https://openziti.discourse.group/u/plorenz)\
**Post date:** [November 7, 2022, 2:13pm UTC](https://openziti.discourse.group/t/adding-port-to-intercept-or-host-adds-another-terminator/852/6 "2022-11-07T14:13:37Z")

</div>

I think this is likely a bug in in the tunneler sdk. Depending on implementation, the terminator should either be unchanged or replaced, but not added to.
