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

Continuously happening authorization error after a while of running #299

Open
Antondomashnev opened this issue Nov 30, 2016 · 3 comments
Open

Comments

@Antondomashnev
Copy link
Contributor

Unfortunately I don't have much to say in details. But I think since a week, I have to authorize the GitHub user which Builda is using everyday. Otherwise the syncer fails with the authorization error.

@krin-san
Copy link

krin-san commented Dec 8, 2016

+1 Same issue with my setup. I integrated with a BitbucketServer (forked repo build) and all works fine, but sometimes I notice that bots are not created for a new PR. When I see Buildasaur status, it says "401 Authorization error" and require to enter Captcha.

It brings me idea that Buildasaur sometimes lose the password or can't take it from keychain on some attempts - it becomes invalid or empty. After a few attempts to login on server with invalid/empty password account become locked until Captcha was entered.

Unfortunately I have no chance to debug it now. Maybe someone have more info on this issue.

@Antondomashnev
Copy link
Contributor Author

Antondomashnev commented Dec 20, 2016

UPD: It stopped happening for some reason, so far three days without authorization issue.

@krin-san
Copy link

krin-san commented Feb 6, 2017

I constantly getting this issue after my server re-establish VPN connection. Seems like a failure handler do smth that reset login/password cache and every next login attempt will be made with a wrong credentials.

Workaround: stop bot, login manually in browser to complete Captcha check, edit buildasaur bot configuration and complete first 2 steps (xcode server and bitbucket server connection) and press Cancel. And that's it! You can run bot again it it will perform login with a valid credentials.

Not sure thought where the issue reason located in source code. Just tried to describe a "blackbox" behavior overview.

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

No branches or pull requests

2 participants