Prosys OPC UA Client连接配置循环问题求助

I’ve run into similar quirks with Prosys OPC UA Client’s discovery flow when working with NodeOPCUA servers, so let’s break down what’s likely happening and how to fix it. You’ve already confirmed the server works with other clients, so the issue is almost certainly with how Prosys is handling endpoint discovery or configuration matching.

Potential Fixes to Break the Loop #

1. Bypass Discovery by Entering the Endpoint Directly #

Prosys loves to default to auto-discovery even when you input a specific endpoint URL, which can cause this loop. Here’s how to skip that:

• Open Prosys and go to File > New Connection
• Look for a radio button or toggle labeled "Enter endpoint URL directly" (it might be under an "Advanced" section)
• Paste your exact endpoint URL (e.g., opc.tcp://your-server-ip:4840) and click next
• Select the security settings that match your NodeOPCUA server (most default setups use None for both security mode and policy)
• This should bypass the redundant discovery step that’s triggering the loop.

2. Align NodeOPCUA Server’s Application URI with Prosys’ Expectations #

That urn:NodeOPCUA-Server-default string is your server’s default application URI, and Prosys might be getting confused if it doesn’t match the endpoint’s context. Try explicitly setting a consistent URI in your server code:

const server = new OPCUAServer({
  port: 4840,
  serverInfo: {
    applicationUri: "urn:NodeOPCUA-Server-default", // Match what Prosys is picking up
    productUri: "urn:NodeOPCUA-Server-default"
  }
});

Restart the server after making this change, then try connecting again. This ensures Prosys sees a consistent identity between the endpoint and server.

3. Tweak Prosys’ Discovery Settings #

Prosys has hidden settings that force discovery even when you provide a URL. Disable these:

• Go to Tools > Options in Prosys
• Navigate to the Discovery tab
• Uncheck options like "Automatically discover servers when entering a URL" or "Use discovery server for endpoint resolution"
• Save the settings and start a fresh connection attempt.

4. Double-Check Security Settings Match Exactly #

Even though other clients work, Prosys is stricter about security parameter matching. Make sure:

• You select the same security mode (e.g., None, Sign, SignAndEncrypt) as your NodeOPCUA server
• Pick the corresponding security policy (e.g., None, Basic256Sha256)
• If your server uses authentication, enter the correct username/password before proceeding past the security step.

If none of these work, capturing a quick Wireshark trace of the connection attempt can help spot if Prosys is sending malformed discovery requests that the server is rejecting, which would cause the loop.

内容的提问来源于stack exchange，提问作者TwistedOwl