"No GitHub API authentication" error

[tomjoht]

Before submitting an issue, please be sure to

• Read the contributing instructions
• Update to the latest Gem version (either gem update github-pages or bundle update github-pages)

This issue affects

• The site generated by GitHub Pages
• Building sites locally

What did you do (e.g., steps to reproduce)

Add this into the Gemfile:

source "https://rubygems.org"

gem 'github-pages', group: :jekyll_plugins

Run bundle update and bundle exec jekyll serve.
Make a small edit to a file.
When Jekyll auto-rebuilds, an error appears in the Terminal that says "GitHub Metadata: No GitHub API authentication could be found. Some fields may be missing or have incorrect data."

What did you expect to happen?

I did not expect that Github Metadata error to appear.

Additional information

When I removed the Gemfile, the error went away. Since this is the only gem outside of Jekyll that I'm using in my project, I suspect the error has something to do with github-pages. That's why I'm filing an issue here.

I fixed the issue by following the resolution described here. This removed the error from occurring.

I just wanted to report this error in case there's something with the github-pages gem that is causing it.

[parkr]

Hey @tomjohnson1492! This is expected. The jekyll-github-metadata gem is automatically enabled for GitHub Pages builds (including builds using this gem locally). It pulls in information from the GitHub API, but first checks the environment for authentication, which is required for some API calls to return the data we want. It's a warning, not an error, so you should be good to ignore them locally. 👍

[SeanKilleen]

@parkr I think the issue here is that it appears to break Jekyll's watch functionality.

In the scenario described here, which I'm also hitting, I have the following:

Repro

• Setup the gemfile as described above
• run bundle exec jekyll serve (which watches for changes and regenerates each time)
• make a change to a file and save
• See the "warning" errors

Expected behavior

The files are still generated on each change and we can ignore the errors.

Actual behavior

The jekyll pipeline is broken. The file changes are not actually processed, because jekyll perceives an error to have happened during generation.

In addition to the warning message, I see the following errors:

Error: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed
             Error: Run jekyll build --trace for more information.

Instead, we are required to force-quit jekyll and run bundle exec jekyll serve each time.

Does this help clarify the issue? If so, it would be awesome to open this up for a second look.

It's also possible that this may be a separate issue entirely; if so, I'm happy to create a new ticket.

Update: A workaround (sort of?)

The workaround described here and referenced above requires two environment variables, a cacert file download, and seemingly a restart of the PC.

I'll try this as a workaround and note it in my README if it works.

Alternatively, is there a way we can disable this gem or functionality locally? I apologize for jumping in with a lack of familiarity on the structure of the project (a project which I appreciate on a daily basis, btw -- thank you!)

[coin8086]

I have the same problem with the new version of github-pages (136) on jekyll (= 3.4.3). It breaks the common dev flow locally, that is the convenient edit-and-refresh way. So I hope it will be fixed soon.

[asnowfix]

The work-around described above does not work for me. I am using a GitHub Enterprise instance & tried using a personal access token generated by GHE & a one generated by GH.com. None worked & I am still getting the error message at each refresh:

      Regenerating: 1 file(s) changed at 2017-05-16 12:27:51 ...error:
             Error: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed
             Error: Run jekyll build --trace for more information.

Despite the hint above, $ jekyll build --trace --watch does not give anything more useful:

      Regenerating: 1 file(s) changed at 2017-05-16 12:25:13 ...error:
             Error: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed
             Error: Run jekyll build --trace for more information.

[asnowfix]

Fixed my issue (not saying it is yours) by adding...

github: [metadata]

...to _config.yml

[whizzzkid]

fix by @asnowfix works :) thanks 👍

[abhishekp1996]

A ton thanks to @asnowfix
The fix works very well.

I need to point out, add the code as it is. [metadata] will be automatically pulled by the generator.

[fgreve]

Thanks to @asnowfix

[super456]

@asnowfix
I'm very grateful to you ！:smile:

[john20xdoe]

as per @asnowfix fix, this results in a missing site.title (blank values?). but other wise the site was being served locally successfully.

[wrschneider]

thanks @asnowfix, this was driving me crazy.

[karamfd]

@asnowfix Your solution is working perfectly for me as well. Thank you very much 😃

[troccoli]

Thank you @asnowfix . Worked for me too.

[seanlerner]

@asnowfix solution didn't work for me.

I ended up generating a token and putting it in my env:

Generate token: https://github.com/settings/tokens

Run:

JEKYLL_GITHUB_TOKEN=<your token> jekyll serve

Or you can add to your shell config file:

#  .zshrc, .bashrc or .bash_profile

export JEKYLL_GITHUB_TOKEN=<your token>

Then in terminal:

source ~/.zshrc