Following the download link for logitechmediaserver_8.5.2_amd64.deb results in a 404
Closed this issue · 6 comments
On the download page, when trying to download the most recent version of .deb for amd64 Linux, I run into a 404 page.
Working fine here. Can you double check with curl or something in verbose mode to see whether it's doing odd forwarding or something?
From my home server, where I want to install it:
$ wget https://downloads.lms-community.org/LogitechMediaServer_v8.5.2/logitechmediaserver_8.5.2_amd64.deb
--2024-06-13 13:57:42-- https://downloads.lms-community.org/LogitechMediaServer_v8.5.2/logitechmediaserver_8.5.2_amd64.deb
Resolving downloads.lms-community.org (downloads.lms-community.org)... 172.67.213.99, 104.21.53.138, 2606:4700:3032::6815:358a, ...
Connecting to downloads.lms-community.org (downloads.lms-community.org)|172.67.213.99|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2024-06-13 13:57:42 ERROR 404: Not Found.
From my computer at work, I get the same result. And this page below in my browser. The error message in the browser hints at object permissions. Could it be that it's a private object and you are somehow authorised to access it?
Can you curl -I
the url?
% curl -I https://downloads.lms-community.org/LogitechMediaServer_v8.5.2/logitechmediaserver_8.5.2_amd64.deb
HTTP/2 200
date: Thu, 13 Jun 2024 12:33:50 GMT
content-type: application/vnd.debian.binary-package
content-length: 25715568
etag: "d76755d16158979dd2bb135f42c1255d-4"
last-modified: Sun, 26 May 2024 15:52:05 GMT
vary: Accept-Encoding
cache-control: max-age=31536000
cf-cache-status: MISS
accept-ranges: bytes
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=ajzNixQegWYM4b6qXEU1Z7jFX4dB1Dl%2B817JsYgw0e1ceQvfsfm4NTwNZa300%2BoLAfDLzeECYLDCFawhSOYQ8L0uhsG2cgc3JZ%2FG5K3MS5K483Uf0wAkhaeceycZn1xVZL5mJI9wvn9EjUk9mrc%3D"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
server: cloudflare
cf-ray: 89321c836aeebe68-ZRH
alt-svc: h3=":443"; ma=86400
I purged the cache for that file. Maybe that's "fixing" the issue?
Yeah, getting the same results as you. But it also works with wget and in the browser now :) Thanks, Michael!
Thanks for letting me know! This should not happen. But I'll hopefully remember next time somebody reports a similar issue.