-
-
Notifications
You must be signed in to change notification settings - Fork 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
[Bug]: claim ('exp') is too far in the future #4702
Comments
I've noticed the same error message also appears when syncing the Github App Name at
|
Ok, this is super strange. After setting my Coolify VPS to exactly match the time of GitHubs API, using:
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: