Alicia Sykes

I think you're right @lee88688 - thanks for the suggestion. I'll do a bit more testing, but if all that passes, this will be released later this week, in 3.0.1.

Yup, you were right. Much better without the second build! Merged 1bbb91b3fef501b8e23bc8942c6cf59df3db36a5 into #1542 and released to [3.0.1](https://github.com/Lissy93/dashy/releases/tag/3.0.1)

Could you share the chart and nginx config that you used, as I can't see what might be wrong or try and recreate anything without those details.

For the `The engine "node" is incompatible with this module` error specifically, try running with the `--ignore-engines` E.g. `yarn install --ignore-engines` should fix this. And that will work with Node...

Hey @bogdanjsx. Re the incorrect dates, yeah that's a dup of #1376 - But your insight (3 hour increments) is the cause, so thank you for finding that! In terms...

> An error occurred, see the logs for more info. > Unable to fetch data > Retry > Flag (error image) > > I see no errors in app info....

Looks like you're looking at the wrong logs Widgets are executed client-side, so you'll need to check your browser log (as opposed to the Docker logs). [Here's how](https://github.com/Lissy93/dashy/blob/master/docs/troubleshooting.md#how-to-open-browser-console) (TL;DR Ctrl...

> I don't really know if that is practical for the backend, you could run a flask server for example and use http endpoints and input them into dashy, however...

Cheers @bajo and @joshbuker - sorry this took so long to come around to. Given it was a breaking change it made sense to include it with the other breaking...

I'm going to close as a dup of #990, follow that ticket instead for updates