on a fresh “hello” project I get: Error occurred while proxying request localhost:8080/api/v2/status to http://localhost:8000/ [ECONNREFUSED] on the webpack server in a development environment. The canisters run fine on the replica and if I go directly to the replica i.e “localhost:8000/api/v2/sta…

Hello Forum - FYI, I also posted this in the Dfinity Discord and @anon74414410 (Kyle) from the Dfinity team said that this behavior was most likely from a newer version of node.js. So, I had 17.2 active and he said the SDK supports 12, 14, and 16 … I unlinked 17, installed 16 and linked it … for…

I really hope this bug doesn’t make it into a stable node.js release so that I don’t have the excuse anymore :grimacing:

Recently ran into this same bug with NodeJS version v18.1.0. Reverting to 16.xx.xx (stable) fixed it. I’m a huge fan of nvm (also installable via brew) for switching between node versions.

I’m not sure I followed this thread correctly, but maybe the problem can be explained by this: [image] Development workflow: quickly test code modifications Developers Note to self for the future: bind to 127.0.0.1:8000 instead of localhost:8000 since binding to localhos…

@anon74414410 This bug is now in a stable NodeJS release (18.12.1) As previously mentioned, this issue occurs when using Node 18, but is fixed (does not occur) when using Node 16. Is specific bug (in the post) with webpack, webpack plugins, or something else entirely? It would be nice to be able …

Yes, node 18 is fully supported, and Paul is correct. Replace localhost with 127.0.0.1 in your webpack config and you should be good to go

I’m just now running into this issue with my app after adding a local ledger canister. I’ve replaced the localhost with 127.0.0.1 in my webpack config as well as binding that address as described in the thread linked by @paulyoung but I am unable to make calls or queries from my frontend canister to…

The default port recently switched to 4943. Can you try localhost:4943/api/v2/status? On my machine, this works

This worked, thank you so much!

I get similar error too. [webpack-dev-server] [HPM] Error occurred while proxying request localhost:8081/api/v2/status to http://127.0.0.1:4943/api/v2/status? [ECONNREFUSED] (https://nodejs.org/api/errors.html#errors_common_system_errors) I even get something similar when i try to test http outcal…

Webpack Proxy - ECONNREFUSED for proxy to api

Developers

paulyoung August 23, 2022, 2:09am 5

I’m not sure I followed this thread correctly, but maybe the problem can be explained by this:

Topic		Replies	Views
ConnectionRefused on localhost! Frontend unable to connect to my backend Programs & Applications	4	12335	March 1, 2022
Node fetch to replica connection refused Developers	2	472	January 25, 2024
[webpack-dev-server] Motoko	16	2774	July 19, 2023
How to use `npm start` JavaScript	5	2325	September 29, 2023
Failed to load resource: the server responded with a status of 504 (Gateway Timeout) Developers	2	2216	December 19, 2024

Webpack Proxy - ECONNREFUSED for proxy to api

Related topics