Could you share more please? Probably check the browser console to see if a network xhr request is failing or maybe there is a js error on the console?
First of all thank you for your reply.
I currently cannot access to this Netdata instance through a desktop web browser (this should be fixed by the end of the week or next week).
Here’s the debug output I can get atm:
[0304/152157.888469:INFO:CONSOLE(1)] "Running in development mode version: cloud-frontend 7.41.3", source: http://192.168.xx:19999/v3/app.73a9e46f037759645194.js (1)
[0304/152157.933033:INFO:CONSOLE(2)] "Uncaught (in promise) UnknownError: Internal error.", source: http://192.168.xx:19999/v3/6375.7e521a060410d9901eeb.js (2)
[0304/152157.940507:INFO:CONSOLE(2)] "Uncaught (in promise) UnknownError: Internal error.", source: http://192.168.xx:19999/v3/6375.7e521a060410d9901eeb.js (2)
[0304/152159.342567:INFO:CONSOLE(2)] "RangeError: Incorrect locale information provided", source: http://192.168.xx:19999/v3/npm.react.dom.a0486f71f0f8ec723b8c.js (2)
[0304/152159.342688:INFO:CONSOLE(1)] "RangeError: Incorrect locale information provided [object Object]", source: http://192.168.xx:19999/v3/app.73a9e46f037759645194.js (1)
Most of the time the error you saw on the browser is because of a server error or a bad response. I will try to check the version you shared to maybe find what could trigger it. If you can share the page/url you were trying to visit at the time it could help me narrow it down. If we dont find anything and you manage to visit it again, please open the network tab on the brower console to check if any request is failing.
Ok, thank you for your help!
The error pops as soon as I click on the “Skip and use the dashboard anonymously” link on the homepage, and directly if I append /v3 at the end of the URL (eg. http://netdata_server_ip:19999/v3)
I’ll set up a desktop environment to access the dashboard, hopefully by the end of the week.
Could you share the browser you are using to access the dashboard?
From your screenshot I can gather it’s a text based browser, and I thought there are no valid locales there, so we are getting RangeError: Incorrect locale information provided and crashes everything.
But I tried lynx and browsh and both work - not on 100% but they do not crash.
Let me know more of your environment. Probably/hopefully is just the missing locale info and I have the fix ready for it.
Sorry for the delay of my reply.
Of course, I use Carbonyl (lighter and requires less dependencies than Browsh).
Netdata VM and the “client” one run in Outscale Cloud, on Debian 12 (using theirs official image).
Interestingly, in an other non-cloud environment, using Carbonyl to access Netdata dashboard (hosted on a VM in the non-cloud environment) doesn’t trigger any error.
Debian images used on this non-cloud environment are Bookworm’s generic cloud.
It looks like even though the implementation of the Intl API is correct on the carbonyl, the ICU (International Components for Unicode) has outdated data. For example, navigator.language would return: en-US@posix (@posix → legacy suffix not recognized by the Intl API).
Said that, I saw the problem only on the linux carbonyl running with docker. I think if you do pass the correct ICU data (like install libicu) would make it work.
Nevertheless, the frontend code was checking if the browser had implemented the Intl API before falling back to polyfills. Now we will drop the usage of the Intl API when we get an error coming from it - in this case, passing a wrong locale string to it.
For your case, make sure when you run Netdata to open the datetime picker at the top and select the timezone you will need. Most probably the default selected should be something like 0, which doesn’t make sense, but that’s what outdate locale data gets you
The fix is already available on latest netdata UI, but will be in the local folder v3, in the next nightly release (tomorrow). Try to access netdata without the v3 in the url (this way you always have the latest UI). Otherwise you will need to upgrade to the latest nightly version to get the fresh v3 UI.
Hopefully it will work out for you. Let me know how it went! Cheerz
Oh ok, I understand.
Thank you for the time you spent to sort this issue out!
I accessed to the dashboard (using Carbonyl) and it works!
We installed the package on the stable channel; I re-installed Netdata from the nightly channel through kickstart.sh, accessed the dashboard both from the homepage and from /v3 URL and both work!
Thanks again for fixing this issue that enable for us the use of this great software in our cloud environment!
Have a nice day