Setup with docker

[Jisagi]

Hi, I was tryting to setup gokapi with docker-compose, but wasn't able to get everything up and running. Starting with docker-compose works fine and it creates a config file, but trying to access gokapi from a different machine does not work at all. Trying to access it with curl on the machine its running on does not work (curl: (7) Failed to connect to 127.0.0.1 port 8084: Verbindungsaufbau abgelehnt).
I then tried to run everything with the provided command from the readme with docker run -it -v /home/gokapi/data:/app/data -v /home/gokapi/config:/app/config -p 8084:53842 f0rc3/gokapi:latest with the same result. Config file is the same both ways but I cannot access the sever, neither with an apache reverse proxy nor with ip:port (or on the machine itself). I also tried to run gokapi with the default ports, but same result again.

Additionally I saw, the LengthId in the config is always 0, despite me setting it in the environment. The created config will never use use my value or the default 15. This happens with both docker run... and docker-compose btw.

Am I missing something?

docker-compose.yml:

version: "3"
services:
  gokapi:
    image: f0rc3/gokapi:latest
    container_name: gokapi
    restart: unless-stopped
    environment:
      - GOKAPI_USERNAME=Jisagi
      - GOKAPI_PASSWORD=XXXXXX
      - GOKAPI_LENGTH_ID=20
    ports:
      - "8084:53842"
    volumes:
      - /home/gokapi/data:/app/data
      - /home/gokapi/config:/app/config

created config:

{
    "Port": "127.0.0.1:53842",
    "AdminName": "Jisagi",
    "AdminPassword": "XXXXXXXXXXXXXXXXX",
    "ServerUrl": "http://127.0.0.1:53842/",
    "DefaultDownloads": 1,
    "DefaultExpiry": 14,
    "DefaultPassword": "",
    "RedirectUrl": "https://github.com/Forceu/Gokapi/",
    "Sessions": {},
    "Files": {},
    "Hotlinks": {},
    "ConfigVersion": 4,
    "SaltAdmin": "zsYecQPNEbPxhInpa62nOvWrICDyVCfoDOxotOW",
    "SaltFiles": "2z8CH4B6mkE3YoVHcXLUUg1j8lcVEuNclFe6Umq9",
    "LengthId": 0,
    "DataDir": "data"
}

[Forceu]

Hi, thank you very much for your report!
The issue with the LengthId being 0 has been fixed in aae4138, but is not in the current version yet.
The problem seems to be config entry "Port": "127.0.0.1:53842", which seems to be a bug here:

Gokapi/internal/configuration/Configuration.go

Line 249 in 3ebcafb

return environment.IsTrue

(should probably return false instead of true).

As I am using podman instead of Docker (where it works with that configuration) I did not notice the problem. Can you please change "Port": "127.0.0.1:53842", to "Port": ":53842", in your config and let me know if that is working?

[Jisagi]

Using "Port": ":53842" did actually fix the problem, nice.

EDIT: Now I just have to find out, how I can tell to not use 127.0.0.1 as domain for new files :D Something like this http://127.0.0.1:53842/d?id=5J3Ng6MIurP9HErgGJPJ is the result of any file upload. Might be connected to the initial problem. Using the inside port/ip/domain will def break it both inside a docker and also behind a reverse proxy

[Forceu]

Great to hear, I will upload a fix in that case!

During the setup you were asked to provide an entry for "External Server Url", you can set the Domain there. Or you can simply edit the config line "ServerUrl": xxxx

[Jisagi]

Yes, I saw that setting in the config again the minute you posted it. I'm facing problems downloading now, but that might be because of cloudflare, since the hotlinks work just fine

[Forceu]

Hm that is interesting! What exactly is the problem? I know that there are some limitations with cloudflare (eg. no uploads bigger than 100MB, which could be solved with chunked uploading).

[Jisagi]

I was only testing my setup with files not larger than 1-2MB and I was experiencing seemingly random problems. I wasn't able to download most of the uploaded files and just got the "not valid or expired" error page. It did work sometimes with >1 possible downloads, but that might have been not ralted to the actual problem. The other problem was not being able to delete a download. I was getting a 200 by the endpoint when trying to delete a file, but it neither actually deleted the file from the data folder, not removed it from the config.

[Forceu]

Okay, that is very strange. Can you test if the problem exists in the latest-dev Docker image as well?

[Jisagi]

I tested both back to back now, and I only have the mentioned problems with :latest, but not :latest-dev, very strange indeed. My way of testing was to just setup the instance completely fresh, no config nothing, upload a single file and try to download it. This always fails when downloading the file afterwards. Then I can't even delete it. Strangely enough, latest-dev works out of the box as intended.

If you want me to test everything some more or provide you with more data, just lmk. Or just set latest master as new version ;D

[Forceu]

I could image that Cloudflare is trying to cache the files and therefore these problems were created. I will add a header to disable caching, maybe that helps. Since the last release there have been some internal changes as well, but I would be somewhat surprised if they fixed the problem. Definitely let me know if you experience them again!