<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Activity for malte</title><link href="https://forge.codesys.com/u/malte/activity/" rel="alternate"/><id>https://forge.codesys.com/u/malte/activity/</id><updated>2025-10-28T20:51:51.193000Z</updated><subtitle>Recent activity for malte</subtitle><entry><title>malte posted a comment on discussion Engineering 🇬🇧</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/cb996a6864/?limit=25#1c5f" rel="alternate"/><published>2025-10-28T20:51:51.193000Z</published><updated>2025-10-28T20:51:51.193000Z</updated><author><name>malte</name><uri>https://forge.codesys.com/u/malte/profile/</uri></author><id>https://forge.codesys.com/forge/talk/Engineering/thread/cb996a6864/?limit=25#1c5f</id><summary type="html">My CODESYS OPC UA server provides endpoints using both the hostname and the IP address. Connecting via the IP address works fine, but connecting via the hostname does not. The endpoint list shows both opc.tcp://&lt;hostname&gt;:4840 and opc.tcp://&lt;ip&gt;:4840. When using the hostname, the OPC UA client (UA Expert) fails to connect. Using the IP address connects without issues. Main goal is to conect via Python but opcua-asyncio seems to prefer the hostname. How can I configure CODESYS or my system so that...</summary></entry></feed>