I think that’s a BlueOS frontend issue that’s been fixed in the beta releases but not yet in stable. This direct link should hopefully work:
http://blueos.local:7777/file-browser/files/var/logs/blueos/services/ardupilot-manager/
If there are permission errors, try removing everything after file-browser and reload the page, then click through the folders to the one you’re after.
Those tests are for the network speed between the vehicle and the topside computer, and are unrelated to internet speed. The download is from the vehicle, and upload is to the vehicle. They’re both important for normal communication (and a low download speed would be a potential reason for choppy video), but aren’t related to the vehicle’s connection to the internet (which is what matters when downloading firmware).
By the way, if your network speed is very low, and your order shipped in May or June this year, you may be running into this issue. Worth a check!
I brought up the failing firmware fetching issue internally and was told it’s possible our timeout is too short before deciding that the information was not available, because the ArduPilot servers can sometimes be very slow to respond, so we’re looking into improving that.
In the interim you may want to download firmwares directly from ArduPilot firmware : /Sub, selecting a valid one for your flight controller board (e.g. Navigator / Pixhawk 1), then using the “upload custom file” option to upload it to the vehicle.
Note that updating the autopilot firmware is only relevant if you aren’t already on the latest stable firmware. Currently that’s 4.1.0, and you can check your in-use version in QGC’s Summary Page, or in the General page of BlueOS >= 1.1 (currently only beta/master, next stable release should hopefully be quite soon).