Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Probot failing to start with bad JWT expiration too far in the future

See original GitHub issue

Bug Report

Current Behavior Starting the bot with probot run ./dist/index.js throws an error:

ERROR probot: 'Expiration time' claim ('exp') is too far in the future

Expected behavior/code Probot should start with the current configuration without erroring.

Environment

Probot version(s): 9.11.5
Node/npm version: Node v12.18.0/npm 6.14.4
OS: Ubuntu 20.04 - WSL 2.0 [Windows 10]

Possible Solution This started happening 7/6/20. I should also add that I am using the @octokit/rest module as well for github api calls outside of the app which failed with the same message. I was generating my own JWT with an exp of 10 minutes but when I switched it to 9 minutes I no longer received this error.

Issue Analytics

State:
Created 3 years ago
Comments:5 (1 by maintainers)

Top GitHub Comments

1reaction

amamutcommented, Jul 9, 2020

@gr2m You were right! The WSL was out of sync with the system time and required me to either do a sudo hwclock -s or a wsl --shutdown in powershell. After doing that time synced up and works fine.

Thanks!

0reactions

amamutcommented, Jul 8, 2020

I’m running probot locally and authenticating manually with @octokit/rest works fine but probot errors. This is github.com as well.