A customer has and issue connecting to a OPC-UA server provided by a MLC.
WebIQ (pc based licese) <-> MLC
IO Handle configured and receiving "waiting for recconnect" message.
Testing so far:
UA client successfully connected to MLC OPC-UA server endpoint
WebIQ successfully connected to "opc.tcp://opcua.webiq.de:48010/WebIQ/DemoServer"
configure a IO Handle at an incorrect address, he receives different behaviour -> cycle between "connecting" & "waiting for reconnect"
So it looks like both server and client is working, just not with each other.
It appears as if WebIQ is being blocked in some way or is waiting for approval from the server.
Note: I've seen in another forum post that someone experience a similar issue and resolved it by reinstalling WebIQ Designer. However I would prefer to find a root cause before resorting to this.
Solved! Go to Solution.
As you are on a PC you can find all information in the log file %PROGRAMDATA%\WebIQ\connect.log - it might also help changing the log file severity to "trace" in the log file settings in WebIQ Designer.
Without this information no analysis is possible so if you cannot solve the issue with that information already can you please provide the log file here?
After obtaining the connect.log, we were able to see a BadCertificateValidation error.
Common error when the date and time is not the same on both server and client. The customer corrected the date and time on their MLC and WebIQ was able to connect successfully, but this only lasted ~6 hours after which we receive the same error.
The MLC date and time are correct so now even though we are using a non-secure connection, we check the rejected and trusted certs on the server. Here we find after a cert is trusted, it will re-appear as rejected. We noticed some of the folders here are dated 2042...(both systems are dated correctly, so it's unclear why)
The all certs were cleared from MLC, still nothing.
Now all certs cleared from C:\programData\WebIQ\io-shared\ (some certs here were also dated 2042), now the customer has a working system.
Some additional info: each TLS certificate in general has expiration dates and dates from when on they are valid. If the date/time on the system is way off and does not fall in the validity period of the certificate errors like these will occur by design.
This is not limited to WebIQ, but to any other system using these certificates so it will also happen on normal web servers as well.
Therefore having the correct time set on a system is always recommended, preferably by using NTP.