# Issue with Forked Node-RED Dashboard Installation: ENOENT Error on File Path

**URL:** <https://discourse.nodered.org/t/issue-with-forked-node-red-dashboard-installation-enoent-error-on-file-path/92087>\
**Category:** Dashboard\
**Tags:** dashboard-2\
**Created:** [1 October 2024 06:12 UTC](https://discourse.nodered.org/t/issue-with-forked-node-red-dashboard-installation-enoent-error-on-file-path/92087 "2024-10-01T06:12:32Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![DhamodharanGopal](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dhamodharangopal/32/95512_2.png) [@DhamodharanGopal](https://discourse.nodered.org/u/DhamodharanGopal)\
**Post date:** [1 October 2024 06:12 UTC](https://discourse.nodered.org/t/issue-with-forked-node-red-dashboard-installation-enoent-error-on-file-path/92087/1 "2024-10-01T06:12:32Z")

</div>

Hello everyone,

I’ve encountered an issue with a forked installation of the Node-RED Dashboard. After installing the dashboard from the forked repository, I’m facing an error that prevents it from loading correctly. Specifically, I receive the following error message:

Error: ENOENT: no such file or directory, stat '/home/dhamo/.node-red/node\_modules/@flowfuse/node-red-dashboard/dist/index.html'

1. Has anyone else encountered this issue with forked installations of the Node-RED Dashboard?
2. Is there a specific build process required to generate the `dist` folder for the dashboard in forked installations?
3. Any suggestions on how to resolve the missing file issue?

I appreciate any guidance or troubleshooting tips you can provide. Thanks in advance!

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [1 October 2024 06:34 UTC](https://discourse.nodered.org/t/issue-with-forked-node-red-dashboard-installation-enoent-error-on-file-path/92087/2 "2024-10-01T06:34:48Z")

</div>

It's all in the docs: [Contributing | Node-RED Dashboard 2.0](https://dashboard.flowfuse.com/contributing/#contributing)

---

<div class="post-metadata">

**Author:** ![DhamodharanGopal](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dhamodharangopal/32/95512_2.png) [@DhamodharanGopal](https://discourse.nodered.org/u/DhamodharanGopal)\
**Post date:** [1 October 2024 06:51 UTC](https://discourse.nodered.org/t/issue-with-forked-node-red-dashboard-installation-enoent-error-on-file-path/92087/3 "2024-10-01T06:51:05Z")

</div>

Thanks,I will review it once again.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [1 October 2024 08:50 UTC](https://discourse.nodered.org/t/issue-with-forked-node-red-dashboard-installation-enoent-error-on-file-path/92087/4 "2024-10-01T08:50:20Z")

</div>

In particular

1. Clone the repository locally
2. Go into the node-red-dashboard folder (assuming that is where you cloned it to) and run `npm install` to install dependencies
3. Run `NODE_ENV=development npm run build` to build a debug version, or `npm run build` to build without debug.
4. Go into your .node-red folder and run `npm install /path/to/node-red-dashboard`.
5. Restart node-red.

After editing the dashboard code you just need to re-run 3 and 5

---

<div class="post-metadata">

**Author:** ![DhamodharanGopal](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dhamodharangopal/32/95512_2.png) [@DhamodharanGopal](https://discourse.nodered.org/u/DhamodharanGopal)\
**Post date:** [2 October 2024 03:34 UTC](https://discourse.nodered.org/t/issue-with-forked-node-red-dashboard-installation-enoent-error-on-file-path/92087/5 "2024-10-02T03:34:06Z")

</div>

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/4/a/4ab65898c913d1f323aa5a851f15f5486a075406.png)

- I have problem while cloning the forked repo facing this issue how to fix
- Can't able to clone at any path in home/dhamo/

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [2 October 2024 08:11 UTC](https://discourse.nodered.org/t/issue-with-forked-node-red-dashboard-installation-enoent-error-on-file-path/92087/6 "2024-10-02T08:11:16Z")

</div>

In future please copy/paste rather than screenshot, where possible. If you had done so I would try that command to see if it is a network problem or a problem with your repository.

I think it is most likely a network problem of some sort, but it is certainly not anything to do with node red.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [2 October 2024 09:10 UTC](https://discourse.nodered.org/t/issue-with-forked-node-red-dashboard-installation-enoent-error-on-file-path/92087/7 "2024-10-02T09:10:00Z")

</div>

First search result of " [RPC failed; curl 92](https://stackoverflow.com/questions/59282476/error-rpc-failed-curl-92-http-2-stream-0-was-not-closed-cleanly-protocol-erro)"

> In most cases, increasing the buffer size will work.
> 
> ```auto
> git config http.postBuffer 524288000
> 
> ```
> 
> It worked for me.
> 
> Use of
> 
> ```auto
> git config --global http.version HTTP/1.1
> 
> ```
> 
> should be kept as a last option.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [1 November 2024 09:10 UTC](https://discourse.nodered.org/t/issue-with-forked-node-red-dashboard-installation-enoent-error-on-file-path/92087/8 "2024-11-01T09:10:33Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.