# Gateway Network - Unable To Establish Connection

**URL:** <https://forum.inductiveautomation.com/t/gateway-network-unable-to-establish-connection/57457>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [March 22, 2022, 2:26pm UTC](https://forum.inductiveautomation.com/t/gateway-network-unable-to-establish-connection/57457 "2022-03-22T14:26:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![scott.stamps](https://avatars.discourse-cdn.com/v4/letter/s/ba9def/32.png) [@scott.stamps](https://forum.inductiveautomation.com/u/scott.stamps)\
**Post date:** [March 22, 2022, 2:26pm UTC](https://forum.inductiveautomation.com/t/gateway-network-unable-to-establish-connection/57457/1 "2022-03-22T14:26:19Z")

</div>

We have a Gateway (A) which was cloned to give us Gateway (B).

Within _Config \> Network \> Gateway Network Settings_, when attempting to set up a Gateway Network from A \> B, you are presented with the usual options to approve/deny on the _Incoming Connections_ tab on B. After approving and returning to A, the _Outgoing Connection_ to B remains in a state of Faulted.

What we’ve checked:  
1.) The UUID values. These are now unique (because of the clone, they initially weren’t)  
2.) Under the _Diagnostics Tab_ \> _Local Certificate Information_, Gateway A’s name is the Common Name - which, because of the clone, makes sense but we are wondering if this could be causing the connection to fault. Additionally, if this has merit, how would you go about removing/re-adding this so that B’s name shows here, as you would expect.

 ![Screenshot 2022-03-23 081617-2](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/0/20777455f32c681500aa457f67a9c3db7d23e578.png)

Thank you

---

<div class="post-metadata">

**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\
**Post date:** [March 23, 2022, 2:00pm UTC](https://forum.inductiveautomation.com/t/gateway-network-unable-to-establish-connection/57457/2 "2022-03-23T14:00:02Z")

</div>

The simplest option might be to just remove the `<IGNITION_INSTALL_LOCATION>/webserver/metro-keystore` file and restart Gateway (B). The local certificate will be regenerated on startup if the file is missing (and will base its generation on the hostname of the system, so make sure that has been updated beforehand).

---

<div class="post-metadata">

**Author:** ![scott.stamps](https://avatars.discourse-cdn.com/v4/letter/s/ba9def/32.png) [@scott.stamps](https://forum.inductiveautomation.com/u/scott.stamps)\
**Post date:** [March 23, 2022, 8:14pm UTC](https://forum.inductiveautomation.com/t/gateway-network-unable-to-establish-connection/57457/3 "2022-03-23T20:14:09Z")

</div>

Great - we’ll give this a shot. Thank you.