Skip to content

[BUG] Documentation cannot be build behind https proxy #2044

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
schmitts opened this issue Oct 26, 2020 · 2 comments
Closed

[BUG] Documentation cannot be build behind https proxy #2044

schmitts opened this issue Oct 26, 2020 · 2 comments
Labels
Bug thing that needs fixing Release 6.x work is associated with a specific npm 6 release

Comments

@schmitts
Copy link

Current Behavior:

The documentation build during the installation of npm fails when an https proxy is used:

"gatsby-plugin-prefetch-google-fonts" threw an error while running the onPreBootstrap lifecycle:

write EPROTO 140379905034048:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../ssl/record/ssl3_record.c:331:

Expected Behavior:

Installation does not fail.

Steps To Reproduce:

wget https://registry.npmjs.org/npm/-/npm-6.14.8.tgz
tar xfz npm-6.14.8.tgz
cd package
# set some https proxy, eg. export https_proxy=http://167.86.120.160:8080
./configure
make

Environment:

  • OS: Ubuntu 20.04
  • npm: 6.14.8
@schmitts schmitts added Bug thing that needs fixing Needs Triage needs review for next steps Release 6.x work is associated with a specific npm 6 release labels Oct 26, 2020
@darcyclarke darcyclarke removed the Needs Triage needs review for next steps label Feb 13, 2021
@darcyclarke
Copy link
Contributor

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.

1 similar comment
@darcyclarke
Copy link
Contributor

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Bug thing that needs fixing Release 6.x work is associated with a specific npm 6 release
Projects
None yet
Development

No branches or pull requests

2 participants