# UascServerAsymmetricHandler Error when connecting to Ignition 8.1.2

**URL:** <https://forum.inductiveautomation.com/t/uascserverasymmetrichandler-error-when-connecting-to-ignition-8-1-2/49430>\
**Category:** Ignition\
**Created:** [August 1, 2021, 1:00am UTC](https://forum.inductiveautomation.com/t/uascserverasymmetrichandler-error-when-connecting-to-ignition-8-1-2/49430 "2021-08-01T01:00:07Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [August 1, 2021, 1:30am UTC](https://forum.inductiveautomation.com/t/uascserverasymmetrichandler-error-when-connecting-to-ignition-8-1-2/49430/2 "2021-08-01T01:30:03Z")

</div>

When Ignition’s server is only configured with Basic256Sha256 SecurityPolicy then most clients will need to be configured with the “discovery” URL, which for Ignition is `opc.tcp://hostname:62541/discovery`.

To get UaExpert connected you’ll need to be using the latest version (1.5.1) and use this discovery URL and the “custom discovery” option, not manually configure the endpoint details.

Kepware’s client is broken and unable to connect unless the “None” SecurityPolicy option is also configured.

---

_[View the full topic](https://forum.inductiveautomation.com/t/uascserverasymmetrichandler-error-when-connecting-to-ignition-8-1-2/49430)._