https://forge.codesys.com/u/baltzer/activity/2026-08-06T20:51:38.097000ZRecent activity for baltzer2026-08-06T20:51:38.097000Z2026-08-06T20:51:38.097000Zbaltzerhttps://forge.codesys.com/u/baltzer/profile/https://forge.codesys.com/forge/talk/Engineering/thread/49500df473/?limit=25#a727

Follow-up: working workaround found (routing TLS outside CODESYS) For anyone finding this thread later with the same problem (a third-party device presenting a self-signed and/or expired certificate that ICertificateVerifier/udiVerificationMode won't let you connect through) - we never got a working fix within NBS itself, but found a practical workaround worth sharing. Approach: run a local TLS-terminating proxy on the same host as the CODESYS runtime, and have CODESYS talk plain, unencrypted TCP...

2026-07-26T09:53:55.607000Z2026-07-26T09:53:55.607000Zbaltzerhttps://forge.codesys.com/u/baltzer/profile/https://forge.codesys.com/forge/talk/Engineering/thread/49500df473/?limit=25#b54d

Setup: Net Base Services (NBS), TCP_Client + TLSContext, ePurpose := CLIENT_SIDE, connecting to a third-party embedded device (Velux KLF200 home automation gateway) whose factory-installed TLS certificate expired on 2026-07-12 and has no user-facing renewal path. Tested on both CODESYS Control for Raspberry Pi SL (3.5.19.0) and CODESYS Control Win V3 x64, with identical results on both. Goal: Accept the peer's expired certificate via a custom ICertificateVerifier implementation, since the certificate...