-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not authorize build request #733
Comments
Thanks for reporting, @kolpav! First off, have you been able to figure this out already? If not, could you please send us an email at [email protected] ? "Could not authorize build request for ... " usually means that the account run out of trial builds or has not an active subscription on travis-ci.com We'll look into documenting the possible messages in the Requests page soon, thank you! |
You are right I have run out of trial builds and got confused by vague error message. Thank you |
@MariadeAnton - Just ran into this myself. A better message would be very helpful. |
Seriously please have better message... |
Is it possible to transfer a subscription to an organization? Ran into this ourselves. We subscribed under our organizations owner account, but not the organization itself. |
@stevebauman please can you send the details of this to [email protected] and we can follow up on your reply. Thanks |
You've fixed it - the subscription has been transferred. Thanks so much for your quick assistance @muizzk! |
It's 2020 and the message still shows: "Could not authorize build request for.." 4 years seems a reasonable time frame to fix an error message. I lost one day verifying token permissions and testing in other repos because of this. |
Hello @khose , it seems like you have run out of trial builds on your personal account. That is the reason you are getting this error message. Please reach us from [email protected] so that we can help you out! Thanks |
Was getting this message and stumbled upon this thread. I am on free subscription of Travis. The main culprit was that my repository was |
This happened to me because I created an organization where I imported my repos but the organization didn't have any plan selected. I selected the free plan and the build started after another trigger. |
For anyone who comes here from google, this was the fix for me. If things were working prior to migrating from travis-ci.org to travis-ci.com and you get the error message |
For me selecting a plan for the organisation the repo belongs to (different than your personal plan) did the job. |
This looks like a fairly serious, non-intuitive oversight for the .org to .com migration. I also found that the only error message I was getting was "Could not authorize build", and without this thread there would have been absolutely no way to know that no plan was selected. |
Absolutely agree. It almost caused me to give up!
…On Fri, Jun 18, 2021 at 9:09 AM Chris Down ***@***.***> wrote:
This happened to me because I created an organization where I imported my
repos but the organization didn't have any plan selected.
This looks like a fairly serious, non-intuitive oversight for the .org to
.com migration. I also found that the only error message I was getting was
"Could not authorize build", and without this thread there would have been
absolutely no way to know that no plan was selected.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#733 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACOZLQ7KEGSRMVQ32Q5XH4TTTNAQBANCNFSM4CPYP6DA>
.
|
I don't understand why you should select the free plan. If there is no plan chosen, just select the free plan. If you have an organization, you should select the free plan and select it on the next page one more time to select it effectively. This is so confusing. |
Why is there such a design, since I clicked "FREE", why is there such a situation as expired? |
My builds suddenly stopped working. I found nothing on google this is the error message I am getting
The text was updated successfully, but these errors were encountered: