Skip to content
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

Can't download a remote theme behind a corporate proxy #81

Open
philippart-s opened this issue Jun 19, 2020 · 4 comments
Open

Can't download a remote theme behind a corporate proxy #81

philippart-s opened this issue Jun 19, 2020 · 4 comments

Comments

@philippart-s
Copy link

Describe the bug

When I'm behind a corporate proxy the remote theme downloading is on error.

Steps to reproduce the behavior

  1. Set http_proxy and https_proxy
  2. Launch bundle exec jekyll serve behind a corporate proxy
  3. See error

Expected behavior

If a set a corporate proxy the remote theme is downloaded.

Screenshots

N/A

Additional context

The logs:

bundle exec jekyll serve --verbose
  Logging at level: debug
Configuration file: xxxxx/_config.yml
  Logging at level: debug
      GitHub Pages: github-pages v202
      GitHub Pages: jekyll v3.8.5
             Theme: jekyll-theme-primer
      Theme source: C:/softs/Ruby26-x64/lib/ruby/gems/2.6.0/gems/jekyll-theme-primer-0.5.3
         Requiring: jekyll-github-metadata
Dotenv not found. Skipping
         Requiring: jekyll-seo-tag
         Requiring: jekyll-feed
         Requiring: jekyll-paginate
         Requiring: jekyll-sitemap
         Requiring: jekyll-coffeescript
         Requiring: jekyll-commonmark-ghpages
         Requiring: jekyll-gist
         Requiring: jekyll-github-metadata
         Requiring: jekyll-relative-links
         Requiring: jekyll-optional-front-matter
         Requiring: jekyll-readme-index
         Requiring: jekyll-default-layout
         Requiring: jekyll-titles-from-headings
         Requiring: jekyll-remote-theme
   GitHub Metadata: Initializing...
            Source: xxxxx
       Destination: xxxxx/_site
 Incremental build: disabled. Enable with --incremental
      Generating...
             Theme: blackrockdigital/startbootstrap-clean-blog-jekyll
      Theme source: C:/Users/xxx/AppData/Local/Temp/jekyll-remote-theme-20200619-9532-xv058
Invalid theme folder: _sass
      Remote Theme: Using theme blackrockdigital/startbootstrap-clean-blog-jekyll
      Remote Theme: Downloading https://codeload.github.com/blackrockdigital/startbootstrap-clean-blog-jekyll/zip/master to C:/Users/xxx~1/AppData/Local/Temp/jekyll-remote-theme-20200619-9532-48beoi.zip
jekyll 3.8.5 | Error:  Failed to open TCP connection to codeload.github.com:443 (Une tentative de connexion a ÚchouÚ car le parti connectÚ nÆa pas rÚpondu convenablement au-delÓ dÆune certaine durÚe ou une connexion Útablie a ÚchouÚ car lÆh¶te de connexion nÆa pas rÚpondu. - connect(2) for "codeload.github.com" port 443)
@philippart-s
Copy link
Author

philippart-s commented Jul 2, 2020

I have still the problem but I think I find the cause, I think that the proxy is used without the credentials information.

I set the proxy configuration as following: $ export http_proxy=http://user:pass@proxy:8080 and the error is:

Remote Theme: Using theme blackrockdigital/startbootstrap-clean-blog-jekyll
jekyll 3.8.5 | Error:  407 "authenticationrequired"

The Net documentation is clear:

Net::HTTP will automatically create a proxy from the http_proxy environment variable if it is present.
See ::new for further details and examples such as proxies that require a username and password.
If the proxy requires authentication you must supply it by hand.

Source: https://ruby-doc.org/stdlib-2.4.2/libdoc/net/http/rdoc/Net/HTTP.html#method-c-new

I'm not a ruby developper but I think that to be compatible with authenticated proxies the following code must handle external proxy autothentification ?

Net::HTTP.start(zip_url.host, zip_url.port, :use_ssl => true) do |http|

Class : Net::HTTP - Ruby 2.4.2

@stale
Copy link

stale bot commented Aug 31, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Aug 31, 2020
@stale stale bot closed this as completed Sep 7, 2020
@philippart-s
Copy link
Author

philippart-s commented Sep 15, 2020

any chance that a fix to use http_proxy will be planed ?

@philippart-s
Copy link
Author

is this repo is still alive ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants