You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When deploying resources which have a private GitHub source created from the Private Repository (with GitHub App) option, this error often appears almost immediately after triggering the deployment:
2024-Dec-29 20:49:09.796095 Starting deployment of monorepo:wings:staging:mightywings to node-staging-mightywings.
2024-Dec-29 20:49:10.507605 Preparing container with helper image: ghcr.io/coollabsio/coolify-helper:1.0.4.
2024-Dec-29 20:49:10.914382 docker rm -f vo4c0g4kc8ow80804o884gg4
2024-Dec-29 20:49:10.914382 Error response from daemon: No such container: vo4c0g4kc8ow80804o884gg4
2024-Dec-29 20:49:11.290012 docker run -d --network coolify --name vo4c0g4kc8ow80804o884gg4 --rm -v /var/run/docker.sock:/var/run/docker.sock ghcr.io/coollabsio/coolify-helper:1.0.4
2024-Dec-29 20:49:11.290012 52dd64d762720394ff9fd2218ce6ae58aeb6efdb15688f1a33002ae2313ff2d5
2024-Dec-29 20:49:14.233401 Oops something is not okay, are you okay? 😢
2024-Dec-29 20:49:14.235961 Failed to get access token for GITHUB_APP_NAME with error: 'Expiration time' claim ('exp') is too far in the future
By "often appears", what I mean is it does not appear on every deployment. Sometimes it works just fine. It appears more frequently after not having deployed using the Github App for a long period of time.
My organization have been using Coolify for about 4 months and this error has only started appearing since about a month back. It seems like it's related to the GitHub app secret expiring. I will try dig up more information and update this task if I'm able to find any.
Steps to Reproduce
Create a Resource and select the Private Repository (with GitHubApp) option
Trigger a deployment of said service
Example Repository URL
No response
Coolify Version
v4.0.0-beta.380
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Debian 12
Additional Information
No response
The text was updated successfully, but these errors were encountered:
astrooom
added
🐛 Bug
Reported issues that need to be reproduced by the team.
🔍 Triage
Issues that need assessment and prioritization.
labels
Dec 29, 2024
astrooom
changed the title
[Bug]:
[Bug]: claim ('exp') is too far in the future
Dec 29, 2024
the exp error no longer appears. This is even though I had UTC set as my system date this whole time. I even re-synced the system time to UTC a couple times to be sure.
Error Message and Logs
When deploying resources which have a private GitHub source created from the
Private Repository (with GitHub App)
option, this error often appears almost immediately after triggering the deployment:By "often appears", what I mean is it does not appear on every deployment. Sometimes it works just fine. It appears more frequently after not having deployed using the Github App for a long period of time.
My organization have been using Coolify for about 4 months and this error has only started appearing since about a month back. It seems like it's related to the GitHub app secret expiring. I will try dig up more information and update this task if I'm able to find any.
Steps to Reproduce
Private Repository (with GitHubApp)
optionExample Repository URL
No response
Coolify Version
v4.0.0-beta.380
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Debian 12
Additional Information
No response
The text was updated successfully, but these errors were encountered: