Github Action self-hosted runner - error 400 refresh token
CompletedWe have an EC2 instance self-hosted runner that runs our GitHub Actions to compile the application software and uploads it to the Box. This setup has been working well so far since the EC2 instance runs 24/7 (it is expensive).
We are now pursuing a new initiative to use on-demand EC2 instances, where an EC2 instance starts up, runs the workflow, and then shuts down. Upon testing it; we are seeing the error below. The OAuth App that worked on the 24/7 EC2 instance is not working with the on-demand EC2 instance.
Please note that the 24/7 EC2 instance is still operational, and the same token works without any issues. The problem only arises with the on-demand EC2 instance. When created the dynamic EC2 instance, we took an image of the 24/7 that is used to create the dynamic EC2 instance.
How do we resolve this issue? What type of access to create to make the dynamic EC2 Instance work. I went over the different types of authorization but it was not so clear which fits our situation. I would a secret.user and secret.pass that we store on Github actions (secrets) can be an avenue, but I would like to ask before committing time.
BoxCLIError: Your refresh token has expired.
Please run this command "box login --name <ENVIRONMENT_NAME> --reauthorize" to reauthorize selected environment and then run your command again.
Caused by: Error: Expired Auth: Auth code or refresh token has expired [400 Bad Request] invalid_grant - Refresh token has expired
-
Hi Laith,
Welcome to the Box Community!
This would be something our Product Support team would like to investigate with you and may require specific account information.
I've gone ahead and created a ticket for you so that an agent can work directly with you on looking into this.
Kindly check your email for details and updates.
Best,
Ann
Please sign in to leave a comment.
Comments
1 comment