Open Galateanul opened 2 years ago
Hi there, I am sorry for late response, I expirience this problem as well if you use legacy http latency test not sure why it happens
for hosting your own server you need a VPS (which has better connection than you have in your home of course)
then its just simply running OoklaServer.exe (oh shit, I didn't archive linux version, hmm, I think its somewhere in Documentation) with config like this
#
# This is a sample configuration file for OoklaServer
#
# OoklaServer Options
# The server listens to TCP port 5060 and 8080 by default. This can be changed to any other port if desired. Only a single port is required.
OoklaServer.tcpPorts = 5060,8080
# The server listens to UDP port 5060 and 8080 by default. This can be changed to any other port if desired. Only a single port is required.
OoklaServer.udpPorts = 5060,8080
# Remove the comment mark below to bind OoklaServer to IPv6
# OoklaServer.useIPv6 = true
# OoklaServer.allowedDomains allows you to limit access to your OoklaServer. The default allows all *
# Remove the comment below to allow access from Ookla.com, Speedtest,net, and simply add your domain(s)
# OoklaServer.allowedDomains = ookla.com, speedtest.net
OoklaServer.maxThreads = 5120
# Enable auto updates (default)
# OoklaServer.enableAutoUpdate = true
# Log to the Console
logging.loggers.app.name = Application
logging.loggers.app.channel.class = ConsoleChannel
logging.loggers.app.channel.pattern = %Y-%m-%d %H:%M:%S [%P - %I] [%p] %t
logging.loggers.app.level = information
# Log to files
#logging.loggers.app.name = Application
#logging.loggers.app.channel.class = FileChannel
#logging.loggers.app.channel.pattern = %Y-%m-%d %H:%M:%S [%P - %I] [%p] %t
#logging.loggers.app.channel.path = ${application.dir}/ooklaserver.log
#logging.loggers.app.level = information
name the file OoklaServer.properties, place it in the same dir and run OoklaServer
then its just metter of changeing the config on speedtest to point to your custom server
if anything is not clear, you can always ask :smile:
Hi! Don't worry. The explanation on how to host your own server is very clear and comprehensive although I am unfortunately left with the problem that all tests stop at 290 Mbps... Is there any way to fix this limit? Thanks
Hi there, did you manage to host the server up, does it work now? I tried this myself
and it appears download is realy stuck for some reason (although I think my problem is that the server that I am hosting this on has a lot do do so its (servers --> users download)upload is bottled
BTW: there is another problem we need to fix, its the map, you see the map is hosted on ookla servers, right now its still up, but you never know when they will deletes their map tiles, and when they do, then speedtest will look odd without the map)
now downloading all the maps (which you can do, using a program like MapTilesDownloader
will take a lot of space, so I never done that even if I manage to archive them, I don't think I could archive them here because of space constraints on github, so if you have any other idea where to archive them (which needs to be done soon) let me know
Hi! The speedtest on my server doesn't go over 295 Mbps despite my connection being 940 Mbps. During the download test it's like it's lagging because it doesn't go smooth and doesn't go over 295 Mbps. The upload is similar but my connection goes 300 Mbps so I don't know if the same problem applies to the upload. I have already solved the correct display of ISP, location and total number of tests done but with the servers I just used the server.xml file you had uploaded on the handout:. Most servers don't work but others apparently do but none exceed that speed.... You told me it was possible to host your own server, maybe you need that to be able to measure the actual speed up to 940 Mbps. How do you host your own server? Thanks again.