Skip to content
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

Closed
kolpav opened this issue Sep 15, 2016 · 17 comments
Closed

Could not authorize build request #733

kolpav opened this issue Sep 15, 2016 · 17 comments
Labels

Comments

@kolpav
Copy link

kolpav commented Sep 15, 2016

My builds suddenly stopped working. I found nothing on google this is the error message I am getting this

@MariadeAnton
Copy link
Contributor

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!

@kolpav
Copy link
Author

kolpav commented Sep 25, 2016

You are right I have run out of trial builds and got confused by vague error message. Thank you

@kolpav kolpav closed this as completed Sep 25, 2016
@jmichaelprobert
Copy link

@MariadeAnton - Just ran into this myself. A better message would be very helpful.

@bj97301
Copy link

bj97301 commented Aug 24, 2018

Seriously please have better message...

@stevebauman
Copy link

stevebauman commented Nov 18, 2019

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.

@muizzk
Copy link
Contributor

muizzk commented Nov 18, 2019

@stevebauman please can you send the details of this to [email protected] and we can follow up on your reply. Thanks

@stevebauman
Copy link

You've fixed it - the subscription has been transferred. Thanks so much for your quick assistance @muizzk!

@khose
Copy link

khose commented May 21, 2020

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.

@mustafa-travisci
Copy link
Contributor

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

@Xonshiz
Copy link

Xonshiz commented Jan 13, 2021

Was getting this message and stumbled upon this thread. I am on free subscription of Travis. The main culprit was that my repository was private. As soon as I made it public, the builds triggered just fine.

@tannerhallman
Copy link

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.

@Verron
Copy link

Verron commented Jun 10, 2021

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 Could not authorize build request for. Go to travis-ci.com (make sure it isn't travis-ci.org), Click User (top right) > Settings > Your Organization > Plan then choose your plan.

@biphasic
Copy link

For me selecting a plan for the organisation the repo belongs to (different than your personal plan) did the job.

@cdown
Copy link

cdown commented Jun 18, 2021

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.

@tannerhallman
Copy link

tannerhallman commented Jun 18, 2021 via email

@gerardnico
Copy link

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.

@zongzi531
Copy link

Why is there such a design, since I clicked "FREE", why is there such a situation as expired?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests