Deployment failed: Invalid authentication

Bugs
1

Deployments started failing for us due to the following error:

Cannot build Application “XXXXX” due to an error with git: Error { code: -16, klass: -16, message: "Invalid authentication: Exhausted all available auth method to fetch repository

Is this some permission problem on our end or Qovery?

2

Hey !

Github changes a bit how token work recently, we made changes accordingly, maybe your token got invalidated in-between.
Do you mind retrying to see if it fails again?

Thanks

3

Yeah, it works OK now.

4

Hi @bchastanier, we are having the same issue again.

5

Hi @bchastanier, the issue was not solved, we periodically see these errors. It seems as if we would hit some sort of API rate limit.

6

Hi @prki,

Let me circle it back internally. Can you please share execution IDs or anything I can use to investigate this one please?

Thanks

7

I can’t access old deployment logs so I will have to wait for the next occurrence. We also see an issue that is likely related: sometimes we cannot change the branch of an application because the GitHub integration is failing, it’s being reported as just “internal server error”.

1 Like
8

Hi @prki,

Following recent Github changes, token mechanics has changed a bit as explained earlier. We need to fix it asap, and this matter will be working on during this sprint on our end, so should have a fix quickly.
Sorry about that …

9

Hi @bchastanier,

Was this ever fixed? We are still occasionally get these errors:

Cannot build Application “z4bec7b83” due to an error with git: Error { code: -16, klass: -16, message: "Invalid authentication: Exhausted all available auth method to fetch repository

I don’t see execution id anywhere in the deployment logs but I have deployment request 06b27686-2a51-4231-a028-ef090cfba5f3-430-1674568521 id.

1 Like
11

Hi back,

You are correct, 06b27686-2a51-4231-a028-ef090cfba5f3-430-1674568521 is the execution Id.
After taking a look at the log of your deployment, it seems indeed that we started to execute your deployment while your GitHub token was set to expire a few minutes later.
It should not happen as we force re-generate a new one before triggering a deployment.
I am looking at the possible issue that may cause that.

12

Just to let you know, we are going to land a fix for that next week.

1 Like
13

Hi back @prki ,

The fix landed in production, let me know if you still encounter this kind of issue.

14

Thanks @Erebe, I will keep an eye out if we see it again.

15

@Erebe we just encountered the same error again, execution id: 06b27686-2a51-4231-a028-ef090cfba5f3-475-1675160220

16

Indeed, I just saw it in our logs, fixing the issue.

17

Just landed the fix for the transport error, I monitoring, but If you endup seeing it again let me know.