-
Notifications
You must be signed in to change notification settings - Fork 318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I can't see any chart #411
Comments
First of all, does it work fine on http://192.168.1.130:5000 ? And only then you should proceed with http://tpm.unraid.nas |
I've updated the issue with my findings. Please take a look at it. The reverse proxy is not an issue btw. |
I see now. I made some changes recently so it can remember which streamer was selected. |
Any first run of the app will encounter this issue until a name of a streamer is clicked. Then the error will never happen again. |
Yes, gotcha. Incognito = clean browser localStorage, same as on the first opening. ;) |
Describe the bug
I installed your app on my unraid server using docker. Edited the conf file to enable the WebUI:
twitch_miner.analytics(host="0.0.0.0", port=5000, refresh=5, days_ago=7) # Start the Analytics web-server
Then I set up Nginx-Reverse-Proxy to connect through
http://tpm.unraid.nas/
rather thanhttp://192.168.1.130:5000/
.I can access the WebUI just fine and I can see the logs and how the points increase, but the graph is stuck at loading.
Chrome's Dev Console shows this:
Firefox' Dev Console shows this:
Basically,
streamer
is null. But here's the kicker:If I click on any of the streamer names, the chart loads and any page refresh works OK because the browser remembers my selection.
The bug, apparently, is that there's no streamer selected on first page load and that's why the chart crashes.
Steps to reproduce
Expected behavior
The graphs load.
Operating system
Unraid 6.12.4
Python version
Python 3.12.0
Miner version
v2-1.9.0
Other relevant software versions
No response
Logs
It's not an error of the backend.
Additional context
No response
The text was updated successfully, but these errors were encountered: