Proclaim Error connecting to Song Select

I have been using Proclaim with SongSelect for quite some time now, but today Proclaim seems to be having a problem connecting to SongSelect. Is anyone else seeing this?
2012-03-17 16:59:57.4531 6 Error ProclaimWebClient WebServiceException for SongSelectSongs with uri=https://production.songselectapi.com/v1/songs/find/there: Libronix.Utility.Net.WebServiceException: Exception of type 'Libronix.Utility.Net.WebServiceException' was thrown. Request: GET https://production.songselectapi.com/v1/songs/find/there (status BadRequest, content type 'application/json; charset=utf-8').
at Libronix.Utility.Net.WebServiceRequest.ExecuteResponseSync(HttpWebRequest webRequest, IWorkState state)
at Libronix.Utility.Net.WebServiceRequest.GetResponse(IWorkState state)
at Libronix.Utility.Net.WebServiceRequest.GetResponse()
at Libronix.Utility.Json.Web.JsonWebServiceRequest.GetResponse()
at Libronix.Utility.Json.Web.JsonWebServiceRequest`1.GetResponse()
at Logos.Proclaim.Common.ProclaimWebServiceRequest`1.Invoke()
content: {"advice":"The timestamp is too far in the future, it must be at most 450 seconds after the server current date and time","problem":"timestamp_refused"}
2012-03-17 17:00:01.3906 8 Error ProclaimWebClient WebServiceException for SongSelectSongs with uri=https://production.songselectapi.com/v1/songs/find/there%20is%20a%20redeemer: Libronix.Utility.Net.WebServiceException: Exception of type 'Libronix.Utility.Net.WebServiceException' was thrown. Request: GET https://production.songselectapi.com/v1/songs/find/there%20is%20a%20redeemer (status BadRequest, content type 'application/json; charset=utf-8').
at Libronix.Utility.Net.WebServiceRequest.ExecuteResponseSync(HttpWebRequest webRequest, IWorkState state)
at Libronix.Utility.Net.WebServiceRequest.GetResponse(IWorkState state)
at Libronix.Utility.Net.WebServiceRequest.GetResponse()
at Libronix.Utility.Json.Web.JsonWebServiceRequest.GetResponse()
at Libronix.Utility.Json.Web.JsonWebServiceRequest`1.GetResponse()
at Logos.Proclaim.Common.ProclaimWebServiceRequest`1.Invoke()
content: {"advice":"The timestamp is too far in the future, it must be at most 450 seconds after the server current date and time","problem":"timestamp_refused"}
Comments
-
Looks like your system time is ahead if the SongSelect server by more than 7.5 minutes. I have verified it still works on my machine, hopefully ruling out the possibility of the SongSelect server time being off. Does this explain it for you?
0