But: S3 proxy not working when set with ENV

[diminDDL]

I have setup Gokapi pretty close to what the docs say. Instead of AWS S3 I am using a self hosted garage S3 instance in another container. These are connected using docker networking, so the compose for Gokapi looks as follows:

services:
  gokapi:
    image: f0rc3/gokapi:latest
    container_name: gokapi
    networks:
      - s3-garage-net
    ports:
      - "53842:53842"
    volumes:
      - ./gokapi-data:/app/data
      - ./gokapi-config:/app/config
    restart: unless-stopped
    env_file:
      - "./.env"

networks:
  s3-garage-net:
    name: s3-garage-net
    external: true

During the setup and creation of .env I selected to enable the S3 proxying, this is confirmed in both files:

# env file
# Timezone
TZ=Europe/Berlin

# Optional S3
GOKAPI_AWS_BUCKET=gokapi-bucket
GOKAPI_AWS_REGION=garage-server-1
GOKAPI_AWS_KEY=redacted
GOKAPI_AWS_KEY_SECRET=redacted
GOKAPI_AWS_ENDPOINT=http://garage:3900
GOKAPI_AWS_PROXY_DOWNLOAD=true

# Other flags
GOKAPI_DISABLE_CORS_CHECK=true
GOKAPI_LOG_STDOUT=false

./gokapi-config/cloudconfig.yml:

aws:
    Bucket: gokapi-bucket
    Region: garage-server-1
    KeyId: redacted
    KeySecret: redacted
    Endpoint: http://garage:3900
    ProxyDownload: true

However, whenever I visit a link and start downloading a file I get redicred to http://garage:3900/gokapi-bucket/... so clearly it is not proxying correctly.

All I see in the logs is

Sat, 15 Nov 2025 11:17:17 UTC   [info] Gokapi started
Sat, 15 Nov 2025 11:17:34 UTC   [upload] test.mp4, ID Q6nqtuUo0CP94Ke, uploaded by admin (user #1)
Sat, 15 Nov 2025 11:17:45 UTC   [download] test.mp4, ID Q6nqtuUo0CP94Ke, Useragent Mozilla/5.0 (X11; Linux x86_64; rv:144.0) Gecko/20100101 Firefox/144.0

And the config json for completeness:

{
  "Authentication": {
    "Method": 0,
    "SaltAdmin": "redacted",
    "SaltFiles": "redacted",
    "Username": "admin",
    "HeaderKey": "",
    "OauthProvider": "",
    "OAuthClientId": "",
    "OAuthClientSecret": "",
    "OauthGroupScope": "",
    "OAuthRecheckInterval": 12,
    "OAuthGroups": [],
    "OnlyRegisteredUsers": false
  },
  "Port": ":53842",
  "ServerUrl": "http://example.com:53842/",
  "RedirectUrl": "https://example.com/",
  "PublicName": "Gokapi",
  "DataDir": "data",
  "DatabaseUrl": "sqlite://./data/gokapi.sqlite",
  "ConfigVersion": 22,
  "MaxFileSizeMB": 102400,
  "MaxMemory": 50,
  "ChunkSize": 45,
  "MaxParallelUploads": 3,
  "Encryption": {
    "Level": 0,
    "Cipher": null,
    "Salt": "",
    "Checksum": "",
    "ChecksumSalt": ""
  },
  "UseSsl": false,
  "PicturesAlwaysLocal": false,
  "SaveIp": false,
  "IncludeFilename": false
}

Just to be clear, uploading works perfectly and I can see the data appearing in the S3 bucket, so it can communicate with the endpoint.

[Forceu]

Hi, sorry for the very late reply! We did some changes regarding the AWS code in the latest version, does the problem still occur?

[diminDDL]

Hello, I just did a fresh deployment to test this and now when I get to the AWS step in the setup wizard and enter all the correct details I get:

Could not get CORS settings. Error NotFound: NotFound: Not Found
status code: 404, request id: , host id: 

At the same time in the docker logs it prints AWS login successful.

When I do something like change the bucket name to a non existing one it correctly returns me an error in the web browser about no bucket being found and still prints AWS login successful in the docker terminal, so it can communicate with the S3 point, just incorrectly it seems.

If I ignore the error and go through with the setup I see WARNING: AWS login not successful in the logs and it defaults to local storage silently (nothing uploaded to the bucket, and files appearing in the data directory instead).

In gokapi-config the following files are generated:
cloudconfig.yml:

aws:
    Bucket: gokapi-bucket
    Region: garage-server-1
    KeyId: redacted
    KeySecret: redacted
    Endpoint: http://garage:3900
    ProxyDownload: true

config.json:

{
  "Authentication": {
    "Method": 0,
    "SaltAdmin": "redacted",
    "SaltFiles": "redacted",
    "Username": "redacted",
    "HeaderKey": "",
    "OauthProvider": "",
    "OAuthClientId": "",
    "OAuthClientSecret": "",
    "OauthGroupScope": "",
    "OAuthRecheckInterval": 12,
    "OAuthGroups": [],
    "OnlyRegisteredUsers": false
  },
  "Port": ":53842",
  "ServerUrl": "http://127.0.0.1:53842/",
  "RedirectUrl": "https://github.com/Forceu/Gokapi/",
  "PublicName": "Gokapi",
  "DataDir": "data",
  "DatabaseUrl": "sqlite://./data/gokapi.sqlite",
  "ConfigVersion": 22,
  "MaxFileSizeMB": 102400,
  "MaxMemory": 50,
  "ChunkSize": 45,
  "MaxParallelUploads": 3,
  "Encryption": {
    "Level": 0,
    "Cipher": null,
    "Salt": "",
    "Checksum": "",
    "ChecksumSalt": ""
  },
  "UseSsl": false,
  "PicturesAlwaysLocal": false,
  "SaveIp": false,
  "IncludeFilename": false
}

[Forceu]

Okay so I did some investigation and installed Garage myself.

It seems that the error Could not get CORS settings. Error NotFound: NotFound: Not Found is triggered when no CORS settings are not set for the bucket and Garage then sends a 404, which is not according to specs.

Unfortunately I was not able to create an account for their repository, but I will send them an email later on. In b3602df I enhanced the error a bit, so that it is less generic, but as they are not returning the correct value I will probably not add a workaround for Garage.

I will investigate the proxy issue later today.

[Forceu]

The proxy issue might be fixed by #372. Can you try again with the latest docker image?

[diminDDL]

Latest f0rc3/gokapi:latest-dev image gives me Login OK, but could not check bucket CORS settings. now, so at least the message is now less cryptic. It also now actually loaded the values from my .env instead of having me enter it manually on the setup wizard.

[Forceu]

Great to hear - does proxying work as well now?

[diminDDL]

Yes, despite the error message during setup uploading and proxying works fine to the bucket! Maybe it would be worth adding a message letting the user know that it still might work even with the CORS issues?

[Forceu]

Thank you for the feedback and good to hear that it is working now :)