[NPMCLI-207] jumpstart STILL fails when behind proxy Created: 11/Feb/19  Updated: 21/Feb/19  Resolved: 11/Feb/19

Status: Closed
Project: Magnolia CLI
Component/s: None
Affects Version/s: 3.0.5
Fix Version/s: 3.0.6

Type: Bug Priority: Critical
Reporter: Christopher Zimmermann Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

node v9.9.0


Issue Links:
Cloners
clones NPMCLI-176 mgnl jumpstart fails when behind proxy Closed
Relates
relates to NPMCLI-206 mgnl jumpstart not working behind proxy Closed
documentation
to be documented by NPMCLI-208 DOC: Document the release of CLI 3.0.6 Closed
supersession
supersedes NPMCLI-199 mgnl jumpstart fails Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Release notes required:
Yes
Epic Link: Starting is easy
Sprint: Foundation 4
Story Points: 2

 Description   

 

Input from jfrantzius on NPMCLI-176.

I just tried with mgnl: 3.0.5 node: v10.15.0 os: darwin and a local cntlm proxy configured in ~/.npmrc:

https-proxy = "http://localhost:3126/"

proxy = "http://localhost:3126/"

Unfortunately, it seems that the proxy is not properly picked up (it does where everywhere else):

 

? What Magnolia would you like to install? magnolia-community-demo-webapp info No magnolia-version option provided. Will use the latest stable version. info No path option provided. Will use the default light-modules in the current directory ERR! Request failed with status code 501 ERR! Error: Request failed with status code 501 ERR!     at createError (/Users/joerg.frantzius/.nvm/versions/node/v10.15.0/lib/node_modules/@magnolia/cli/node_modules/axios-proxy-fix/lib/core/createError.js:16:15) ERR!     at settle (/Users/joerg.frantzius/.nvm/versions/node/v10.15.0/lib/node_modules/@magnolia/cli/node_modules/axios-proxy-fix/lib/core/settle.js:18:12) ERR!     at IncomingMessage.handleStreamEnd (/Users/joerg.frantzius/.nvm/versions/node/v10.15.0/lib/node_modules/@magnolia/cli/node_modules/axios-proxy-fix/lib/adapters/http.js:194:11) ERR!     at IncomingMessage.emit (events.js:187:15) ERR!     at endReadableNT (_stream_readable.js:1094:12) ERR!     at process._tickCallback (internal/process/next_tick.js:63:19)

Reported by Tomas

mgnl jumpstart -m 5.7info Using configuration at /usr/lib/node_modules/@magnolia/cli/lib/config/mgnl-cli.jsoninfo Using prototypes at /usr/lib/node_modules/@magnolia/cli/lib/config/mgnl-cli-prototypes? 
What Magnolia would you like to install? magnolia-community-demo-webappinfo No path option provided. 
Will use the default light-modules in the current directoryinfo /home....ight-modules does not seem to exist. Path will be created automatically.

ERR! Request failed with status code 400ERR! Error: Request failed with status code 400ERR!     at createError (/usr/lib/node_modules/@magnolia/cli/node_modules/axios-proxy-fix/lib/core/createError.js:16:15)ERR!     
at settle (/usr/lib/node_modules/@magnolia/cli/node_modules/axios-proxy-fix/lib/core/settle.js:18:12)ERR!     
at IncomingMessage.handleStreamEnd (/usr/lib/node_modules/@magnolia/cli/node_modules/axios-proxy-fix/lib/adapters/http.js:194:11)ERR!     
at IncomingMessage.emit (events.js:187:15)ERR!     
at endReadableNT (_stream_readable.js:1094:12)ERR!     
at process._tickCallback (internal/process/next_tick.js:63:19
)ERR!ERR!ERR! 

mgnl: 3.0.5 node: v10.15.0 os: linux
ERR! please open an issue including this log on https://jira.magnolia-cms.com/browse/NPMCLI






 Comments   
Comment by Christopher Zimmermann [ 11/Feb/19 ]

jfrantzius This fix and the new version of the CLI 3.0.6 should fix your proxy issue. It would be great if you can try it and let us know.

Generated at Mon Feb 12 04:47:34 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.