Quote:
Originally Posted by NickVas
No it is not official.
But it is looks like it is the problem of SSL cert expiring. That's why it is works if you change a computer date.
Very strange that it tooks so long to fix this problem. Looks like there is no anyone in Lock support. Bad sign...
I have changed the date/time early and it worked for a while, now nothing.
if it was a cert issue it is as simple as going to your provider, generate a cert, put it on the server, and restart the app on every node on the cluster. Your can write a perl/shell/etc. script and ftps it everywhere and restart in a matters of moments. Every system adm has a script that does that in there homeDIR
and it gets the system time from the physical server.
it looks like if code issue because a cert issue takes minutes to resolve