During install it sees all downloads of Foundry as Windows .exe files

[djk4346]

I've been racking my brain on this one. I've tried to use by username and password, I've tried the timed URL, I've tried to download the file myself and use container_cache. No matter what I do, I get the below message indicating that the file is a windows .exe file. But it's not, I know for a fact that I downloaded the linux .zip file. I've tried this many times and I get this same message every time. Any thoughts would be very much appreciated.

[felddy]

That is very odd. Please enable the verbose logging by setting the environment variable CONTAINER_VERBOSE to true, and then post the logs. Specifically we are looking for the section where it is detecting the mime type of the file.

Entrypoint | 2023-10-06 15:26:04 | [error] Please provide the 'Linux/NodeJS' version of the release or URL.
Entrypoint | 2023-10-06 15:26:17 | [debug] Timezone set to: UTC
Entrypoint | 2023-10-06 15:26:17 | [info] Starting felddy/foundryvtt container v11.313.0
Entrypoint | 2023-10-06 15:26:17 | [debug] CONTAINER_VERBOSE set.  Debug logging enabled.
Entrypoint | 2023-10-06 15:26:17 | [debug] Running as: uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),11(floppy),20(dialout),26(tape),27(video)
Entrypoint | 2023-10-06 15:26:17 | [debug] Environment: CONTAINER_CACHE=/data/container_cache
CONTAINER_VERBOSE=true
FOUNDRY_HOME=/home/foundry
FOUNDRY_LICENSE_KEY=[REDACTED]
FOUNDRY_RELEASE_URL=https://foundryvtt.s3.amazonaws.com/releases/11.313/FoundryVTT-11.313.zip?AWSAccessKeyId=AKIA2KJE5YZ3BCQQ6DH3&Signature=YLobFu78PEHP5evcGETQQg7ag3U%3D&Expires=1696606223
FOUNDRY_VERSION=11.313
HOME=/root
HOSTNAME=0891f780a07c
NODE_VERSION=18.18.0
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PWD=/home/foundry
SHLVL=1
YARN_VERSION=1.22.19
Entrypoint | 2023-10-06 15:26:17 | [info] No Foundry Virtual Tabletop installation detected.
Entrypoint | 2023-10-06 15:26:17 | [info] Using FOUNDRY_RELEASE_URL to download release.
Entrypoint | 2023-10-06 15:26:17 | [info] Using CONTAINER_CACHE: /data/container_cache
Entrypoint | 2023-10-06 15:26:17 | [info] Downloading Foundry Virtual Tabletop release.
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 52.92.227.177:443...
* Connected to foundryvtt.s3.amazonaws.com (52.92.227.177) port 443
* ALPN: curl offers h2,http/1.1
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: none
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [110 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [4970 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [333 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [70 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=*.s3.amazonaws.com
*  start date: Mar 21 00:00:00 2023 GMT
*  expire date: Dec 19 23:59:59 2023 GMT
*  subjectAltName: host "foundryvtt.s3.amazonaws.com" matched cert's "*.s3.amazonaws.com"
*  issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M01
*  SSL certificate verify ok.
* using HTTP/1.1
} [5 bytes data]
> GET /releases/11.313/FoundryVTT-11.313.zip?AWSAccessKeyId=AKIA2KJE5YZ3BCQQ6DH3&Signature=YLobFu78PEHP5evcGETQQg7ag3U%3D&Expires=1696606223 HTTP/1.1
> Host: foundryvtt.s3.amazonaws.com
> User-Agent: curl/8.3.0 (felddy/foundryvtt:11.313.0)
> Accept: */*
> If-Modified-Since: Thu, 05 Oct 2023 00:35:04 GMT
> 
{ [5 bytes data]
< HTTP/1.1 304 Not Modified
< x-amz-id-2: 91b7s+Duf4OrapHZFi4vN01kJgSP9B1g6DYuZDsL0mWsHO2fDZmjqec8nAdlWmOj/tBnyhWH+ck=
< x-amz-request-id: 9Z8V31THKZFJ22DQ
< Date: Fri, 06 Oct 2023 15:26:18 GMT
< Last-Modified: Tue, 03 Oct 2023 19:34:18 GMT
< ETag: "357fe41431a88e67622bf5770c3c7fd4-42"
< x-amz-version-id: null
< Server: AmazonS3
< 
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
* Connection #0 to host foundryvtt.s3.amazonaws.com left intact
Entrypoint | 2023-10-06 15:26:17 | [info] Installing Foundry Virtual Tabletop 11.313
Entrypoint | 2023-10-06 15:26:17 | [debug] Checking mime-type of release file.
Entrypoint | 2023-10-06 15:26:17 | [debug] Found mime-type: application/vnd.microsoft.portable-executable
Entrypoint | 2023-10-06 15:26:17 | [error] The release file appears to be a Windows executable (.exe).
Entrypoint | 2023-10-06 15:26:17 | [error] Please provide the 'Linux/NodeJS' version of the release or URL.

[felddy]

That is definitely an .exe disguised as a .zip.

Entrypoint | 2023-10-06 15:26:17 | [debug] Found mime-type: application/vnd.microsoft.portable-executable

Since the modification date of the file is newer than what is in the S3 bucket it is not downloading a replacement file:

< HTTP/1.1 304 Not Modified
...
< Date: Fri, 06 Oct 2023 15:26:18 GMT
< Last-Modified: Tue, 03 Oct 2023 19:34:18 GMT

I suspect that at some point in your testing you downloaded the Windows version and renamed it to foundryvtt-11.313.zip and placed in the container_cache directory.

Check the file in your the container_cache directory to see if it has the same hash and mime type as below:

sha256sum foundryvtt-11.313.zip 
c6302200b73b67136dcbf0f0e9b79612c440f4318f322a8b1e5d5ded36138f86  foundryvtt-11.313.zip

file --mime-type --brief foundryvtt-11.313.zip
application/zip

I suspect that it does not match. Then delete foundryvtt-11.313.zip file from the container_cache directory and restart the container. The container will download the correct file and startup correctly.

[djk4346]

Attached is the log. I tried it again this morning, same error.
_foundry11_logs.txt

[fastalan]

I am having this same issue, using the download URL from Foundry, the system thinks it's a windows EXE.

[fastalan]

I figured this out, I had to go into the mounted file storage and delete the zip file from the container cache there. I think there is a bug with this container if the user puts in the Windows download link, it saves it as the zip file. I did make the mistake of using the windows url for download, the container needs an enhancement to deal with this issue.

My file system was stored here /var/docker-foundryvtt/container_cache. It will be unique to however the user set up their persistent docker storage.

[felddy]

See:

• Install Breaks when Admin provides Windows Install URL causing container to store the exe file in cache as zip file blocking further start after putting the correct Linux NODE URL. #843