Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

  1. ,
    Expert tip

    Check if you don't have a VPN or something like this messing with your connection. Also, check Jenkins DNS configurations (try to start it with "--dns".

Solutions on the web

via by Unknown author, 1 year ago
via Jenkins JIRA by OHTAKE Tomohiro, 1 year ago
via Jenkins JIRA by OHTAKE Tomohiro, 1 year ago
via GitHub by wbmacleod
, 6 months ago
via GitHub by Siedlerchr
, 1 year ago
via GitHub by rvb-033
, 1 year ago	at	at	at	at	at	at	at	at	at	at	at	at	at	at	at	at org.kohsuke.github.Requester.parse(	at org.kohsuke.github.Requester._to(	at	at org.kohsuke.github.GitHub.getMyself(	at org.kohsuke.github.GitHub.(	at org.kohsuke.github.GitHub.connectUsingOAuth(	at org.jenkinsci.plugins.ghprb.GhprbGitHub.connect(	at org.jenkinsci.plugins.ghprb.GhprbGitHub.get(	at org.jenkinsci.plugins.ghprb.GhprbRepository.initGhRepository(	at org.jenkinsci.plugins.ghprb.GhprbRepository.check(	at	at	at hudson.triggers.Trigger.checkTriggers(	at hudson.triggers.Trigger$Cron.doRun(	at	at java.util.concurrent.Executors$	at java.util.concurrent.FutureTask.runAndReset(	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(	at java.util.concurrent.ScheduledThreadPoolExecutor$	at java.util.concurrent.ThreadPoolExecutor.runWorker(	at java.util.concurrent.ThreadPoolExecutor$