Automation has determined NetSarangComputer.PortX 2.0.5 is unavailable

[wingetbot]

The URL for version 2.0.5 of NetSarangComputer.PortX has been unavailable for 5 or more days.
This package may be removed from the repository if no valid manifest is available in the next 14 days.

If the installer has been moved, please update the manifest with the new URL. If a new version of the package is available, please create a new manifest with the valid URL, version, and SHA256 hash.
If this package is no longer available, please delete the manifest.

[wingetbot]

Suspicious installer hashes:

• 9c3052be1baac8ccf784428001656fe6221de0fac581df4fe97b5500fb622b72

[jedieaston]

PS C:\Users\WDAGUtilityAccount\Desktop\manifests> winget install NetSarangComputer.PortX -v 2.0.5
Found PortX [NetSarangComputer.PortX] Version 2.0.5
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://cdn.netsarang.net/0ac7ea20/PortX-2.0.5-Setup.exe
  ██████████████████████████████  71.6 MB / 71.6 MB
Successfully verified installer hash
Starting package install...
Successfully installed
PS C:\Users\WDAGUtilityAccount\Desktop\manifests>

@wingetbot, explain yourself!

edit: nvm, their cdn is blocking Azure:

@jedieaston ➜ /workspaces/coder-test (main ✗) $ wget https://cdn.netsarang.net/0ac7ea20/PortX-2.0.5-Setup.exe
--2022-01-21 13:17:53--  https://cdn.netsarang.net/0ac7ea20/PortX-2.0.5-Setup.exe
Resolving cdn.netsarang.net (cdn.netsarang.net)... 172.67.201.196, 104.21.74.99, 2606:4700:3032::6815:4a63, ...
Connecting to cdn.netsarang.net (cdn.netsarang.net)|172.67.201.196|:443... connected.
HTTP request sent, awaiting response... 503 Service Temporarily Unavailable
2022-01-21 13:17:53 ERROR 503: Service Temporarily Unavailable.

[Trenly]

Their entire cdn was experienceing 503's yesterday, even for me. Might have just been a regional outage or something

[vedantmgoyal9]

@denelon can't wingetbot put installer url with hash? it would be easy to check the urls, then instead of going to the manifest manualy🤔

[Trenly]

@denelon can't wingetbot put installer url with hash? it would be easy to check the urls, then instead of going to the manifest manualy🤔

Or a link to the manifest file in the repo

[denelon]

We've gone back and forth on the value of linking to the manifest since it could be changed with multiple different Git commit's. What do you think makes the most sense? I'm open to suggestions.

[jedieaston]

IMO, whatever commit had the "Suspicious installer hash" in it would probably be the most logical one. It would be really nice if on the daily check @wingetbot could check to see if a commit had been made to the affected manifest that fixed the issue, as in that case we know if the issue is still open that there is still a problem.

Alternatively, with the installer hash it could give us the InstallerUrl value, so we could at least check that.

[OfficialEsco]

Updated in #54808

Hello @wingetbot,
We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Please add your 👍 to the other issue to raise its priority. Thanks for your report!

[dklobucaric]

OT
I've searcher do downgrade portx on some Machines and i needed the link.
So here are some examples

for linux...
https://cdn.netsarang.com/0ac7ea20/PortX_2.0.10_amd64.deb
https://cdn.netsarang.com/0ac7ea20/PortX_2.0.9_amd64.deb
https://cdn.netsarang.com/0ac7ea20/PortX_2.0.8_amd64.deb
etc...

for windows ...
https://cdn.netsarang.net/0ac7ea20/PortX-2.0.10-Setup.exe
https://cdn.netsarang.net/0ac7ea20/PortX-2.0.9-Setup.exe
https://cdn.netsarang.net/0ac7ea20/PortX-2.0.8-Setup.exe
etc...