support http proxy when using `nuxi init` with node >= 18 #159

ikexing-cn · 2022-10-05T05:23:31Z

Environment

Operating System: Darwin
Node Version: v16.17.0
Nuxt Version: 0.0.0
Nitro Version: -
Package Manager: unknown
Builder: webpack
User Config: -
Runtime Modules: -
Build Modules: -

Reproduction

Not exist

Describe the bug

 ERROR  Failed to download template from registry: request to https://raw.githubusercontent.com/nuxt/starter/templates/templates/v3.json failed, reason: connect ECON3

  at /Users/xdclass/.npm/_npx/a95e0f536cf9a537/node_modules/nuxi/dist/chunks/init.mjs:13269:11
  at processTicksAndRejections (node:internal/process/task_queues:96:5)
  at async downloadTemplate (/Users/xdclass/.npm/_npx/a95e0f536cf9a537/node_modules/nuxi/dist/chunks/init.mjs:13268:20)
  at async Object.invoke (/Users/xdclass/.npm/_npx/a95e0f536cf9a537/node_modules/nuxi/dist/chunks/init.mjs:13336:15)
  at async _main (/Users/xdclass/.npm/_npx/a95e0f536cf9a537/node_modules/nuxi/dist/cli.mjs:50:20)

Additional context

curl https://raw.githubusercontent.com/nuxt/starter/templates/templates/v3.json

{
  "name": "v3",
  "defaultDir": "nuxt-app",
  "url": "https://v3.nuxtjs.org",
  "tar": "https://codeload.github.com/nuxt/starter/tar.gz/refs/heads/v3"
}

Everything works fine when I request the URL directly, I think this might be a bug in nuxt.

Logs

No response

The text was updated successfully, but these errors were encountered:

danielroe · 2022-10-05T06:02:39Z

What happens when you run:

node -e "require('https').get('https://raw.githubusercontent.com/nuxt/starter/templates/templates/v3.json')"

ikexing-cn · 2022-10-05T06:05:41Z

node -e "require('https').get('https://raw.githubusercontent.com/nuxt/starter/templates/templates/v3.json')"

node:events:491
      throw er; // Unhandled 'error' event
      ^

Error: connect ECONNREFUSED 0.0.0.0:443
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1247:16)
Emitted 'error' event on ClientRequest instance at:
    at TLSSocket.socketErrorListener (node:_http_client:481:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  errno: -61,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '0.0.0.0',
  port: 443
}

It looks like the same error is reported...

danielroe · 2022-10-05T06:56:01Z

It seems there is something stopping your node from connecting. Maybe an application firewall?

ikexing-cn · 2022-10-05T07:14:38Z

That's strange, my application firewall is always off...... any other possible reasons?

danielroe · 2022-10-05T07:25:04Z

Are you using a proxy?

Would you run:

env | grep -i proxy
npm config list | grep -i proxy

ikexing-cn · 2022-10-05T07:30:19Z

Yes, I using proxy on clash.

env | grep -i proxy

all_proxy=sock5://127.0.0.1:8889
http_proxy=http://127.0.0.1:8889
https_proxy=http://127.0.0.1:8889
ALL_PROXY=sock5://127.0.0.1:8889

And then npm config list | grep -i proxy has not output.

danielroe · 2022-10-05T07:33:01Z

So the issue is that HTTPS is not working over your HTTP proxy: lovell/sharp#679.

We will need to implement a similar fix.

so1ve · 2022-10-06T02:13:21Z

In fact, it is difficult to access Github and Raw in China, and we often use proxies. However, nuxi seems to be the same as degit, the default tar mode does not use the set proxy.

codingcn · 2022-11-03T02:08:57Z

In china, I succeeded

Just set DNS 114.114.114.114

yonhung · 2022-11-03T05:46:14Z

I got the same error.
It worked for me after I added raw.githubusercontent.com Ip address to my Windows hosts file.
It seems a firewall dns cache pollution problem.

so1ve · 2022-11-03T07:36:34Z

Does degit use https_proxy and https_proxy?

pi0 · 2022-11-03T14:40:58Z

Created issue for giget (used by nuxi cli). PR welcome.

unjs/giget#23

pi0 · 2022-11-18T12:23:05Z

Landed by unjs/giget#24

