Access Denied on Ubuntu Server, fine on CentOS test server

Ok, this is switching to support request - because I deployed the same app to my CentOS test server and it worked fine. So it seems there is an issue specifically on the Ubuntu Server production box. It belongs to a client and I have no other Ubuntu hardware to play with right now. Anything Ubuntu needs to have installed? I shouldn't have thought so. This is most odd! =/

Another quick update - admin form consistently fails everywhere. =(

But there's probably other issues dedicated to that...

Hi,

Thanks for coming back so quick. So, it's PHP 5.2.11 on Ubuntu - PHP 5.2.6 on the CentOS box and on my local Fedora machine.

The error was masked by this bug: #657444: xmlrpc_server can't handle some error responses

But once I got the error object in to watchdog, I could see it was actually Token has expired.

Token generating PHP looks like this, and works fine everywhere else I use it with the Drupal Services module:

/**
 * Function for generating a random string, used for
 * generating a token for the XML-RPC session
 */
function getUniqueCode($length = "") {
  $code = md5(uniqid(rand(), true));
  if ($length != "") return substr($code, 0, $length);
  else return $code;
}

// set vars for this connection
$nonce = getUniqueCode("10");
$method_name = 'user.login';
$timestamp = (string) strtotime("now");
$required_args = array();

// now prepare a hash
$hash_parameters = array(
  $timestamp,
  $domain,
  $nonce,
  $method_name,
);

$hash = hash_hmac("sha256", implode(';', $hash_parameters), $kid);

// prepared the arguments for this service
$required_args = array(
  $hash,
  $domain,
  $timestamp,
  $nonce,
  $response['sessid'],
);

So could PHP 5.2.11 cause issues with Services' ability to decipher tokens? Like I say, PHP 5.2.6 on CentOS, no worries. =/

Ahhhh, yes!!! LOL. Let me try that out.

Yup, timezone it was. Thank you so much! It's always the silly little things that catch me out. =)

For reference, adjusted line was:

$timestamp = (string) strtotime("+1 hour");

Actually, you know what? I set the time back to "now" out of curiosity and it still works. But while I was at it, I remember the server clock was wrong and updated it. So actually, it was an incorrect server clock that was killing me, not timezones. But you put me on to it. Would *expect* timezones to potentially cause issues, but it seems timestamps work regardless of server timezone - guess they're all GMT.