Error 5022 and manual activation timeouts
Posted by Dan H, Last modified by Dan H on 25 April 2019 05:01 PM
There is a 24-hour window from when the activation request data is created until the request is received and processed by SOLO Server.  The activation request data will contain an entry for the date and time the request was created.  When SOLO Server receives the request it will check this date/time in order to verify it is within the 24-hour window.  This is done using a server-side threshold value which is set to 24 hours for SOLO Server customers.  If an activation request is received by SOLO Server that is more than 24 hours old, an error 5022 is returned.  Customers who host SOLO Server have the option to modify the threshold, while SOLO Server Shared and Dedicated customers may not modify the threshold value as it is global.

As of February 13, 2018, this value has ever changed.  If the threshold was modified, we would most likely notify our existing customers.