codername-123 · 2023-01-02T14:23:40Z

I'm still having this issue on my windows machine

danielroe · 2023-01-04T14:31:06Z

@codername-123 Would you try using npx nuxi@latest in case your npm is caching an old version?

codername-123 · 2023-01-06T08:22:20Z

My bad @danielroe it was a problem with my ISP... As soon as I changed my ISP it started working properly

danielroe · 2023-01-06T11:22:29Z

Glad everything is resolved 😊

GeorgeHcc · 2023-01-13T08:31:39Z

in china ,I'm failed

CharryMoon · 2023-03-06T06:44:04Z

get ip of raw.githubusercontent.com from a web.
and set these into hosts file (windows: C:\Windows\System32\drivers\etc)
185.199.111.133 raw.githubusercontent.com
rerun 'npx nuxi init nut3-app', and it works

pi0 · 2023-03-06T10:13:35Z

Reopening to investigate more.

CNMathon · 2023-10-06T05:56:19Z

@danielroe So, has it really been solved? I still have this problem, and this issue has been open for more than one year.

pi0 · 2023-10-06T08:44:19Z

The main issue is native fetch API provided by newer Node.js versions (18+), does not support HTTP agents for proxy support. I am looking for a solution for this. (older issue reports are however unrelavant. this issue contains multiple reports for different causes)

sumasagrp · 2023-10-17T15:56:14Z

when i do a curl to https://raw.githubusercontent.com/nuxt/starter/templates/templates/v3.json it works

however when i do

node -e "require('https').get('https://raw.githubusercontent.com/nuxt/starter/templates/templates/v3.json')"

it does not work

AggregateError at internalConnectMultiple (node:net:1114:18) at internalConnectMultiple (node:net:1177:5) at Timeout.internalConnectMultipleTimeout (node:net:1687:3) at listOnTimeout (node:internal/timers:575:11) at process.processTimers (node:internal/timers:514:7) Emitted 'error' event on ClientRequest instance at: at TLSSocket.socketErrorListener (node:_http_client:495:9) at TLSSocket.emit (node:events:514:28) at emitErrorNT (node:internal/streams/destroy:151:8) at emitErrorCloseNT (node:internal/streams/destroy:116:3) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) { code: 'ETIMEDOUT', [errors]: [ Error: connect ETIMEDOUT 185.199.109.133:443 at createConnectionError (node:net:1634:14) at Timeout.internalConnectMultipleTimeout (node:net:1685:38) at listOnTimeout (node:internal/timers:575:11) at process.processTimers (node:internal/timers:514:7) { errno: -110, code: 'ETIMEDOUT', syscall: 'connect', address: '185.199.109.133', port: 443 }, Error: connect ENETUNREACH 2606:50c0:8003::154:443 - Local (:::0) at internalConnectMultiple (node:net:1176:40) at Timeout.internalConnectMultipleTimeout (node:net:1687:3) at listOnTimeout (node:internal/timers:575:11) at process.processTimers (node:internal/timers:514:7) { errno: -101, code: 'ENETUNREACH', syscall: 'connect', address: '2606:50c0:8003::154', port: 443 }, Error: connect ETIMEDOUT 185.199.108.133:443 at createConnectionError (node:net:1634:14) at Timeout.internalConnectMultipleTimeout (node:net:1685:38) at listOnTimeout (node:internal/timers:575:11) at process.processTimers (node:internal/timers:514:7) { errno: -110, code: 'ETIMEDOUT', syscall: 'connect', address: '185.199.108.133', port: 443 }, Error: connect ENETUNREACH 2606:50c0:8002::154:443 - Local (:::0) at internalConnectMultiple (node:net:1176:40) at Timeout.internalConnectMultipleTimeout (node:net:1687:3) at listOnTimeout (node:internal/timers:575:11) at process.processTimers (node:internal/timers:514:7) { errno: -101, code: 'ENETUNREACH', syscall: 'connect', address: '2606:50c0:8002::154', port: 443 }, Error: connect ETIMEDOUT 185.199.110.133:443 at createConnectionError (node:net:1634:14) at Timeout.internalConnectMultipleTimeout (node:net:1685:38) at listOnTimeout (node:internal/timers:575:11) at process.processTimers (node:internal/timers:514:7) { errno: -110, code: 'ETIMEDOUT', syscall: 'connect', address: '185.199.110.133', port: 443 }, Error: connect ENETUNREACH 2606:50c0:8001::154:443 - Local (:::0) at internalConnectMultiple (node:net:1176:40) at Timeout.internalConnectMultipleTimeout (node:net:1687:3) at listOnTimeout (node:internal/timers:575:11) at process.processTimers (node:internal/timers:514:7) { errno: -101, code: 'ENETUNREACH', syscall: 'connect', address: '2606:50c0:8001::154', port: 443 }, Error: connect ETIMEDOUT 185.199.111.133:443 at createConnectionError (node:net:1634:14) at Timeout.internalConnectMultipleTimeout (node:net:1685:38) at listOnTimeout (node:internal/timers:575:11) at process.processTimers (node:internal/timers:514:7) { errno: -110, code: 'ETIMEDOUT', syscall: 'connect', address: '185.199.111.133', port: 443 }, Error: connect ENETUNREACH 2606:50c0:8000::154:443 - Local (:::0) at internalConnectMultiple (node:net:1176:40) at Timeout.internalConnectMultipleTimeout (node:net:1687:3) at listOnTimeout (node:internal/timers:575:11) at process.processTimers (node:internal/timers:514:7) { errno: -101, code: 'ENETUNREACH', syscall: 'connect', address: '2606:50c0:8000::154', port: 443 } ] }

