Checksum missing for version 6.1.3.3

[barryjj]

My ASF is stuck at 6.1.2.3 because when it tries to update to 6.1.3.3 it fails to find the checksum at the following URL:
https://asf.justarchi.net/Api/Checksum/6.1.3.3/win-x64

Do I need to submit an issue for this? How can I get someone to put the checksum where the auto update function expects it to be?

[JustArchi]

The backend preserves the checksums for latest stable and pre-release version of ASF - that includes V6.1.4.3 and V6.1.3.3 as of today, so this is not your issue.

[Abrynos]

@JustArchi status-code is 401. Response indicates the same thing

{"status":401}

[JustArchi]

Status code is 401 because you're not authorized to call this from a web browser - only from inside ASF. That's not a missing checksum problem.

Changed it regardless though.

[barryjj]

I can verify that the 401 at the URL has been replaced by the checksum in a normal browser now... but my ASF install is still having issues with it.

I pulled the following out of the UI after telling it to update to the newer detected version manually:

[18:10:19] INFO ASF > UpdateASF() Local version: 6.1.2.3 | Remote version: 6.1.3.3
[18:10:19] INFO ASF > UpdateASF() Fetching checksum from the remote server...
[18:10:19] DEBUG ASF > InternalRequest() Forbidden <- GET https://asf.justarchi.net/Api/Checksum/6.1.3.3/win-x64
[18:10:19] WARN ASF > UrlGetToJsonObject() Request failed after 5 attempts!
[18:10:19] DEBUG ASF > UrlGetToJsonObject() Request failing: https://asf.justarchi.net/Api/Checksum/6.1.3.3/win-x64
[18:10:19] WARN ASF > UpdateASF() Failed to fetch checksum of the downloaded binary - refusing to proceed with the update procedure at this time as an additional security measure.

This goes pretty much hand in hand with what I've been seeing in the console:

I thought for a minute that it was windows firewall deciding to block ASF from making the calls, but that doesn't seem to be the case either as disabling windows defender entirely doesn't solve the problem.

Any ideas?

[JustArchi]

That's because, as I suspected in the original response, your issue is not related to any backend server issue, but to your IP being unable to reach ASF server. Most of the time that's the result of either, a ban on ASFB part, or your own networking issue, e.g. censorship by your local government.

Fetch the url using the same machine hosting ASF and see why you're getting forbidden - there should be an error there. Since you're using Windows, this means launching web browser from target machine and seeing why it doesn't work.

[barryjj]

That's because, as I suspected in the original response, your issue is not related to any backend server issue, but to your IP being unable to reach ASF server. Most of the time that's the result of either, a ban on ASFB part, or your own networking issue, e.g. censorship by your local government.

Fetch the url using the same machine hosting ASF and see why you're getting forbidden - there should be an error there. Since you're using Windows, this means launching web browser from target machine and seeing why it doesn't work.

Strangely, after you enabled http access to the checksums earlier, the browser has gone from throwing a Status Code 401 to working just fine:

{"checksum":"88581e941dbf9cd0ba6e15cbc685233a3e0792532b6e04e84bd7148283b5996966629f049257f6c6323ecfc85930993c6c22e64af75e55a19a81650dff337ccc","Result":"88581e941dbf9cd0ba6e15cbc685233a3e0792532b6e04e84bd7148283b5996966629f049257f6c6323ecfc85930993c6c22e64af75e55a19a81650dff337ccc","Message":"OK","Success":true}

I did try to hit the URL via a curl command, but that ends up complaining that JS and cookies aren't enabled... could ASF possibly bet getting the same type of response back if the UrlGetToJsonObject() doesn't support JS/cookies either?

[JustArchi]

This means that cloudflare has identified your IP as malicious/possible bot, ASF doesn't have JS engine and it won't have one. The block is typically temporary. I recommend you to update manually in this case.

I've purged the detection engine for you just now, so you can try again and see if it helped.

[barryjj]

That must've done it -- I had manually updated to 6.1.3.3 as suggested, but now that 6.1.4.3 is available, it managed to update itself again.

Thank you!

[barryjj]

Didn't mean to close out the discussion...

Please let me know if there's anything else I can try outside of manually updating via reinstall -- or if there's any additional debug information that would prove helpful.

It got cut off in the screenshot, but if it's helpful at all:
.NET 9.0.1; win-x64; Microsoft Windows 10.0.26100