Peer rejected timestamp of our OAuth request although servers are on the same machine.

JIRA and FishEye appear to lose app-link connection randomly. Restarting JIRA appears to fix this issue temporarily. Trying to figure out what the issue could be as both JIRA and Fisheye/Crucible are on the same machine. Any ideas?

The exact error is:

"Peer rejected the timestamp on our OAuth request. This might be due to a replay attack, but its more likely our system clock is not synchronized with the server's clock."

 

JIRA 6.4.13

Fisheye/Cruc - 3.3.2

 

3 answers

Do you have any antivirus or network analyzer/checker software that can harm the connection?

No I do not.

Could this be potentially a result of our internal Jira/Fisheye system times being about an hour behind the actual worlds time?

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Bridget Sauer
Published Thursday in Marketplace Apps

Calling all developers––You're invited to Atlas Camp 2018

 Atlas Camp   is our developer event which will take place in Barcelona, Spain  from the 6th -7th of   September . This is a great opportunity to meet other developers and get n...

242 views 0 6
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you