We have seen an instance of ‘Error 504’ being reported on the logon screen, and a related ‘timeout’ message during initial signup.
It seems likely that this is caused by particular ISPs having a short request timeout setting, which is affecting the polling mechanism in RapID.
A simple refresh of the login screen will fix this, and during initial sign-up it doesn’t adversely affect the operation.
We will provide a fix for it as soon as we have positively identified the cause, but meanwhile just refresh to work round the problem.
Viewing 1 post (of 1 total)
The forum ‘RapID Secure Login Knowledge base’ is closed to new topics and replies.