Speedtest-Tracker
Speedtest-Tracker copied to clipboard
[BUG] Blank page when accessing via web interface
Describe the bug I find this issue keeps reoccurring. My docker container has been running for a few weeks and after a period of time accessing the web interface (e.g. 10.10.10.2:8996) results in a blank page.
I've discovered a workaround fix to this problem which is simply restarting the docker container. However, this of course is not ideal.
It's also worth noting that I also connect to the container using Organizr which displays the results of application. For some reason, Organizr still displays the results within it's own page as I would expect on the direct web interface page. Perhaps they are entirely separate, but I thought I'd note as it displays the container is still functioning.
Within Chrome, the console prints the follow:
192.168.85.2/:39 GET http://192.168.85.2:8996/files/js/app.js?v=1-12-0 net::ERR_INCOMPLETE_CHUNKED_ENCODING 200 (OK) DevTools failed to load source map: Could not load content for http://192.168.85.2:8996/files/js/popper.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
Within Edge, the console prints the follow:
192.168.85.2/:39 GET http://192.168.85.2:8996/files/js/app.js?v=1-12-0 net::ERR_INCOMPLETE_CHUNKED_ENCODING 200 (OK) DevTools failed to load source map: Could not load content for http://192.168.85.2:8996/files/js/popper.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
To Reproduce Steps to reproduce the behaviour are difficult as it seems to occur periodically. However, I would say:
- Run the docker container
- Use the service for a number of weeks via the Web Interface
- After a period of time, see error (blank page)
Expected behavior Of course the expected behaviour here is to see the standard web page.
Context
- OS: Synology > Docker
- Speedtest-Tracker Version: v1.12.0
Additional context Add any other context about the problem here.
Same for me since I installed a few months ago, issue appears to be related with fastcgi, it looses its permissions over a temporary directory.
Like people comment here #607 and here #368
There are a few workarounds like restart docker container or chmod -R /var/lib/nginx/tmp/fastcgi but like you said this is not ideal.
Hope @henrywhitaker3 figure how to fix this out.
I use environment variables (PUID and PGID) to set the container user and group ids to one that has access to that folder on the system.
Have no issues for a long time.
Hope this helps someone.
Sent from my iPhone
On Nov 20, 2021, at 12:33, garanda21 @.***> wrote:
Same for me since I installed a few months ago, issue appears to be related with fastcgi, it looses its permissions over a temporary directory.
Like people comment here #607 and here #368
There are a few workarounds like restart docker container or chmod -R /var/lib/nginx/tmp/fastcgi but like you said this is not ideal.
Hope @henrywhitaker3 figure how to fix this out.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.
I use environment variables (PUID and PGID) to set the container user and group ids to one that has access to that folder on the system. Have no issues for a long time. Hope this helps someone. …
No working for me , PUID and PGID since the beginning, user with full control to the folder. And issue still remains.
Thanks anyway.
I also have been using PUID and PGID since I started using the container and I still have this issue.
Same problem here.
Is this project dead?
What's wrong here ?
https://ibb.co/RScqt7K
Looks like a corrupt database
Sent from my iPhone
On Jan 15, 2022, at 17:24, Asad Islam @.***> wrote:
What's wrong here ?
https://ibb.co/RScqt7K
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.
Bumping this if that's okay as I'd still like to see a fix as Im sure would many others.