Greetings,
we have a trouble with a 3rd part OPC-UA with error:
"status=Bad_InvalidTimestamp, description=The timestamp is outside the range allowed by the server."
we can't connect to it from Ignition, but the programmer is able to work as usual (everything is working fine on his part).
We checked the timezone and the difference is question of minutes (like 10 minutes past our gateway time).
Is it possible to "validate the time" on the OPC-UA server or to check other configuration on the PLC to check wich timestamp is giving to us? The PLC was working fine until yesterday, then the connection became faulted and we can't connect.
If you need any further informations, i can give them to you.
Thank you in advance, we're struggling on this since yesterday
Can you click show full details and copy the full error here?
Sure!
here's the full message:
UaServiceFaultException: status=Bad_InvalidTimestamp, message=The timestamp is outside the range allowed by the server.
at org.eclipse.milo.opcua.stack.client.UaStackClient.lambda$deliverResponse$5(UaStackClient.java:337)
at org.eclipse.milo.opcua.stack.core.util.ExecutionQueue$InlineTask.run(ExecutionQueue.java:154)
at org.eclipse.milo.opcua.stack.core.util.ExecutionQueue$Task.run(ExecutionQueue.java:136)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)
8.1.37 (b2024013011)
Azul Systems, Inc. 17.0.9
Hmm, still not sure why this is happening. It seems to be a service fault response from the server, not something related to certificates like my initial hunch.
You'll probably have to turn off security for the connection (SecurityPolicy=None) and then get a Wireshark capture to further troubleshoot.
This is probably the issue. There's probably some allowable gap between client and server time that has been exceeded.
Unfortunately this is something being enforced on the server/PLC you are connected to, not the Ignition side, so I can't offer you any settings to turn it off.
You'll have to either synchronize the times or figure out if the server/PLC you're connected to has configuration to increase the gap or turn off the check.
Thank you Kevin,
i checked the Security Policy and is set to "None":
we asked now to the PLC's programmer to check if this configuration is possible on his machine; just in case is needed, do i have to open a new ticket with support sending the wireshark capture?
You can upload the Wireshark capture here, or I can provide a dropbox link if needed.
I'm not sure it's going to be much help, it's mostly just because I'm curious to see the timestamps and what request it fails on.
1 Like
Hello Kevin,
sorry to let you wait. Yesterday the PLC's programmer finally simply syncronize his clock with ours and everything works perfectly.
So, for everyone coming in this topic using the error's name: even if is a difference of minutes (not timezone), the clocks needs to be syncronized.
Thank you a lot Kevin!
