# Bad\_GatewayCommOff in designer, OPC UA crash?

**URL:** <https://forum.inductiveautomation.com/t/bad-gatewaycommoff-in-designer-opc-ua-crash/21874>\
**Category:** Ignition Early Access\
**Created:** [January 14, 2019, 9:16pm UTC](https://forum.inductiveautomation.com/t/bad-gatewaycommoff-in-designer-opc-ua-crash/21874 "2019-01-14T21:16:44Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![hunterdg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/hunterdg/32/67774_2.png) [@hunterdg](https://forum.inductiveautomation.com/u/hunterdg)\
**Post date:** [January 14, 2019, 9:16pm UTC](https://forum.inductiveautomation.com/t/bad-gatewaycommoff-in-designer-opc-ua-crash/21874/1 "2019-01-14T21:16:44Z")

</div>

Found beta HMI screeens non-functional this morning - all tags had lost communication. All OPC UA Devices were listed as “Enabled”

After some digging, i restarted the Logix Driver Module driver (no effect) and then the OPC UA (8.0.0-beta0 (b2018121802)) which seems to have resolve the issue

Here’s the log entry that seems to be responsible/ More info available upon request.

| UascClientMessageHandler | 12Jan2019 13:38:23 | Error validating chunk headers: received unknown secure channel token: tokenId=258 currentTokenId=257 previousTokenId=256 |
| --- | --- | --- |
| org.eclipse.milo.opcua.stack.core.UaException: received unknown secure channel token: tokenId=258 currentTokenId=257 previousTokenId=256 | | |

at org.eclipse.milo.opcua.stack.client.transport.uasc.UascClientMessageHandler.validateChunkHeaders(UascClientMessageHandler.java:698)  
at org.eclipse.milo.opcua.stack.client.transport.uasc.UascClientMessageHandler.lambda$onSecureMessage$10(UascClientMessageHandler.java:617)  
at org.eclipse.milo.opcua.stack.core.channel.SerializationQueue.lambda$decode$1(SerializationQueue.java:67)  
at org.eclipse.milo.opcua.stack.core.util.ExecutionQueue$PollAndExecute.run(ExecutionQueue.java:107)  
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)  
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)  
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)  
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)  
at java.base/java.lang.Thread.run(Unknown Source)|

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [January 14, 2019, 9:20pm UTC](https://forum.inductiveautomation.com/t/bad-gatewaycommoff-in-designer-opc-ua-crash/21874/2 "2019-01-14T21:20:03Z")

</div>

Can you provide the entire log export or zip up the wrapper.log files and attach or email them to us?

Do you have any additional OPC UA connections aside from the default “loopback” connection to Ignition’s server?

---

<div class="post-metadata">

**Author:** ![hunterdg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/hunterdg/32/67774_2.png) [@hunterdg](https://forum.inductiveautomation.com/u/hunterdg)\
**Post date:** [January 14, 2019, 9:27pm UTC](https://forum.inductiveautomation.com/t/bad-gatewaycommoff-in-designer-opc-ua-crash/21874/3 "2019-01-14T21:27:21Z")

</div>

Only the one loopback, but ~15 device connections. Sending you a PM

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [January 14, 2019, 9:52pm UTC](https://forum.inductiveautomation.com/t/bad-gatewaycommoff-in-designer-opc-ua-crash/21874/4 "2019-01-14T21:52:31Z")

</div>

Thanks, got your logs. Can you upgrade to the latest release and let me know if it happens again? It looks like your OPC UA module is from Dec 18th.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [January 15, 2019, 12:34am UTC](https://forum.inductiveautomation.com/t/bad-gatewaycommoff-in-designer-opc-ua-crash/21874/7 "2019-01-15T00:34:38Z")

</div>

If you updated to the latest build I think you would continue to see this periodically but the connection should recover automatically. There were a lot of different errors in your logs and I’m not sure this one was the root cause of what you were observing or not.

I can’t reproduce this since it’s a race condition, but I did find a place that it could be happening and fix it, so one of nightly builds this week will contain a possible fix.

---

<div class="post-metadata">

**Author:** ![hunterdg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/hunterdg/32/67774_2.png) [@hunterdg](https://forum.inductiveautomation.com/u/hunterdg)\
**Post date:** [January 16, 2019, 3:16pm UTC](https://forum.inductiveautomation.com/t/bad-gatewaycommoff-in-designer-opc-ua-crash/21874/8 "2019-01-16T15:16:22Z")

</div>

I look forward to it. Happened again overnight.

---

<div class="post-metadata">

**Author:** ![awalker](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/awalker/32/6874_2.png) [@awalker](https://forum.inductiveautomation.com/u/awalker)\
**Post date:** [February 8, 2019, 9:39pm UTC](https://forum.inductiveautomation.com/t/bad-gatewaycommoff-in-designer-opc-ua-crash/21874/9 "2019-02-08T21:39:45Z")

</div>

This issue should be fixed in the newest build.  
Let us know if you continue to see this behavior after upgrading.
