Hi there, I'm back again. I've been continuing my work on a Controller cluster in HA mode. Still based on these installation scripts . I'm now on Controller/Router version 1.4.3 and ZET version 1.5.2. See my services configuration here . I've ran into the following error in ZET since i started my H…

Hi @farmhouse , just wanted to let you know that we've seen your issue and aren't trying to ignore it. We just need to find the time to be able to reproduce the issue and confirm it's a problem and fix it if it is... We appreciate the post and we'll see if we can find some time soon to get to this. …

Hi, Thanks @TheLumberjack ! I don't expect anything over the weekend ! :smiling_face_with_sunglasses:

I've been working through this issue over the past few days and updated some of my scripts I'm now using v1.5.0 on Controllers and Edge Routers. and 1.5.3 on ZET. I think it's being caused by my use of a haproxy load balancer in front of my two edge-routers. The reason i'm using a load balancer i…

[image] farmhouse: I think it's being caused by my use of a haproxy load balancer in front of my two edge-routers. Oh interesting. That's definitely possible. That's not a deployment that we typically see people using but it surely might be somehow causing issues as the LB round robins betwee…

Thanks @TheLumberjack . I have been using source IP balancing as I anticipated these kind of issues but the operation seems to be the same if I use round robin too. I’ll try these suggestions. Another question I had… is it possible to somehow configure that the ZET client only connects to a single…

[image] farmhouse: is it possible to somehow configure that the ZET client only connects to a single Edge Router Sure you can influence this using edge-router-policies. You can ensure a given identity can only connect to a single edge router if that's what you want. Generally speaking though…

Thanks @TheLumberjack . Removing the load balancer from in front of the Edge Routers worked as expected. ZET clients operate as expected now although they are obviously addressing Edge Routers individually E.G tls:router1.foo.bar:443, tls:router2.foo.bar:443.

I'm not quite sure what you mean by the following though. Can you explain please ? [image] TheLumberjack: Or use the LB but provide two discreet paths for "router1" and "router2" and advertise them as such just to see if that is where the problem is coming from?

[image] farmhouse: I'm not quite sure what you mean Oh. I was just saying have the LB provide one solitary "non-load balanced" passthrough path for each router. I didn't know if you were forced to use the LB or not. Basically, assign a path through the LB for a particular host. You seem to h…

Can the maxConnections host.v1 config option described here be used to limit the number of edge routers that the ZET client creates terminators on ? I set this value to 1 in my host.v1 config but i still see a terminator for each of my identities on all of my Edge Routers. { "name": "lifeboat.ss…

ERROR ziti-sdk:connect.c:990

Uncategorized

ekoby March 17, 2025, 5:25pm 14

it is a bug in tunneler code

Router connection load balancing

Topic		Replies	Views
ZET random loss of connection during usage Ziti Edge Tunnel	4	341	November 23, 2022
Failed to connect to ER (on a separate box from the controller) Uncategorized	5	145	August 20, 2024
Router connection to Controller, handshake failed Uncategorized	5	135	April 16, 2025
SEGV crashing ziti-edge-tunnel von v0.22.15 Uncategorized	1	128	February 15, 2024
Connection closed errors between Ziti-Edge-Tunnels Uncategorized	4	424	November 11, 2024

ERROR ziti-sdk:connect.c:990

Related topics