Seems

Node.js does not use HTTP_PROXY environment variables. See this discussion nodejs/node#8381.

To set a global Node.js proxy use https://github.com/gajus/global-agent.

I think this is the culprit

Possible work around ?? nodejs/undici#1650 (comment)
I can't belive there is no proxy support in 2023 .... working in corporate environment becomes a nightmare

pi0 · 2023-10-17T21:06:54Z

Fully agree with you @sumasagrp sadly this is a limitation with Node/undici that lacks built-in HTTP_PROXY support whereas it is a well-known standard... (also little bit of corporate firewalls that consider "github" as possible harmful resource and block it most of the times)

Sorry for delay on this. this is still on my todo list to find best workaround. Possibly (also) in lowset level (ofetch) to make proxy support for most of our ecosystem out of the box.

subinznz · 2023-10-17T23:08:53Z

Bun seems to have support for http_proxy. thanks for all your hard work

liamwang · 2023-11-17T13:07:36Z

@codingcn Thanks. 114's DNS works for me.

BTW, Aliyun's DNS doesn't work, don't try.

lzb-libra · 2023-12-07T07:21:46Z

I have the same issue. Besides the usual settings like changing DNS, modifying the hosts file, and using VPN, I've tried everything, but it still doesn't work.

caodaiquang · 2023-12-08T04:44:34Z

