June 19, 20242 yr Support for Docker image Myspeed.dev template Application Name: Myspeed.dev Application: https://myspeed.dev/ Documentation: https://docs.myspeed.dev/ Overview : MySpeed is a speed test analysis software that stores the speed of your internet for up to 30 days. This can also be useful if you want to know when your network might have drops or if you want to check if your internet matches the booked values from your contract. It is recommended to install the software at home. Of course, it can also be installed on a server in a data center, if you wish Make sure to look at the complete documentation Please post any questions/issues relating to this docker template you have in this thread.
June 20, 20242 yr Just now, ZappyZap said: hmmm weird let me check that Ok - it might not be your install. I just tried installing a couple of other apps and getting the same 503 error
June 20, 20242 yr Author well i think the issue come from docker hub : $ docker pull ubuntu:latest Error response from daemon: Head "https://registry-1.docker.io/v2/library/ubuntu/manifests/latest": received unexpected HTTP status: 503 Service Unavailable confirmed : Edited June 20, 20242 yr by ZappyZap
June 20, 20242 yr 2 minutes ago, ZappyZap said: Ok seems to be back.... give it an other try and let me know It's installing now. Gawd - random errors are terrifying LOL
June 25, 20242 yr Getting this with MySpeed after 2 days of having it installed. It just reloads endlessly and I never see the UI or dashboard. Any ideas? Logs show it's working fine though: Test #107 was executed successfully in 9s. 🏓 1 ⬇ 932.28️ ⬆ 492.6️ Looking for network interfaces... Found interface eth0 with IP 172.18.0.13 Test #108 was executed successfully in 13s. 🏓 0 ⬇ 931.65️ ⬆ 492.58️ Looking for network interfaces... Found interface eth0 with IP 172.18.0.13 Test #109 was executed successfully in 12s. 🏓 0 ⬇ 889.88️ ⬆ 492.56️ Looking for network interfaces... Found interface eth0 with IP 172.18.0.13 Test #110 was executed successfully in 10s. 🏓 0 ⬇ 898.87️ ⬆ 492.39️ Looking for network interfaces... Found interface eth0 with IP 172.18.0.13 Test #111 was executed successfully in 10s. 🏓 0 ⬇ 913.87️ ⬆ 492.49️ Looking for network interfaces... Found interface eth0 with IP 172.18.0.13 Test #112 was executed successfully in 12s. 🏓 0 ⬇ 922.01️ ⬆ 493.25️ I've done nothing to modify the docker container at all. Edited June 25, 20242 yr by plantsandbinary
June 25, 20242 yr Author open a shel in the container and check : /myspeed/build/assets/locales open a issue on their github, first time seeing this errors
September 9, 20241 yr Hi First of all thanks for implementing this docker! Was looking for an nice graphical GUI for monitoring my connection. Somehow the donwload speed seems to be sometimes limited by something to 4 Mbit - I can't figure it out, what is causing this issue. Even when I start manual tests like 1 minute in between it switches between the real speed ~630 Mbit and this 4 Mbit. Maybe someone has an idea what is reason of this. Thanks in advance! Lelo
September 9, 20241 yr this is the Log File: Error: Cannot read: at module.exports (/myspeed/server/util/speedtest.js:65:29) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async module.exports.run (/myspeed/server/tasks/speedtest.js:57:21) at async module.exports.create (/myspeed/server/tasks/speedtest.js:95:20) at async module.exports.runTask (/myspeed/server/tasks/timer.js:18:5) Test #82 was executed successfully in 13s. 🏓 10 ⬇ 624.93️ ⬆ 64.08️ Looking for network interfaces... Found interface eth0 with IP 192.168.0.112 Test #83 was executed successfully in 20s. 🏓 12 ⬇ 0.74️ ⬆ 64.31️ Looking for network interfaces... Found interface eth0 with IP 192.168.0.112 Error: Cannot read: at module.exports (/myspeed/server/util/speedtest.js:65:29) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async module.exports.run (/myspeed/server/tasks/speedtest.js:57:21) at async module.exports.create (/myspeed/server/tasks/speedtest.js:95:20) at async module.exports.runTask (/myspeed/server/tasks/timer.js:18:5) Test #84 was executed successfully in 15s. 🏓 14 ⬇ 628.34️ ⬆ 64.47️ Looking for network interfaces... Found interface eth0 with IP 192.168.0.112 Test #85 was executed successfully in 26s. 🏓 10 ⬇ 1.03️ ⬆ 47.52️ Looking for network interfaces... Found interface eth0 with IP 192.168.0.112 Error: Latency test failed at module.exports (/myspeed/server/util/speedtest.js:65:29) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async module.exports.run (/myspeed/server/tasks/speedtest.js:57:21) at async module.exports.create (/myspeed/server/tasks/speedtest.js:95:20) at async module.exports.runTask (/myspeed/server/tasks/timer.js:18:5) Test #86 was executed successfully in 15s. 🏓 12 ⬇ 628.81️ ⬆ 64.32️ Looking for network interfaces... Found interface eth0 with IP 192.168.0.112 Test #87 was executed successfully in 21s. 🏓 11 ⬇ 5.87️ ⬆ 64.03️ Looking for network interfaces... Found interface eth0 with IP 192.168.0.112 Test #88 was executed successfully in 12s. 🏓 9 ⬇ 630.01️ ⬆ 64.69️ Looking for network interfaces... Found interface eth0 with IP 192.168.0.112 Test #89 was executed successfully in 12s. 🏓 10 ⬇ 630.13️ ⬆ 64.29️ Looking for network interfaces... Found interface eth0 with IP 192.168.0.112 Test #90 was executed successfully in 11s. 🏓 9 ⬇ 630.99️ ⬆ 64.19️ Looking for network interfaces... Found interface eth0 with IP 192.168.0.112 Test #91 was executed successfully in 13s. 🏓 9 ⬇ 629.67️ ⬆ 64.48️ Looking for network interfaces... Found interface eth0 with IP 192.168.0.112 Test #92 was executed successfully in 15s. 🏓 10 ⬇ 629.96️ ⬆ 44.97️ Looking for network interfaces... Found interface eth0 with IP 192.168.0.112 Test #93 was executed successfully in 10s. 🏓 10 ⬇ 630.04️ ⬆ 64.37️ Looking for network interfaces... Found interface eth0 with IP 192.168.0.112 Test #94 was executed successfully in 20s. 🏓 10 ⬇ 13.82️ ⬆ 63.33️ Looking for network interfaces... Found interface eth0 with IP 192.168.0.112 Test #95 was executed successfully in 23s. 🏓 10 ⬇ 7.37️ ⬆ 42.33️ Looking for network interfaces... Found interface eth0 with IP 192.168.0.112 Test #96 was executed successfully in 19s. 🏓 13 ⬇ 6.61️ ⬆ 63.66️ Looking for network interfaces... Found interface eth0 with IP 192.168.0.112 Error: Latency test failed at module.exports (/myspeed/server/util/speedtest.js:65:29) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async module.exports.run (/myspeed/server/tasks/speedtest.js:57:21) at async module.exports.create (/myspeed/server/tasks/speedtest.js:95:20) at async module.exports.runTask (/myspeed/server/tasks/timer.js:18:5) Test #97 was executed successfully in 21s. 🏓 10 ⬇ 4.27️ ⬆ 41.66️ Looking for network interfaces... Found interface eth0 with IP 192.168.0.112 Test #98 was executed successfully in 23s. 🏓 12 ⬇ 4.06️ ⬆ 62.9️ Looking for network interfaces... Found interface eth0 with IP 192.168.0.112 Error: Latency test failed at module.exports (/myspeed/server/util/speedtest.js:65:29) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async module.exports.run (/myspeed/server/tasks/speedtest.js:57:21) at async module.exports.create (/myspeed/server/tasks/speedtest.js:95:20) at async module.exports.runTask (/myspeed/server/tasks/timer.js:18:5) Test #99 was executed successfully in 17s. 🏓 14 ⬇ 614.37️ ⬆ 46️ Test #100 was executed successfully in 24s. 🏓 11 ⬇ 3.23️ ⬆ 45.54️ Error: Cannot read: at module.exports (/myspeed/server/util/speedtest.js:65:29) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async module.exports.run (/myspeed/server/tasks/speedtest.js:57:21) at async module.exports.create (/myspeed/server/tasks/speedtest.js:95:20) at async /myspeed/server/routes/speedtests.js:26:21 Test #101 was executed successfully in 11s. 🏓 11 ⬇ 629.81️ ⬆ 63.51️ Error: Latency test failed at module.exports (/myspeed/server/util/speedtest.js:65:29) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async module.exports.run (/myspeed/server/tasks/speedtest.js:57:21) at async module.exports.create (/myspeed/server/tasks/speedtest.js:95:20) at async /myspeed/server/routes/speedtests.js:26:21 Test #103 was executed successfully in 17s. 🏓 13 ⬇ 631.1️ ⬆ 35.28️ Test #104 was executed successfully in 19s. 🏓 166 ⬇ 2.84️ ⬆ 63.32️ Error: Cannot open socket at module.exports (/myspeed/server/util/speedtest.js:65:29) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async module.exports.run (/myspeed/server/tasks/speedtest.js:57:21) at async module.exports.create (/myspeed/server/tasks/speedtest.js:95:20) at async /myspeed/server/routes/speedtests.js:26:21 Test #105 was executed successfully in 15s. 🏓 14 ⬇ 629.75️ ⬆ 63.48️ Edited September 9, 20241 yr by Lelo
January 19, 20251 yr Hi everyone, This was running great when I installed it for the first time. Now after rebooting, reinstalling, this no longer works! Logs say: "Interface eth0 not found. Falling back to default." Seems to be a bug already captured here: https://github.com/gnmyt/myspeed/issues/806 But, can't seem to get this going again under Unraid. Any ideas? Cheers, Xav.
January 21, 20251 yr On 1/20/2025 at 1:15 PM, ZappyZap said: ok seems like a bug , i will follow the issue #806 closely I did find one work around... As I had recently changed some of my local network settings, I realised I had forgotten to specify an additional DNS server (secondary) in Network Settings. I just had the default gateway listed. Added Google's (8.8.8.8) and then I could access the WebUI again.
January 21, 20251 yr Author 1 hour ago, xavierda said: I did find one work around... As I had recently changed some of my local network settings, I realised I had forgotten to specify an additional DNS server (secondary) in Network Settings. I just had the default gateway listed. Added Google's (8.8.8.8) and then I could access the WebUI again. great
June 18, 20251 yr For some reason when the scheduled test is run, the results are wildly off compared to a manual test. Has anyone else had this issue
November 20, 2025Nov 20 When I export the log to look at it the times for the tests are no where near when they where taken. Is there a way to fix this or adjust the time zone?
November 21, 2025Nov 21 Author 6 hours ago, kizer said:When I export the log to look at it the times for the tests are no where near when they where taken. Is there a way to fix this or adjust the time zone?try to add a ENv variable TZ=Let me know
December 8, 2025Dec 8 Noticing a weird issue with this. It only ever seems to keep the last 24ish hours worth of tests in the GUI?But if you go to export the tests it clearly shows more tests than the GUI? The export contains all the tests I would expect it to, significantly more than the GUI shows.If I try to run the recommendations (since I have 24 tests supposedly) it tells me I don't have enough tests?Nothing particularly weird or interesting about my docker setup:EDIT: Ah ok, I'm an idiot and didn't realize you needed to set the period to see more tests. The recommendations still don't appear to be working though, it just keeps giving me the error about not having enough tests? Am I just missing something else obvious? Edited December 8, 2025Dec 8 by weirdcrap
.thumb.jpg.bec61e4e919a9235cc4475f8cb53d5e3.jpg)
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.