Oauth authorization timestamp refused

Source: Internet
Author: User
400 timestamp_refused/oauth/request_tokenThe codes of machines 161 and 155 are the same, but during deployment of machines 155, oauth is required to authorize the user to start. Authorization always fails, but 161 is okay! Searching the API and modifying the Schell file will not help... I found an explanation of the problem online, it probably means that the timestamp of the server parameter required to generate the oauth authentication signature is incorrect. I compared the time of the two servers and found that the time of the 155 server was 10 minutes faster than that of the 161 server. 161, but only two minutes
161 10:05:33 155 10:15:23 Local Machine 10:03:12
It is possible that the time at which the liunx system server provider is located is faster than ours, so I first raised doubts like 155 machine time, changed 155 machine time to 161 machine time, then restarted, and authorized OK!

Oauth authorization timestamp refused

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.