Netdata "File does not exist, or is not accessible:" after update

Started by RutgerDiehard, June 18, 2025, 03:50:46 PM

Previous topic - Next topic
OPNsense updates just offered a Netdata update which I installed. When I attempt to access Netdata on http://[IP]:19999, I get "File does not exist, or is not accessible:" message.

I've tried removing and then reinstalling with the same result.

Not had any issues with Netdata previously so I assume it's the update that's broken it.

Quote from: RutgerDiehard on June 18, 2025, 03:50:46 PMOPNsense updates just offered a Netdata update which I installed. When I attempt to access Netdata on http://[IP]:19999, I get "File does not exist, or is not accessible:" message.

I've tried removing and then reinstalling with the same result.

Not had any issues with Netdata previously so I assume it's the update that's broken it.

Hereby confirmed - same issue after 25.1.9 Update

I'm confirming this issue as well. The /usr/local/share/netdata/web/index.html file no longer exists.

Same issue here. It worked yesterday with 25.1.9, but today it appeared as a plugin update to 2.5.2, and poof.



Hi there

Me to. Now at v. 25.1.9_2 and still netdata dosen't work. Any fix/workaround?

Best

I've just noticed the same after updating last night. I suppose if someone has the default index.html, that could be added back in?


There are a pile of files (35) and directories (9) missing from /usr/local/share/netdata/web.
I copied them from an older OPNsense VM i had from testing something ages ago and it works again.
There are a couple of issues about this logged in Github but they don't seem to be gaining much traction.

There's four main reasons:

1. netdata is community scope
2. the plugin was last updated years ago in OPNsense 22.7.1
2. the netdata error reported is not helpful
3. netdata port in FreeBSD likely broke this and an update was made there already although the problem scope is still unclear because of 1+2+3

opnsense-revert should work on an older netdata package or 25.1.10 will fix it when the FreeBSD port is correctly fixed again. Worse case someone needs to make an effort to update the plugin to whatever it was that netdata broke in a 3 year old plugin...


Cheers,
Franco