# Getting error trying to connect to Ignition OPC UA Server with security Basic256Sha256 **URL:** \ **Category:** Ignition\ **Tags:** ignition81, security\ **Created:** [February 5, 2024, 4:21pm UTC](https://forum.inductiveautomation.com/t/getting-error-trying-to-connect-to-ignition-opc-ua-server-with-security-basic256sha256/85242 "2024-02-05T16:21:12Z")\ **Posts on this page:** 1\ **Showing post:** 7
**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:** [February 5, 2024, 4:31pm UTC](https://forum.inductiveautomation.com/t/getting-error-trying-to-connect-to-ignition-opc-ua-server-with-security-basic256sha256/85242/7 "2024-02-05T16:31:24Z")
Right, so this means your client is trying to open a secured connection to the wrong endpoint. There is a discovery endpoint at `opc.tcp://host:62541/discovery`. It accepts unsecured connections and implements the discovery services. The endpoints it returns contain URLs that point to the session endpoint at `opc.tcp://host:62541` (no /discovery). If your client / client library can't correctly use the endpoint URLs returned in the GetEndpoints response then it won't be able to connect. I've found that on order to connect broken clients like this to Ignition you have to enable the "None" security policy in the server and then point the client directly at the session endpoint instead. --- _[View the full topic](https://forum.inductiveautomation.com/t/getting-error-trying-to-connect-to-ignition-opc-ua-server-with-security-basic256sha256/85242)._