[wheybags] [0.17.52] "latest experimental" link for headless server returns 404 response.

[Xertez]

I ran into the error when my automatic update script was run. The steps are easy to replicate, because if you navigate to the download headless experimental releases page, then click on the latest experimental link, You receive the standard 404 response in a browser as well.

1. What did you do?
   I was attempting to update my headless server to the latest experimental via script, via the "latest experimental" link.
   -
2. What happened?
   A 404 response was recieved. Here is a copy of the original error recieved (note that this section is quote text instead of code display. This is intentional.):

   --2019-06-24 11:52:48-- https://www.factorio.com/get-download/latest/headless/l inux64
   Resolving www.factorio.com (www.factorio.com)... 52.73.94.166, 52.54.237.49, 52. 22.236.254, ...
   Connecting to www.factorio.com (www.factorio.com)|52.73.94.166|:443... connected .
   HTTP request sent, awaiting response... 302 FOUND
   Location: https://dcdn.factorio.com/releases/fact ... 7.51.tar.x z?key=UaJ-tFpQe_RHrZDxtQUXEA&expires=1561392168 [following]
   --2019-06-24 11:52:48-- https://dcdn.factorio.com/releases/factorio_headless_x6 4_0.17.51.tar.xz?key=UaJ-tFpQe_RHrZDxtQUXEA&expires=1561392168
   Resolving dcdn.factorio.com (dcdn.factorio.com)... 2600:3c00::f03c:91ff:fee5:659 8, 45.56.70.196
   Connecting to dcdn.factorio.com (dcdn.factorio.com)|2600:3c00::f03c:91ff:fee5:65 98|:443... failed: Connection timed out.
   Connecting to dcdn.factorio.com (dcdn.factorio.com)|45.56.70.196|:443... connect ed.
   HTTP request sent, awaiting response... 404 Not Found
   2019-06-24 11:54:58 ERROR 404: Not Found.

   
   Also, keep in mind that I did not address the "failed: Connection timed out." that you see when the script tries to utilize IPV6.That has never worked for me. This has not been an issue because when that fails the script automatically tries the IPv4 address, and that has worked in the past. For the purposes of this bug report, and because I believe the IPv6 issue is a separate bug entirely, I would like to focus on the IPv4 response of 404.
   
   -
3. What did you expect to happen instead? It might be obvious to you, but do it anyway!
   I expected for the latest experimental build for headless servers to be downloaded.
   -
4. Write down the steps to reproduce the bug if you know them.
   [a] The steps are easy to replicate, because if you open your browser and navigate to the download headless experimental releases page, then click on the latest experimental link, you receive the standard 404 response in a browser as well.
   -
   [a1] alternatively, you can use the original way I noticed this issue. I run a script via a user who has sudo permissions. Here is the "cat" of the script:

   Code: Select all

   read -p "Service Owner Password: " soPassword
   
   wget -O factorio.tar.xz https://www.factorio.com/get-download/latest/headless/linux64
   
   unxz factorio.tar.xz
   
   printf "%s\n" "$soPassword" | systemctl stop factorio
   
   printf "%s\n" "$sopassword" | systemctl disable factorio
   
   tar -C .. -xvf factorio.tar
   
   printf "%s\n" "$sopassword" | systemctl enable factorio
   
   printf "%s\n" "$sopassword" | systemctl start factorio
   
   rm factorio.tar
   

   -
5. Does it happen always, once, or sometimes?
   always as of the latest experimental release
   -
6. Be precise! When i click with the mouse on Quit in the main menu... Not: When I close the game.
   -I have checked this post for preciseness.

[kovarex]

Hello, it seems to be working now.