# Edge Tunnel (v1.2.7) Fails to Connect to public Router

**URL:** <https://openziti.discourse.group/t/edge-tunnel-v1-2-7-fails-to-connect-to-public-router/4777>\
**Category:** Uncategorized\
**Created:** [June 24, 2025, 9:17pm UTC](https://openziti.discourse.group/t/edge-tunnel-v1-2-7-fails-to-connect-to-public-router/4777 "2025-06-24T21:17:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ss\_vinoth22](https://avatars.discourse-cdn.com/v4/letter/s/ecccb3/32.png) [@ss\_vinoth22](https://openziti.discourse.group/u/ss_vinoth22)\
**Post date:** [June 24, 2025, 9:17pm UTC](https://openziti.discourse.group/t/edge-tunnel-v1-2-7-fails-to-connect-to-public-router/4777/1 "2025-06-24T21:17:35Z")

</div>

We have two public edge routers — one deployed on GKE and another on a Google Cloud VM.  
Both the Ziti controller and router are running version **1.1.5**.

Existing identities are able to connect to the **Google VM-based public edge router** without any issues. However, new identities using edge tunnels (SDK version **1.2.7** ) running on IoT devices are consistently **aborting** when attempting to connect **only to the Google VM router**.

```auto

_connect() ch[0] failed to connect to ER[gcp-edge-pub-router] [-103/software caused connection abort]
_connect() ch[0] failed to connect to ER[gcp-edge-pub-router] [-103/software caused connection abort]
_connect() ch[0] failed to connect to ER[gcp-edge-pub-router] [-103/software caused connection abort]
_connect() ch[0] failed to connect to ER[gcp-edge-pub-router] [-103/software caused connection abort]
_connect() ch[0] failed to connect to ER[gcp-edge-pub-router] [-103/software caused connection abort]

```

From IOT i tested  
nc -vz 35.xx.xx.xxx 443  
Connection to 35.xxx.xxxx.xxx 443 port [tcp/https] succeeded!

so it can reach Google VM so i dont know why router is rejecting?  
do i need to manage any version specific to make it work?

Please advise on how to proceed or investigate this further.

---

<div class="post-metadata">

**Author:** ![ss\_vinoth22](https://avatars.discourse-cdn.com/v4/letter/s/ecccb3/32.png) [@ss\_vinoth22](https://openziti.discourse.group/u/ss_vinoth22)\
**Post date:** [June 25, 2025, 4:47am UTC](https://openziti.discourse.group/t/edge-tunnel-v1-2-7-fails-to-connect-to-public-router/4777/2 "2025-06-25T04:47:53Z")

</div>

The issue was caused by **FortiGate overwriting the certificate** when connecting via IP. It only allows proper TLS verification when using a **DNS name**. So I re-created the public router using **DNS in the advertise address** , and that resolved the problem.
