invalid_signature: The timestamp is too old.

Hi @lifesatomato,

Can you send a link to your site?

It sounds like your server’s time/date is misconfigured. Are you able to check the time configuration on your server is correct, or ask your host to do that for you?

Sorry I should have included it.

https://www.lifesatomato.com/

I will ask my host about the time configuration.

Thank you
Mike

Hi @lifesatomato,

Thanks — there appears to be a Jetpack connection error, which could be why you are having trouble viewing the stats. Would you please deactivate and delete the Jetpack plugin and then reinstall, reactivate and reconnect?

Thank you for your quick response. I deactivated/deleted/re-installed/reactivated/connected and I still get the same error.

Hi @lifesatomato,

Thanks for trying that. Were you able to contact your host to ask if there are any issues on their side?

They pointed me towards editing my php.ini file. I’m not sure what entries they think I could make that would correct this. If it was a timezone issue I would expect it to never work, right? It does work about 10% of the time if I keep refreshing the dashboard.

Mike

Interestingly and possibly related, I deactivated and reactived the plugin again and see this across the top of the page:

Error Details: The Jetpack server encountered the following client error: Verification took too long

Another thing I should add, I have not been able to reproduce this using the WP mobile app, just when I access the dashboard via Chrome on my notebook.

@lifesatomato Thanks for the update! You’re accessing the site in the WordPress.com mobile app through your site’s xmlrpc.php file, rather than the Jetpack connection. That’s why it works in the app but not on your computer.

I’m seeing a different error in the connection now. It seems like there is a misbehaving bit of code somewhere in your site.

If you go to here:

https://www.lifesatomato.com/xmlrpc.php

… you’ll see a message saying “XML-RPC server accepts POST requests only.” That’s the correct message.

However, the problem is that there’s also whitespace on that page, which suggests that some plugin, theme, or your wp-config.php file has extra whitespace before the first “<?php” in the file.

This problem is another symptom of a more common problem: the “Headers already sent” problem. More information on that is here:

https://codex.www.ads-software.com/FAQ_Troubleshooting#How_do_I_solve_the_Headers_already_sent_warning_problem.3F

Can you check your wp-config.php file, theme files, and plugins for that whitespace?

Once you’ve fixed the whitespace issue, your XML-RPC should look exactly like this:

https://jetpack.com/xmlrpc.php

Let me know how that goes and if you need any further help.

Thank you. I cleaned up my functions.php, which was adding the CR/LFs to the xmlrpc.php output. However, I still get the original message. I tried disabling plugins and didn’t find one that was causing the problem, however I can’t guarantee that I stopped every plugin. I’m going to try that again during a low-traffic time to see if it helps.

Regards
Mike

Hey Mike,

I’m seeing a good connection to Jetpack now with no errors at all anywhere on our side. Are you still seeing that timestamp error when trying to access the stats?

If so, I’d push back to your host and ask them to take a look at this for you. Everything looks great for us.

I hope that helps.

Hi Tracy. Thanks for checking. I do still get the message, but only about 50% of the time. I’ll contact my host. Thank you for all of your efforts I do greatly appreciate it.

Mike

It’s our pleasure! Let us know how it goes ??