# Client show error "context deadline exceeded" **URL:** \ **Category:** Ziti Overlay\ **Created:** [October 8, 2024, 9:01am UTC](https://openziti.discourse.group/t/client-show-error-context-deadline-exceeded/3213 "2024-10-08T09:01:54Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![McGonagall666](https://avatars.discourse-cdn.com/v4/letter/m/51bf81/32.png) [@McGonagall666](https://openziti.discourse.group/u/McGonagall666)\ **Post date:** [October 8, 2024, 9:01am UTC](https://openziti.discourse.group/t/client-show-error-context-deadline-exceeded/3213/1 "2024-10-08T09:01:54Z")
According to the tutorial [Use a Router as a Local Gateway | OpenZiti](https://openziti.io/docs/guides/topologies/gateway/router/) Create local-router and remote-router, and after all routers are started, curl [www.zftest.com:5000](http://www.zftest.com:5000) in the local-router environment to display the following content in the local-router log. There are no error logs in the controller, router, and remote-router， **ziti version is 1.1.11** Oct 08 07:02:37 routerserver ziti-router[3021]: {"file":"[github.com/openziti/ziti/tunnel/intercept/tproxy/tproxy\_linux.go:311","func":"github.com/openziti/ziti/tunnel/intercept/tproxy.(\*tProxy).acceptTCP","level":"info","msg":"received](http://github.com/openziti/ziti/tunnel/intercept/tproxy/tproxy_linux.go:311%22,%22func%22:%22github.com/openziti/ziti/tunnel/intercept/tproxy.(*tProxy).acceptTCP%22,%22level%22:%22info%22,%22msg%22:%22received) connection: 100.64.0.1:5000 --\u003e 100.64.0.0:42292","time":"2024-10-08T07:02:37.044Z"} Oct 08 07:02:37 routerserver ziti-router[3021]: {"ctrlId":"[www.ziti-test-ctrl.com](http://www.ziti-test-ctrl.com)","error":"context deadline exceeded","file":"[github.com/openziti/ziti/router/xgress\_edge\_tunnel/fabric.go:269","func":"github.com/openziti/ziti/router/xgress\_edge\_tunnel.(\*fabricProvider).tunnelServiceV1","level":"warning","msg":"failed](http://github.com/openziti/ziti/router/xgress_edge_tunnel/fabric.go:269%22,%22func%22:%22github.com/openziti/ziti/router/xgress_edge_tunnel.(*fabricProvider).tunnelServiceV1%22,%22level%22:%22warning%22,%22msg%22:%22failed) to dial fabric","service":"zftest","time":"2024-10-08T07:02:37.044Z"} Oct 08 07:02:37 routerserver ziti-router[3021]: {"error":"context deadline exceeded","file":"[github.com/openziti/ziti/tunnel/tunnel.go:51","func":"github.com/openziti/ziti/tunnel.DialAndRun","level":"error","msg":"tunnel](http://github.com/openziti/ziti/tunnel/tunnel.go:51%22,%22func%22:%22github.com/openziti/ziti/tunnel.DialAndRun%22,%22level%22:%22error%22,%22msg%22:%22tunnel) failed","service":"zftest","time":"2024-10-08T07:02:37.045Z"} **ziti fabric list links** │ 3g6nWN5YqxERvphBvZb4o2 │ local-router │ [www.ziti-test-router.com](http://www.ziti-test-router.com) │ 1 │ 3.0ms │ 2.9ms │ Connected │ up │ 6 │ │ 5R4cuJXHyjDOg19fRsZz3l │ remote-router │ [www.ziti-test-router.com](http://www.ziti-test-router.com) │ 1 │ 3.0ms │ 3.0ms │ Connected │ up │ 6 **ziti-test-router is public router, not open tunnel** ![image](https://global.discourse-cdn.com/free1/uploads/netfoundry/original/2X/7/781c4c873147ff920919dc71b710ffaf3142c8c9.png) ![image](https://global.discourse-cdn.com/free1/uploads/netfoundry/original/2X/c/c5ab87417872445b787f9680620835ba4008f88a.png) ![image](https://global.discourse-cdn.com/free1/uploads/netfoundry/original/2X/6/641cd6a23ee3b6c993e36a7decf1e04f722bf9c2.png) ![image](https://global.discourse-cdn.com/free1/uploads/netfoundry/original/2X/6/647f810f4d22bd5b28dfdcaf0076bfd0c9902a40.png) ![image](https://global.discourse-cdn.com/free1/uploads/netfoundry/original/2X/0/0a6324f3f93be9fd11f05dfe6304340cbf2623c7.png) ![image](https://global.discourse-cdn.com/free1/uploads/netfoundry/original/2X/8/8da049ab8a5f15eee3358c3a2692dc2c68cba9ad.png) ---
**Author:** ![dariuszSki](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/dariuszski/32/339_2.png) [@dariuszSki](https://openziti.discourse.group/u/dariuszSki)\ **Post date:** [October 8, 2024, 12:12pm UTC](https://openziti.discourse.group/t/client-show-error-context-deadline-exceeded/3213/2 "2024-10-08T12:12:59Z")
Hi, It looks like the route creation or at least attempt across fabric is not happening. If you increase the log level to at least debug, any luck with logs? ---
**Author:** ![McGonagall666](https://avatars.discourse-cdn.com/v4/letter/m/51bf81/32.png) [@McGonagall666](https://openziti.discourse.group/u/McGonagall666)\ **Post date:** [October 9, 2024, 12:40am UTC](https://openziti.discourse.group/t/client-show-error-context-deadline-exceeded/3213/3 "2024-10-09T00:40:23Z")
I have set the log level for both local-router and remote-router to - v **remote-router** [180.010] DEBUG ziti/router/forwarder.(\*Scanner).scan: scanning [0] circuits [180.117] DEBUG ziti/router/state.(\*ManagerImpl). StartRouterModelSave.func1.(\*RouterDataModel). Save.1: could not save router data model, no index **local-router** [101.018] INFO ziti/tunnel/intercept/tproxy.(\*tProxy).acceptTCP: received connection: 100.64.0.1:5000 --\> 100.64.0.0:60886 [101.018] WARNING ziti/router/xgress\_edge\_tunnel.(\*fabricProvider).tunnelServiceV1: {ctrlId=[[www.ziti-test-ctrl.com](http://www.ziti-test-ctrl.com)] error=[context deadline exceeded] service=[zftest]} failed to dial fabric [101.019] ERROR ziti/tunnel.DialAndRun: {error=[context deadline exceeded] service=[zftest]} tunnel failed [120.010] DEBUG ziti/router/forwarder.(\*Scanner).scan: scanning [0] circuits [120.093] DEBUG ziti/router/state.(\*ManagerImpl).StartRouterModelSave.func1.(\*RouterDataModel).Save.1: could not save router data model, no index ---
**Author:** ![dariuszSki](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/dariuszski/32/339_2.png) [@dariuszSki](https://openziti.discourse.group/u/dariuszSki)\ **Post date:** [October 9, 2024, 2:49am UTC](https://openziti.discourse.group/t/client-show-error-context-deadline-exceeded/3213/4 "2024-10-09T02:49:13Z")
Can you capture the tcpdump on the local router on the main interface while trying to access the service? one interface on this router? ---
**Author:** ![McGonagall666](https://avatars.discourse-cdn.com/v4/letter/m/51bf81/32.png) [@McGonagall666](https://openziti.discourse.group/u/McGonagall666)\ **Post date:** [October 9, 2024, 3:01am UTC](https://openziti.discourse.group/t/client-show-error-context-deadline-exceeded/3213/5 "2024-10-09T03:01:42Z")
I will try to use tcpdump to capture routing data in the Ubuntu environment I want the entire process to follow [Use a Router as a Local Gateway | OpenZiti](https://openziti.io/docs/guides/topologies/gateway/router/) I went to configure it. The entire process is created through zitiu\_router\_auto-enroll. I don't know if it's because of version v1.1.11. The video is from two years ago, so is it outdated ---
**Author:** ![McGonagall666](https://avatars.discourse-cdn.com/v4/letter/m/51bf81/32.png) [@McGonagall666](https://openziti.discourse.group/u/McGonagall666)\ **Post date:** [October 9, 2024, 10:56am UTC](https://openziti.discourse.group/t/client-show-error-context-deadline-exceeded/3213/6 "2024-10-09T10:56:33Z")
Next, I made the following attempts > **[Service Topologies | OpenZiti](https://openziti.io/docs/guides/topologies/services/)** > > 3.0 Ziti services Figure 1 is accessible The flipping of Figure 2 and Figure 2 is not working, as the router cannot be accessed by either the client or server, just like the errors in local-router and remote-router ---
**Author:** ![dariuszSki](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/dariuszski/32/339_2.png) [@dariuszSki](https://openziti.discourse.group/u/dariuszSki)\ **Post date:** [October 9, 2024, 6:14pm UTC](https://openziti.discourse.group/t/client-show-error-context-deadline-exceeded/3213/7 "2024-10-09T18:14:03Z")
The thing is that it seems to be timing out trying to create circuit across the fabric, i.e. fabric route in the public router and then should attempt to dial the end service endpoint on the remote router. The end to end circuit can not be created successfully if these events are not completed. Logs suggest that is the case. The dev team is working on the HA and some of that logic is evolving. The controller is involved in this process, but there seems to be no logs on the controller either. I was just trying to see with wireshark if your local router is even talking the controller, since there are no logs indicating that either. Did you try to restart the local router or reboot the host? By the way, the process of creating the router did not change much if at all. ---
**Author:** ![McGonagall666](https://avatars.discourse-cdn.com/v4/letter/m/51bf81/32.png) [@McGonagall666](https://openziti.discourse.group/u/McGonagall666)\ **Post date:** [October 10, 2024, 12:42am UTC](https://openziti.discourse.group/t/client-show-error-context-deadline-exceeded/3213/8 "2024-10-10T00:42:05Z")
Indeed, the communication between the route and the controller was not captured. I think the most critical thing should be the route yml. The following one is generated by ziti\_router\_auto\_enroll. Is there any problem? In local-router, you can see successfully connected to controller. In api sessions, you can see local-router, but you can't see dial record in sessions because curl [www.zftest.com:5000](http://www.zftest.com:5000) has reported an error. ```auto v: 3 identity: cert: /opt/openziti/ziti-router/certs/cert.pem server_cert: /opt/openziti/ziti-router/certs/server_cert.pem key: /opt/openziti/ziti-router/certs/key.pem ca: /opt/openziti/ziti-router/certs/ca.pem ctrl: endpoint: tls:www.ziti-test-ctrl.com:6262 link: dialers: - binding: transport edge: heartbeatIntervalSeconds: 60 csr: country: US province: NC locality: Charlotte organization: NetFoundry organizationalUnit: Ziti sans: dns: - localhost ip: - 172.16.222.190 - 127.0.0.1 listeners: - binding: edge address: tls:0.0.0.0:443 options: advertise: 172.16.222.190:443 - binding: tunnel options: mode: tproxy resolver: udp://172.16.222.190:53 lanIf: ens160 dnsSvcIpRange: 100.64.0.0/10 ``` ---
**Author:** ![dariuszSki](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/dariuszski/32/339_2.png) [@dariuszSki](https://openziti.discourse.group/u/dariuszSki)\ **Post date:** [October 10, 2024, 1:19am UTC](https://openziti.discourse.group/t/client-show-error-context-deadline-exceeded/3213/9 "2024-10-10T01:19:03Z")
This looks ok to me, even though I don’t see that many controllers fqdns with www as a hostname. Can you also share the controller’s config? ---
**Author:** ![McGonagall666](https://avatars.discourse-cdn.com/v4/letter/m/51bf81/32.png) [@McGonagall666](https://openziti.discourse.group/u/McGonagall666)\ **Post date:** [October 10, 2024, 1:25am UTC](https://openziti.discourse.group/t/client-show-error-context-deadline-exceeded/3213/10 "2024-10-10T01:25:11Z")
```auto v: 3 db: "/opt/ziti/related/www.ziti-test-ctrl.com/db/ctrl.db" identity: cert: "/opt/ziti/related/www.ziti-test-ctrl.com/pki/www.ziti-test-ctrl.com-intermediate/certs/www.ziti-test-ctrl.com-client.cert" server_cert: "/opt/ziti/related/www.ziti-test-ctrl.com/pki/www.ziti-test-ctrl.com-intermediate/certs/www.ziti-test-ctrl.com-server.chain.pem" key: "/opt/ziti/related/www.ziti-test-ctrl.com/pki/www.ziti-test-ctrl.com-intermediate/keys/www.ziti-test-ctrl.com-server.key" ca: "/opt/ziti/related/www.ziti-test-ctrl.com/pki/cas.pem" ctrl: options: advertiseAddress: tls:www.ziti-test-ctrl.com:6262 listener: tls:0.0.0.0:6262 healthChecks: boltCheck: interval: 30s timeout: 20s initialDelay: 30s edge: api: sessionTimeout: 30m address: "www.ziti-test-ctrl.com:1280" enrollment: signingCert: cert: /opt/ziti/related/www.ziti-test-ctrl.com/pki/www.ziti-test-ctrl.com-signing-intermediate/certs/www.ziti-test-ctrl.com-signing-intermediate.cert key: /opt/ziti/related/www.ziti-test-ctrl.com/pki/www.ziti-test-ctrl.com-signing-intermediate/keys/www.ziti-test-ctrl.com-signing-intermediate.key edgeIdentity: duration: 180m edgeRouter: duration: 180m web: - name: client-management bindPoints: - interface: "[::]:1280" address: www.ziti-test-ctrl.com:1280 identity: ca: "/opt/ziti/related/www.ziti-test-ctrl.com/pki/www.ziti-test-ctrl.com-intermediate/certs/www.ziti-test-ctrl.com-intermediate.cert" key: "/opt/ziti/related/www.ziti-test-ctrl.com/pki/www.ziti-test-ctrl.com-intermediate/keys/www.ziti-test-ctrl.com-server.key" server_cert: "/opt/ziti/related/www.ziti-test-ctrl.com/pki/www.ziti-test-ctrl.com-intermediate/certs/www.ziti-test-ctrl.com-server.chain.pem" cert: "/opt/ziti/related/www.ziti-test-ctrl.com/pki/www.ziti-test-ctrl.com-intermediate/certs/www.ziti-test-ctrl.com-client.cert" options: idleTimeout: 5000ms #http timeouts, new readTimeout: 5000ms writeTimeout: 100000ms minTLSVersion: TLS1.2 maxTLSVersion: TLS1.3 apis: - binding: edge-management options: { } - binding: edge-client options: { } - binding: fabric options: { } ``` ---
**Author:** ![dariuszSki](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/dariuszski/32/339_2.png) [@dariuszSki](https://openziti.discourse.group/u/dariuszSki)\ **Post date:** [October 10, 2024, 1:36am UTC](https://openziti.discourse.group/t/client-show-error-context-deadline-exceeded/3213/11 "2024-10-10T01:36:35Z")
Can you enable debug on the controller and capture logs when trying to dial the service? ---
**Author:** ![McGonagall666](https://avatars.discourse-cdn.com/v4/letter/m/51bf81/32.png) [@McGonagall666](https://openziti.discourse.group/u/McGonagall666)\ **Post date:** [October 10, 2024, 1:45am UTC](https://openziti.discourse.group/t/client-show-error-context-deadline-exceeded/3213/12 "2024-10-10T01:45:18Z")
Current test scenarios ![image](https://global.discourse-cdn.com/free1/uploads/netfoundry/original/2X/c/c3c36f9077e1a8a73500715d42619676278d4725.png) no any log about local-router，only server client log，172.16.222.43为egress-tunnel [8.652] DEBUG ziti/controller/events.(\*entityChangeEventDispatcher).flushLoop: cleaning up entity change events [8.653] DEBUG ziti/controller/events.(\*entityChangeEventDispatcher).processPreviousTxEvents: {txId=[36328]} cleaning up entity change events for tx [12.829] DEBUG transport/v2/tls.(\*sharedListener).getConfig [tls:0.0.0.0:1280]: {client=[172.16.222.43:58150]} client requesting protocols = [http/1.1] [12.829] DEBUG transport/v2/tls.(\*sharedListener).getConfig [tls:0.0.0.0:1280]: {client=[172.16.222.43:58150]} found handler for proto [12.860] DEBUG transport/v2/tls.(\*sharedListener).processConn [tls:0.0.0.0:1280]: {remote=[172.16.222.43:58150] client=[172.16.222.43:58150]} selected protocol = 'http/1.1' [12.861] DEBUG ziti/controller/internal/routes.(\*PublicQueryOptions).getFullQuery: query: [QueryOption Predicate: 'true', Sort: '', Paging: '[Paging Offset: '0', Limit: '25', ReturnAll: 'false']'] [17.656] DEBUG ziti/controller/handler\_edge\_ctrl.(\*listTunnelServicesHandler).listServices: {router=[local-router]} service list requested, but no update available Can you reproduce this test scenario? ---
**Author:** ![dariuszSki](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/dariuszski/32/339_2.png) [@dariuszSki](https://openziti.discourse.group/u/dariuszSki)\ **Post date:** [October 10, 2024, 11:20pm UTC](https://openziti.discourse.group/t/client-show-error-context-deadline-exceeded/3213/13 "2024-10-10T23:20:17Z")
I didn't get the chance today because of time. I'll try now. ---
**Author:** ![dariuszSki](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/dariuszski/32/339_2.png) [@dariuszSki](https://openziti.discourse.group/u/dariuszSki)\ **Post date:** [October 11, 2024, 2:18am UTC](https://openziti.discourse.group/t/client-show-error-context-deadline-exceeded/3213/14 "2024-10-11T02:18:32Z")
Followed the same guide with Host OpenZiti Anywhere for the network part, and my setup is working as expected. ---
**Author:** ![dariuszSki](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/dariuszski/32/339_2.png) [@dariuszSki](https://openziti.discourse.group/u/dariuszSki)\ **Post date:** [October 11, 2024, 2:19am UTC](https://openziti.discourse.group/t/client-show-error-context-deadline-exceeded/3213/15 "2024-10-11T02:19:24Z")
![image](https://global.discourse-cdn.com/free1/uploads/netfoundry/original/2X/f/f018a27b82d5e90bb65179e31869e038cd83c3e1.png) Public Router, Controller and ZAC on the same VM Curl to reach service ![image](https://global.discourse-cdn.com/free1/uploads/netfoundry/original/2X/c/cd11682ba869719331caa9c919398b45bee36fa2.png) ---
**Author:** ![McGonagall666](https://avatars.discourse-cdn.com/v4/letter/m/51bf81/32.png) [@McGonagall666](https://openziti.discourse.group/u/McGonagall666)\ **Post date:** [October 11, 2024, 2:24am UTC](https://openziti.discourse.group/t/client-show-error-context-deadline-exceeded/3213/16 "2024-10-11T02:24:24Z")
Is tnet-ctrl-edge-router a tunnel router? Why do we need an additional tunnel routing? Can I take a look at your edge routers and policy sections ---
**Author:** ![dariuszSki](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/dariuszski/32/339_2.png) [@dariuszSki](https://openziti.discourse.group/u/dariuszSki)\ **Post date:** [October 11, 2024, 12:07pm UTC](https://openziti.discourse.group/t/client-show-error-context-deadline-exceeded/3213/17 "2024-10-11T12:07:45Z")
The quickstart configured the public router to have tunneler mode enable to host but not intercept services. I disabled the edge to make it just a relay node. Users have flexibility as to the router configuration. Here is the config ```auto v: 3 identity: cert: "/home/ziggy/.ziti/quickstart/dariusz-tnet-ctrl/dariusz-tnet-ctrl-edge-router.cert" server_cert: "/home/ziggy/.ziti/quickstart/dariusz-tnet-ctrl/dariusz-tnet-ctrl-edge-router.server.chain.cert" key: "/home/ziggy/.ziti/quickstart/dariusz-tnet-ctrl/dariusz-tnet-ctrl-edge-router.key" ca: "/home/ziggy/.ziti/quickstart/dariusz-tnet-ctrl/dariusz-tnet-ctrl-edge-router.cas" #alt_server_certs: # - server_cert: "" # server_key: "" ctrl: endpoint: tls:dariusz-tnet-ctrl:8440 link: dialers: - binding: transport listeners: - binding: transport bind: tls:0.0.0.0:10080 advertise: tls:ctrl01.centralus.cloudapp.azure.com:10080 options: outQueueSize: 4 #listeners: # bindings of edge and tunnel requires an "edge" section below #- binding: edge # address: tls:0.0.0.0:8442 # options: # advertise: ctrl01.centralus.cloudapp.azure.com:8442 # connectTimeoutMs: 5000 # getSessionTimeout: 60 #- binding: tunnel # options: # mode: host #tproxy|host #edge: # csr: # country: US # province: NC # locality: Charlotte # organization: NetFoundry # organizationalUnit: Ziti # sans: # dns: # - localhost # - ctrl01.centralus.cloudapp.azure.com # - dariusz-tnet-ctrl # ip: # - "127.0.0.1" # - "::1" # - "20.46.253.218" #transport: # ws: # writeTimeout: 10 # readTimeout: 5 # idleTimeout: 120 # pongTimeout: 60 # pingInterval: 54 # handshakeTimeout: 10 # readBufferSize: 4096 # writeBufferSize: 4096 # enableCompression: true forwarder: latencyProbeInterval: 0 xgressDialQueueLength: 1000 xgressDialWorkerCount: 128 linkDialQueueLength: 1000 linkDialWorkerCount: 32 ``` Service still works. Links: ```auto /opt/openziti/ziti-router/ziti fabric list links ╭───────────────────────┬───────────────────────┬───────────────────────────────┬─────────────┬─────────────┬─────────────┬───────────┬────────┬───────────╮ │ ID │ DIALER │ ACCEPTOR │ STATIC COST │ SRC LATENCY │ DST LATENCY │ STATE │ STATUS │ FULL COST │ ├───────────────────────┼───────────────────────┼───────────────────────────────┼─────────────┼─────────────┼─────────────┼───────────┼────────┼───────────┤ │ BE85PJfC2s8Z5Yz3fiQNW │ dariusz-remote-router │ dariusz-tnet-ctrl-edge-router │ 1 │ 25.8ms │ 28.2ms │ Connected │ up │ 54 │ │ zyAwFMYJSmMrHZxSgwgjy │ dariusz-local-router │ dariusz-tnet-ctrl-edge-router │ 1 │ 42.0ms │ 40.6ms │ Connected │ up │ 82 │ ╰───────────────────────┴───────────────────────┴───────────────────────────────┴─────────────┴─────────────┴─────────────┴───────────┴────────┴───────────╯ results: 1-2 of 2 ``` Circuit for ssh: ```auto ziti fabric list circuits ╭───────────┬───────────────────────────┬─────────┬────────────────────────┬─────────────────────┬────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮ │ ID │ CLIENT │ SERVICE │ TERMINATOR │ CREATEDAT │ PATH │ ├───────────┼───────────────────────────┼─────────┼────────────────────────┼─────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ ONUC72A6X │ cm241s5e002ytv2dt6aopfyu3 │ ssh │ 25vAusYBL0UQTbzwPK0gbe │ 2024-10-11 11:57:34 │ r/dariusz-local-router -> l/zyAwFMYJSmMrHZxSgwgjy -> r/dariusz-tnet-ctrl-edge-router -> l/BE85PJfC2s8Z5Yz3fiQNW -> r/dariusz-remote-router │ ╰───────────┴───────────────────────────┴─────────┴────────────────────────┴─────────────────────┴────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯ results: 1-1 of 1 ``` Service Terminators ```auto ziti fabric list terminators ╭────────────────────────┬─────────┬───────────────────────┬─────────┬────────────────────────┬──────────┬──────┬────────────┬──────────────┬────────────╮ │ ID │ SERVICE │ ROUTER │ BINDING │ ADDRESS │ INSTANCE │ COST │ PRECEDENCE │ DYNAMIC COST │ HOST ID │ ├────────────────────────┼─────────┼───────────────────────┼─────────┼────────────────────────┼──────────┼──────┼────────────┼──────────────┼────────────┤ │ 25vAusYBL0UQTbzwPK0gbe │ ssh │ dariusz-remote-router │ tunnel │ 25vAusYBL0UQTbzwPK0gbe │ │ 0 │ default │ 2 │ GP.py8BUcB │ ╰────────────────────────┴─────────┴───────────────────────┴─────────┴────────────────────────┴──────────┴──────┴────────────┴──────────────┴────────────╯ results: 1-1 of 1 ``` SP ![image](https://global.discourse-cdn.com/free1/uploads/netfoundry/original/2X/c/cc94a59a6ee94aab4eedde63c30f125a831ace88.png) RP ![image](https://global.discourse-cdn.com/free1/uploads/netfoundry/original/2X/f/fbae49e95e62c7ebd6bb04796696c366425d9cb8.png) SEP ![image](https://global.discourse-cdn.com/free1/uploads/netfoundry/original/2X/8/8d2fcd8e8bb32868257306f6c2e6c5134943ac32.png) ---
**Author:** ![McGonagall666](https://avatars.discourse-cdn.com/v4/letter/m/51bf81/32.png) [@McGonagall666](https://openziti.discourse.group/u/McGonagall666)\ **Post date:** [March 5, 2025, 12:42pm UTC](https://openziti.discourse.group/t/client-show-error-context-deadline-exceeded/3213/18 "2025-03-05T12:42:07Z")
Sorry, I stopped learning ziti some time ago for some reason. Now I still get the error "context deadline exceeded"，ziti version is 1.1.15 This is the resolvectl ,log, yaml of client-router ```auto Global Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub Current DNS Server: 172.16.222.135 DNS Servers: 172.16.222.135 Link 2 (ens160) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported ``` [client-router.txt](https://openziti.discourse.group/uploads/short-url/4RV4eZmPQaoPxzDhFpIvakXNwr8.txt) (25.6 KB) [client-router1.txt](https://openziti.discourse.group/uploads/short-url/sc0x2hdeljUV5km9IY5MGIjGXD9.txt) (1.9 KB) This is the resolvectl , log, yaml of server-router ```auto Global Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub Current DNS Server: 172.16.222.129 DNS Servers: 172.16.222.129 Link 2 (ens160) Current Scopes: DNS Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: 8.8.8.8 DNS Servers: 8.8.8.8 8.8.4.4 Link 3 (docker0) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 4 (br-7ef062c9c483) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported ``` [server-router.txt](https://openziti.discourse.group/uploads/short-url/4i4kSue8JpjF7AFuspwJJnMmdUJ.txt) (23.1 KB) [server-router1.txt](https://openziti.discourse.group/uploads/short-url/6dpm7HyRYezT4cXhjSwiHjbLM5C.txt) (1.7 KB) ```auto icebear@client:~/client-router$ ./ziti1115 fabric list terminators ╭────────────────────────┬─────────┬───────────────────────┬─────────┬────────────────────────┬──────────┬──────┬────────────┬──────────────┬────────────╮ │ ID │ SERVICE │ ROUTER │ BINDING │ ADDRESS │ INSTANCE │ COST │ PRECEDENCE │ DYNAMIC COST │ HOST ID │ ├────────────────────────┼─────────┼───────────────────────┼─────────┼────────────────────────┼──────────┼──────┼────────────┼──────────────┼────────────┤ │ 6niQJQAbnbOCaQyzST9LPN │ chandao │ server-router.myy.com │ tunnel │ 6niQJQAbnbOCaQyzST9LPN │ │ 0 │ default │ 0 │ ktSnvi2ltb │ ╰────────────────────────┴─────────┴───────────────────────┴─────────┴────────────────────────┴──────────┴──────┴────────────┴──────────────┴────────────╯ results: 1-1 of 1 icebear@client:~/client-router$ ./ziti1115 fabric list links ╭────────────────────────┬───────────────────────┬─────────────────┬─────────────┬─────────────┬─────────────┬───────────┬────────┬───────────╮ │ ID │ DIALER │ ACCEPTOR │ STATIC COST │ SRC LATENCY │ DST LATENCY │ STATE │ STATUS │ FULL COST │ ├────────────────────────┼───────────────────────┼─────────────────┼─────────────┼─────────────┼─────────────┼───────────┼────────┼───────────┤ │ 4NsOATCPpLiAHuQzQpWR0Z │ server-router.myy.com │ router2.myy.com │ 1 │ 2.8ms │ 3.1ms │ Connected │ up │ 6 │ │ 79lvL2JOSCYkSoipOzUq2v │ client-router.myy.com │ router2.myy.com │ 1 │ 1.7ms │ 2.7ms │ Connected │ up │ 4 │ ╰────────────────────────┴───────────────────────┴─────────────────┴─────────────┴─────────────┴─────────────┴───────────┴────────┴───────────╯ results: 1-2 of 2 icebear@client:~/client-router$ ./ziti1115 fabric list circuits ╭────┬────────┬─────────┬────────────┬───────────┬──────╮ │ ID │ CLIENT │ SERVICE │ TERMINATOR │ CREATEDAT │ PATH │ ├────┼────────┼─────────┼────────────┼───────────┼──────┤ ╰────┴────────┴─────────┴────────────┴───────────┴──────╯ results: none ``` ---
**Author:** ![dariuszSki](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/dariuszski/32/339_2.png) [@dariuszSki](https://openziti.discourse.group/u/dariuszSki)\ **Post date:** [March 6, 2025, 4:02pm UTC](https://openziti.discourse.group/t/client-show-error-context-deadline-exceeded/3213/19 "2025-03-06T16:02:27Z")
Welcome back @McGonagall666 . Can you share the service details and service, router policies. Also, which destination you are trying to reach. I see a couple destination are being added to the intercept. Just trying to confirm that. ```auto {"file":"github.com/openziti/ziti/tunnel/intercept/svcpoll.go:226","func":"github.com/openziti/ziti/tunnel/intercept.(*ServiceListener).addService","level":"info","msg":"starting tunnel for newly available service chandao","serviceId":"4aoc4SC0vFqqxXi5ZkrePn","serviceName":"chandao","time":"2025-03-05T12:32:59.466Z"} {"file":"github.com/openziti/ziti/tunnel/intercept/tproxy/tproxy_linux.go:229","func":"github.com/openziti/ziti/tunnel/intercept/tproxy.(*interceptor).newTproxy","level":"info","msg":"tproxy listening on tcp:127.0.0.1:32817","time":"2025-03-05T12:32:59.466Z"} {"file":"github.com/openziti/ziti/tunnel/intercept/tproxy/tproxy_linux.go:556","func":"github.com/openziti/ziti/tunnel/intercept/tproxy.(*tProxy).addInterceptAddr","level":"info","msg":"Adding rule iptables -t mangle -A NF-INTERCEPT [-m comment --comment chandao -d 100.64.0.2/32 -p tcp --dport 80:80 -j TPROXY --tproxy-mark 0x1/0x1 --on-ip=127.0.0.1 --on-port=32817]","time":"2025-03-05T12:32:59.466Z"} {"file":"github.com/openziti/ziti/tunnel/intercept/tproxy/tproxy_linux.go:570","func":"github.com/openziti/ziti/tunnel/intercept/tproxy.(*tProxy).addInterceptAddr","level":"info","msg":"Adding rule iptables -t filter -A NF-INTERCEPT [-i ens160 -m comment --comment chandao -d 100.64.0.2/32 -p tcp --dport 80:80 -j ACCEPT]","time":"2025-03-05T12:32:59.468Z"} {"file":"github.com/openziti/ziti/tunnel/intercept/tproxy/tproxy_linux.go:556","func":"github.com/openziti/ziti/tunnel/intercept/tproxy.(*tProxy).addInterceptAddr","level":"info","msg":"Adding rule iptables -t mangle -A NF-INTERCEPT [-m comment --comment chandao -d 100.64.0.2/32 -p tcp --dport 8080:8080 -j TPROXY --tproxy-mark 0x1/0x1 --on-ip=127.0.0.1 --on-port=32817]","time":"2025-03-05T12:32:59.469Z"} {"file":"github.com/openziti/ziti/tunnel/intercept/tproxy/tproxy_linux.go:570","func":"github.com/openziti/ziti/tunnel/intercept/tproxy.(*tProxy).addInterceptAddr","level":"info","msg":"Adding rule iptables -t filter -A NF-INTERCEPT [-i ens160 -m comment --comment chandao -d 100.64.0.2/32 -p tcp --dport 8080:8080 -j ACCEPT]","time":"2025-03-05T12:32:59.471Z"} {"file":"github.com/openziti/ziti/tunnel/dns/server.go:271","func":"github.com/openziti/ziti/tunnel/dns.(*resolver).AddHostname","level":"info","msg":"adding chandao.myy.com = 100.64.0.2 to resolver","time":"2025-03-05T12:32:59.472Z"} {"file":"github.com/openziti/ziti/tunnel/intercept/tproxy/tproxy_linux.go:556","func":"github.com/openziti/ziti/tunnel/intercept/tproxy.(*tProxy).addInterceptAddr","level":"info","msg":"Adding rule iptables -t mangle -A NF-INTERCEPT [-m comment --comment chandao -d 100.64.0.3/32 -p tcp --dport 80:80 -j TPROXY --tproxy-mark 0x1/0x1 --on-ip=127.0.0.1 --on-port=32817]","time":"2025-03-05T12:32:59.472Z"} {"file":"github.com/openziti/ziti/tunnel/intercept/tproxy/tproxy_linux.go:570","func":"github.com/openziti/ziti/tunnel/intercept/tproxy.(*tProxy).addInterceptAddr","level":"info","msg":"Adding rule iptables -t filter -A NF-INTERCEPT [-i ens160 -m comment --comment chandao -d 100.64.0.3/32 -p tcp --dport 80:80 -j ACCEPT]","time":"2025-03-05T12:32:59.474Z"} {"file":"github.com/openziti/ziti/tunnel/intercept/tproxy/tproxy_linux.go:556","func":"github.com/openziti/ziti/tunnel/intercept/tproxy.(*tProxy).addInterceptAddr","level":"info","msg":"Adding rule iptables -t mangle -A NF-INTERCEPT [-m comment --comment chandao -d 100.64.0.3/32 -p tcp --dport 8080:8080 -j TPROXY --tproxy-mark 0x1/0x1 --on-ip=127.0.0.1 --on-port=32817]","time":"2025-03-05T12:32:59.475Z"} {"file":"github.com/openziti/ziti/tunnel/intercept/tproxy/tproxy_linux.go:570","func":"github.com/openziti/ziti/tunnel/intercept/tproxy.(*tProxy).addInterceptAddr","level":"info","msg":"Adding rule iptables -t filter -A NF-INTERCEPT [-i ens160 -m comment --comment chandao -d 100.64.0.3/32 -p tcp --dport 8080:8080 -j ACCEPT]","time":"2025-03-05T12:32:59.477Z"} {"file":"github.com/openziti/ziti/tunnel/dns/server.go:271","func":"github.com/openziti/ziti/tunnel/dns.(*resolver).AddHostname","level":"info","msg":"adding chandao.idn = 100.64.0.3 to resolver","time":"2025-03-05T12:32:59.479Z"} {"file":"github.com/openziti/ziti/tunnel/intercept/tproxy/tproxy_linux.go:556","func":"github.com/openziti/ziti/tunnel/intercept/tproxy.(*tProxy).addInterceptAddr","level":"info","msg":"Adding rule iptables -t mangle -A NF-INTERCEPT [-m comment --comment chandao -d 192.16.1.3/32 -p tcp --dport 80:80 -j TPROXY --tproxy-mark 0x1/0x1 --on-ip=127.0.0.1 --on-port=32817]","time":"2025-03-05T12:32:59.479Z"} {"file":"github.com/openziti/ziti/tunnel/intercept/tproxy/tproxy_linux.go:570","func":"github.com/openziti/ziti/tunnel/intercept/tproxy.(*tProxy).addInterceptAddr","level":"info","msg":"Adding rule iptables -t filter -A NF-INTERCEPT [-i ens160 -m comment --comment chandao -d 192.16.1.3/32 -p tcp --dport 80:80 -j ACCEPT]","time":"2025-03-05T12:32:59.481Z"} {"file":"github.com/openziti/ziti/tunnel/intercept/tproxy/tproxy_linux.go:556","func":"github.com/openziti/ziti/tunnel/intercept/tproxy.(*tProxy).addInterceptAddr","level":"info","msg":"Adding rule iptables -t mangle -A NF-INTERCEPT [-m comment --comment chandao -d 192.16.1.3/32 -p tcp --dport 8080:8080 -j TPROXY --tproxy-mark 0x1/0x1 --on-ip=127.0.0.1 --on-port=32817]","time":"2025-03-05T12:32:59.482Z"} {"file":"github.com/openziti/ziti/tunnel/intercept/tproxy/tproxy_linux.go:570","func":"github.com/openziti/ziti/tunnel/intercept/tproxy.(*tProxy).addInterceptAddr","level":"info","msg":"Adding rule iptables -t filter -A NF-INTERCEPT [-i ens160 -m comment --comment chandao -d 192.16.1.3/32 -p tcp --dport 8080:8080 -j ACCEPT]","time":"2025-03-05T12:32:59.484Z"} ``` ---
**Author:** ![dariuszSki](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/dariuszski/32/339_2.png) [@dariuszSki](https://openziti.discourse.group/u/dariuszSki)\ **Post date:** [March 6, 2025, 4:06pm UTC](https://openziti.discourse.group/t/client-show-error-context-deadline-exceeded/3213/20 "2025-03-06T16:06:58Z")
Based on what is seen in the above logs, it looks like you are trying to reach 100.64.0.3:80 which is chandao.idn. ```auto {"file":"github.com/openziti/ziti/tunnel/intercept/tproxy/tproxy_linux.go:311","func":"github.com/openziti/ziti/tunnel/intercept/tproxy.(*tProxy).acceptTCP","level":"info","msg":"received connection: 100.64.0.3:80 --\u003e 100.64.0.1:56050","time":"2025-03-05T12:33:18.530Z"} {"ctrlId":"ctrl.myy.com","error":"context deadline exceeded","file":"github.com/openziti/ziti/router/xgress_edge_tunnel/fabric.go:269","func":"github.com/openziti/ziti/router/xgress_edge_tunnel.(*fabricProvider).tunnelServiceV1","level":"warning","msg":"failed to dial fabric","service":"chandao","time":"2025-03-05T12:33:18.530Z"} {"error":"context deadline exceeded","file":"github.com/openziti/ziti/tunnel/tunnel.go:51","func":"github.com/openziti/ziti/tunnel.DialAndRun","level":"error","msg":"tunnel failed","service":"chandao","time":"2025-03-05T12:33:18.530Z"} ``` [Next page](https://openziti.discourse.group/t/client-show-error-context-deadline-exceeded/3213.md?page=2)