#1 Handshake Error with Ampache v.3.5.4

[Jeremy Scherer]

After initial install I provided my server data, and when trying to refresh library I get:

Error Invalid Handshake - Login Failed, timestamp too old[Ampache Error: 401]

I have a feeling they changed the handshake format between when the latest version of "Windows Ampache Client" was released and 3.5.4 of Ampache:

http://ampache.org/wiki/dev:xmlapi

Thought I'd submit a bug because this is the cleanest, smallest UI I've found for streaming to Windows :)

[Daniel Wilson]

flare576

The issue seems to be around a time offset between the Ampache server and the client,, i.e. the clock on the server is ahead of the client so the timestamp generated by the client and used for authentication appears to the server to be very old, and so is not accepted.

Are the server and client using different timezones? If so, I'll have a think about how to work around as there doesn't seem to be an easy way to find out what timezone ampache is working in.

Regards,

danielmwilson

[Jeremy Scherer]

Server and client are running in the same timezone, and both clocks are correct. I'll give it another shot on Monday when I'm remote again!

[Jeremy Scherer]

I tried Refreshing the library again today, and received the same error message. The clocks were about 45 seconds off from each other, so I adjusted the server time to match the client (since the client is sync'd to a enterprise clock) and still got the same error.

Are there any sort of logs or messages from either client or server that I could provide to help figure out the problem?