I have same issue :(

lzb-libra · 2023-12-14T02:14:57Z

I have same issue :(

The best way is actually to give up using it altogether, why hang oneself on one tree? I've already given up.

pi0 · 2023-12-14T13:06:04Z

Hi all again and sorry for delay on it. I understand for those behind a firewall, it must be a really hard experience and for that, I apologize (I guess on behalf of the lazy Node.js team too haha) it is not supported yet 🙏🏼

I will try to jump at at as soon as possible.

so1ve · 2023-12-14T13:11:01Z

As a Chinese user, I know the seriousness of this bug, but I don't think it is the right behavior to express one's negative emotions in issues. At the same time, Nuxt is an open source project. Thanks to the Nuxt team for their hard work over the past few years.

hzgotb · 2023-12-20T10:34:47Z

有梯子的方案：

Powershell:

# 请根据实际情况设置梯子地址
$env:all_proxy="ip:port"
$env:FORCE_NODE_FETCH=1
# 最后执行初始化，请根据实际情况执行
pnpm dlx nuxi@latest init my-app

Bash

# 同上，请根据实际情况设置梯子地址和初始化命令
export all_proxy="ip:port" && export FORCE_NODE_FETCH=1 && pnpm dlx nuxi@latest init my-app

心路历程：

翻了翻相关的仓库，在 unjs/giget#120 中看到了解决方法

然后捋了一下整个链路
nuxi.init -> giget.downloadTemplate -> giget.download -> giget.sendFetch -> node-fetch-native.fetch

没有细看 node-fetch-native 的代码，只是稍微看了一下文档，应该是逐渐使用node原生实现的fetch来替代之前的node-fetch方案，并且对不支持原生fetch的旧node版本进行了Polyfill （猜的）。所以在有梯子的情况下还是不生效（貌似原生fetch不接受代理）。
而之前的node-fetch会通过梯子的，那么如上引用的issue所言，通过FORCE_NODE_FETCH来切换到可以用梯子的fetch去下载模板

没梯子的方案：
cli的init.ts代码是这样的

template = await downloadTemplate(templateName, {
        dir: ctx.args.dir,
        cwd,
        force: Boolean(ctx.args.force),
        offline: Boolean(ctx.args.offline),
        preferOffline: Boolean(ctx.args.preferOffline),
        registry: process.env.NUXI_INIT_REGISTRY || DEFAULT_REGISTRY,
      })

可以通过设置环境变量来更改模板地址
Powershell

$env:NUXI_INIT_REGISTRY="https://gitee.com/hzgotb/nuxt-starter/raw/templates/templates"
pnpm dlx nuxi@latest init my-app

pi0 · 2023-12-24T20:43:11Z

Hi. HTTP proxy support for Node.js versions with native fetch added to the latest build of nuxi CLI (read more)

If you want to early test, you can try with nuxi-nightly channel:

http_proxy=http://localhost:9080 npx nuxi-nightly@latest init nuxt-app

(port 9080 is for Tor, you can replace it with your own!)

chunten · 2024-02-02T01:58:30Z

我有同样的问题。除了更改DNS、修改hosts文件、使用VPN等常用设置外，我已经尝试了一切，但仍然不起作用。

me too

pi0 · 2024-02-14T18:28:38Z

With latest nuxi, http proxy should be supported out of the box!

ricky52529 · 2024-03-27T09:35:46Z

get ip of raw.githubusercontent.com from a web. and set these into hosts file (windows: C:\Windows\System32\drivers\etc) 185.199.111.133 raw.githubusercontent.com rerun 'npx nuxi init nut3-app', and it works

it works~ thank you~

Milchreis · 2024-05-27T06:40:34Z

Hi,

the nightly-build works for init. Thank you for the hint, but on module add I got the same issue. Could you add the proxy-support for module, too?

pi0 · 2024-05-27T08:38:24Z

@Milchreis ~> #419 (this will add proxy support to all internal fetches happening with nuxi CLI)

(however package managers should still also respect and support http_proxy)

ClungTsang · 2024-07-10T02:29:44Z

In china, I succeeded

Just set DNS 114.114.114.114

it did work ,appreciate

Hetari · 2024-10-10T13:17:46Z

Guide: Resolving nuxi init Error: "Failed to download template from registry" on Linux

Steps to Resolve:

Find the IP Address for raw.githubusercontent.com:
- Go to IP Address Lookup.
- Search for raw.githubusercontent.com.
- Take note of the current IP address. As of this writing, it could be 185.199.108.133, but you should verify this for the most up-to-date address.
Edit the /etc/hosts File:
- Open your terminal.
- Use the following command to open the /etc/hosts file in a text editor with root privileges:
```
sudo nano /etc/hosts
```
- Add a new entry for raw.githubusercontent.com with the IP address you found. Example:
```
185.199.108.133 raw.githubusercontent.com
```
- Save the file and exit the editor (Ctrl + O to save, Ctrl + X to exit).
Test the Fix:
- Try running the nuxi init command again:
```
npx nuxi@latest init my-app
```
- It should now successfully download the required template.

danielroe added bug Something isn't working and removed bug Something isn't working labels Oct 5, 2022 — with Volta.net

danielroe changed the title ~~Error when I using npx nuxi init nuxt-app.~~ support http proxy when using nuxi init Oct 17, 2022

danielroe mentioned this issue Oct 17, 2022

can't start a new project via npx nuxi init nuxt-app nuxt/nuxt#14991

Closed

pi0 mentioned this issue Nov 3, 2022

Support http proxy unjs/giget#23

Closed

danielroe added the good first issue Good for newcomers label Nov 3, 2022 — with Volta.net

pi0 closed this as completed Nov 18, 2022

danielroe mentioned this issue Jan 4, 2023

Run Npx nuxt/nuxi init Error. can't init the nuxt3 project. nuxt/starter#199

Closed

danielroe transferred this issue from nuxt/framework Jan 19, 2023

danielroe mentioned this issue Oct 13, 2023

create nuxt3 template fail nuxt/nuxt#23657

Closed

danielroe mentioned this issue Oct 20, 2023

command error nuxt/nuxt#23816

Closed

iusx mentioned this issue Nov 23, 2023

nuxi init fails with Failed to download template from registry: fetch failed #288

Open

yuexiaqingmiao mentioned this issue Dec 6, 2023

Nuxt project creation failed. nuxt/nuxt#24618

Closed

pi0 added a commit that referenced this issue Dec 24, 2023

chore: update giget to 1.2 and lockfile (#159)

6c8cef6

pi0 changed the title ~~support http proxy when using nuxi init~~ support http proxy when using nuxi init with node >= 18 Dec 24, 2023

pi0 removed the good first issue Good for newcomers label Dec 24, 2023

pi0 closed this as completed Feb 14, 2024

pi0 mentioned this issue May 27, 2024

Support HTTP proxy for all commands #419

Open

Summpot mentioned this issue Nov 28, 2024

[Bug]: Failed to fetch styles from registry unovue/shadcn-vue#467

Closed

2 tasks

support http proxy when using nuxi init with node >= 18 #159

support http proxy when using nuxi init with node >= 18 #159

Comments

ikexing-cn commented Oct 5, 2022 • edited Loading

Environment

Reproduction

Describe the bug

Additional context

Logs

danielroe commented Oct 5, 2022

ikexing-cn commented Oct 5, 2022

danielroe commented Oct 5, 2022

ikexing-cn commented Oct 5, 2022

danielroe commented Oct 5, 2022

ikexing-cn commented Oct 5, 2022 • edited Loading

danielroe commented Oct 5, 2022

so1ve commented Oct 6, 2022

codingcn commented Nov 3, 2022

yonhung commented Nov 3, 2022

so1ve commented Nov 3, 2022

pi0 commented Nov 3, 2022

pi0 commented Nov 18, 2022

codername-123 commented Jan 2, 2023

danielroe commented Jan 4, 2023

codername-123 commented Jan 6, 2023

danielroe commented Jan 6, 2023

GeorgeHcc commented Jan 13, 2023

CharryMoon commented Mar 6, 2023

pi0 commented Mar 6, 2023

CNMathon commented Oct 6, 2023

pi0 commented Oct 6, 2023 • edited Loading

sumasagrp commented Oct 17, 2023 • edited Loading

pi0 commented Oct 17, 2023 • edited Loading

subinznz commented Oct 17, 2023 • edited Loading

liamwang commented Nov 17, 2023

lzb-libra commented Dec 7, 2023

caodaiquang commented Dec 8, 2023

lzb-libra commented Dec 14, 2023

pi0 commented Dec 14, 2023 • edited Loading

so1ve commented Dec 14, 2023

hzgotb commented Dec 20, 2023 • edited Loading

pi0 commented Dec 24, 2023

chunten commented Feb 2, 2024

pi0 commented Feb 14, 2024

ricky52529 commented Mar 27, 2024

Milchreis commented May 27, 2024

pi0 commented May 27, 2024

ClungTsang commented Jul 10, 2024

Hetari commented Oct 10, 2024 • edited Loading

Guide: Resolving nuxi init Error: "Failed to download template from registry" on Linux

Steps to Resolve:

support http proxy when using `nuxi init` with node >= 18 #159

support http proxy when using `nuxi init` with node >= 18 #159

ikexing-cn commented Oct 5, 2022 •

edited

Loading

ikexing-cn commented Oct 5, 2022 •

edited

Loading

pi0 commented Oct 6, 2023 •

edited

Loading

sumasagrp commented Oct 17, 2023 •

edited

Loading

pi0 commented Oct 17, 2023 •

edited

Loading

subinznz commented Oct 17, 2023 •

edited

Loading

pi0 commented Dec 14, 2023 •

edited

Loading

hzgotb commented Dec 20, 2023 •

edited

Loading

Hetari commented Oct 10, 2024 •

edited

Loading