[NPMCLI-142] ETIMEOUT 109.71.96.19:443 when behind a proxy Created: 20/Sep/17 Updated: 28/Aug/18 Resolved: 28/Aug/18 |
|
| Status: | Closed |
| Project: | Magnolia CLI |
| Component/s: | None |
| Affects Version/s: | 2.1.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Daniel O'Brien | Assignee: | Unassigned |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | support | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 7 |
||
| 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
|
| Date of First Response: |
| Description |
|
I have successfully installed using: npm install @magnolia/cli -g When using mgnl jumpstart, the following timeout occurs when trying to get "temp-magnolia.zip.download" ERR! connect ETIMEDOUT 109.71.96.19:443 |
| Comments |
| Comment by Federico Grilli [ 20/Sep/17 ] |
|
Hello Daniel, that sounds more like a temporary issue with Magnolia's Nexus repository https://nexus.magnolia-cms.com. Could you try again, please? Federico |
| Comment by Daniel O'Brien [ 21/Sep/17 ] |
|
Hi Federico Unfortunately I get the same issue this morning. I should point out I am behind a corporate proxy, however I have used npm a lot successfully with no issues with http or https. Any ideas? Thanks for you help in advance. |
| Comment by Federico Grilli [ 21/Sep/17 ] |
|
Hi Daniel, I would blame the corporate proxy then because I can't reproduce it locally (tested with several Windows machines). HTH, Federico |
| Comment by Federico Grilli [ 21/Sep/17 ] |
|
However after reading the link below I guess we may add a couple of parameters to mgnl jumpstart to specify the proxy. It's not up to me to decide this but I guess this improvement will have low priority anyway. |
| Comment by Daniel O'Brien [ 22/Sep/17 ] |
|
Hi Federico Thanks for your help. I've managed to resolve this and thought I'd share how, as this could help other users behind a corporate proxy. It would appear using "npm config set proxy" and "npm config set https-proxy" wasn't enough in my case. I also had to set some system environmental variables for "http_proxy" and "https_proxy" on my Windows machine. I am now using mgnl jumpstart successfully thanks. Also, just a thought for development ... A lot of us slower moving corporate Magnolia users have webapps which are still using stk templates, alongside our light-modules. I must confess to changing line 61 in npm\node_modules@magnolia\cli\lib\jumpstart.js to try this, and it works very nicely. Line 61: url += '&a=magnolia-enterprise-pro-stk-bundle&c=tomcat-bundle&e=zip&v=${magnoliaVersion}' To add this as a feature, would be a nice touch. Many thanks again for your quick response. First class as always |
| Comment by Federico Grilli [ 25/Sep/17 ] |
|
Hello Daniel, thanks a lot for sharing your findings! That is going to be mentioned in CLI documentation for sure Hope this helps, Federico |
| Comment by Christopher Zimmermann [ 28/Aug/18 ] |
|
dobrien Your requested feature is now available in version 3 of the CLI - please seeĀ https://documentation.magnolia-cms.com/display/DOCS57/Magnolia+CLI+v3#MagnoliaCLIv3-jumpstart for details. Specifically, check out the -w option. |
| Comment by Christopher Zimmermann [ 28/Aug/18 ] |
|
We will update the documentation to include a note about this error and proxies. |
| Comment by Christopher Zimmermann [ 28/Aug/18 ] |
|
NPM proxy must be correctly configured in order to run jumpstart. |