I'm using docker. When I run this:

sudo docker run -v gokapi-data:/app/data -v gokapi-config:/app/config -p 53842:53842 f0rc3/gokapi:latest

it gives me the setup & and I can walk through it. However, when it asks me to pick the storage location, Cloud isn't an option because I didn't build it with that?

I was able to run this instead to build it with the cloud part set up:

sudo docker run -d --restart always -it -v gokapi-data:/app/data -v gokapi-config:/app/config -p 53842:53842
-e GOKAPI_AWS_BUCKET={hiddenBucketName}
-e GOKAPI_AWS_REGION=us-west-2
-e GOKAPI_AWS_KEY={hiddenKey}
-e GOKAPI_AWS_KEY_SECRET={hiddenSecretKey}
f0rc3/gokapi:latest

That boots everything up and lets me upload files. The files go into my S3 bucket. But, I can't download them. I set the CORS value to:

[ { "AllowedHeaders": [ "*" ], "AllowedMethods": [ "GET", "PUT", "POST", "DELETE", "HEAD" ], "AllowedOrigins": [ "https://{domain}", "https://{domain}/*" ], "ExposeHeaders": [] } ]

But when I try to download, the button just turns dark grey and nothing happens.

Is there a way to configure this w/o having direct lan access? I only have SSH access to my droplet and it's asking me to visit the lan IP of the machine. Attempting to visit the WAN IP gives me a "this site is in maintenance mode" message. Any help would be greatly appreciated.

Hi,

Testing with nginx (swag with letsencrypt from linuxserver.io) I always get 400 Bad Request. Accessing via IP it works as it should but of course I cant share on the internet.

My setup is: No SSL Public facing URL - is my URL used by Nginx Redirection is above URL/admin Authentication is username and password Storage - local storage + As above Encryption - level 0

I have other apps behind nginx (like 20+ of them) - they all work fine.

I am not sure what the issues is. limited logs from docker (xxx are my changes):

██████  ██████  ██  ██  █████  ██████  ██  ██       ██    ██ ██  ██  ██   ██ ██   ██ ██  ██  ███ ██  ██ █████   ███████ ██████  ██  ██  ██ ██  ██ ██  ██  ██   ██ ██      ██   ██████   ██████  ██  ██ ██  ██ ██  ██                                        Gokapi v1.5.2 starting Please open http://xxx.xxx.xxx.xxx:53842/setup to setup Gokapi. Saving new files to local storage Binding webserver to :53842 Webserver can be accessed at https://xxx.xxxxxx.xxx/admin Press CTRL+C to stop Gokapi

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"
}

Hello.

Storing files and sessions inside config is not great idea for several reasons:

1. It's not secure, because read-only access for configs in Linux is a common practice.
2. It's not good for performance beacuse full rewrite required.
3. It's, in general, bad practice.

What do you think about adding new backend. Sqlite will be the simplest one, which can be used for existing configs, mostly, inplace (for example, another .sqlite file in config folder). Also supporting sqlite may lead to supporting normal DBs like Postrgres or MariaDB.

Benefits:

1. May increase performance and stability with low-end devices with bad IO which is may relevant for this application.
2. May increase performance for instances with a lot of files, because config rewrite is not required (adding 1 file to 10000 existing is not a problem)
3. State isolation is a good technique in general. Many self-hosted application can store almost full state in DB, except user data. And one DB backup script is enough for server backup, but another procedure is required for gokapi

What do you think? I also can help with this if you wish.

Regards.

Hi, I'm trying run gokapi in docker on Synology NAS and neither after maybe tens attempts i'm don't have any success. Can you help me with settings please? I'm runnig many other containers but with this....i don't know.

My container minimal settings: { "cap_add" : null, "cap_drop" : null, "cmd" : "/app/gokapi", "cpu_priority" : 50, "devices" : null, "enable_publish_all_ports" : false, "enable_restart_policy" : false, "enabled" : true, "env_variables" : [ { "key" : "PATH", "value" : "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" }, { "key" : "GOKAPI_PASSWORD", "value" : "xxxxxxxxxxxxxxxxxx" }, { "key" : "GOKAPI_USERNAME", "value" : "myName" } ], "exporting" : false, "id" : "2379bc3ac01d530858f539bc131313d61cf54dbe0ea20b90694e015ad338875f", "image" : "f0rc3/gokapi:latest", "is_ddsm" : false, "is_package" : false, "links" : [], "memory_limit" : 0, "name" : "f0rc3-gokapi1", "network" : [ { "driver" : "bridge", "name" : "bridge" } ], "network_mode" : "bridge", "port_bindings" : [ { "container_port" : 53842, "host_port" : 0, "type" : "tcp" } ], "privileged" : false, "shortcut" : { "enable_shortcut" : false }, "use_host_network" : false, "volume_bindings" : [] }

Result:

Sorry for my bad eglish.

Hello,

I'm hoping I can get some support, but I'm running this Unraid template - so I can't be certain my issue can be solved here. The template is essentially Gokapi v1.6.1 using docker-compose.

My configuration used to work, until a recent update - not sure which. Now, I cannot start the container, and am left with error reading config.json: unexpected end of JSON input in the log. I deleted my config.json and started over using the newish onboarding wizard (which is really nice btw), but I'm still getting this error.

I don't see anything wrong with the configuration, but maybe I'm missing something.

config.json:

{
  "Authentication": {
    "Method": 1,
    "SaltAdmin": "<redacted>",
    "SaltFiles": "<redacted>",
    "Username": "",
    "Password": "",
    "HeaderKey": "",
    "OauthProvider": "https://authentik.domain.tld/application/o/gokapi/",
    "OAuthClientId": "<redacted>",
    "OAuthClientSecret": "<redacted>",
    "HeaderUsers": null,
    "OauthUsers": null
  },
  "Port": ":53842",
  "ServerUrl": "https://g.domain2.tld",
  "RedirectUrl": "https://domain2.tld",
  "ConfigVersion": 12,
  "LengthId": 10,
  "DataDir": "data",
  "MaxMemory": 40,
  "UseSsl": false,
  "MaxFileSizeMB": 102400,
  "Encryption": {
    "Level": 0,
    "Cipher": null,
    "Salt": "",
    "Checksum": "",
    "ChecksumSalt": ""
  },
  "PicturesAlwaysLocal": true
}

Thank you for any help you can provide.

Hi. I just ran gokapi on a Debian 10 box with apache already installed and it works fine when using the internal IP address to connect, however, when I use my domain to try and connect to it, it changes my connection from being an HTTP connection to an HTTPS connection and FireFox throws the error: SSL_ERROR_RX_RECORD_TOO_LONG I'm not sure whats wrong here, as it runs perfectly fine when using my internal IP, however, this defeats the purpose of using it to share files with others. All of the settings are default except it is not bound only to localhost and I'm not using a reverse proxy. Port 53842 is port forwarded.

Hi, would it be possible to add a fourth button to be able to copy the direct link to a non image file? This would make it easier to download files in a console. I currently create the link manually with https://host.tld/downloadFile?id=<ID>.

It does not necessarily have to be another button, but a possibility in general to copy the above link in the frontend. On that note, you could also add DownloadUrl to the json response when uploading via the api, so custom upload scripts can use it as well.

When trying to use a hotlink URL after the file has been deleted from the server (max download 1), it shows a page of this:

If you use the regular file URL for the same file, it redirects to /error with "Sorry, this file cannot be found. Either the link has expired or it has been downloaded already".

It would be quite helpful if I could see the number of downloads for files without download limits. Since just putting the number of downloads into the "Downloads remaining" column wouldn't make much sense, I was thinking that a sensable change would be to rename the column to something like "Downloads/Limit" and change each row to "x/limit" for files with download restrictions or "x/Unlimited" for files without restrictions. Thank you!

Here's a humble suggestion to improve the design of uploaded items.

1. Not enough space for full filename
2. Slight overlap between progress bar and filename
3. Size units can stay in MB until file size actually reaches 1GB

Hi, I decided to configure Gokapi to use Cloudflare R2, with auto set as the S3 region. When the file is successfully uploaded to the Gokapi server, the server returns an error (504 Gateway Timeout as I used Nginx).

Looking at the logs, I see the following warning, in which I have configured my server with the correct access key and secret access key. Requesting a new one from Cloudflare doesn't fix the issue as well:

caused by: SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your secret access key and signing method.

instead of limiting the access to certain users, restrict the access to certain groups would be helpful. perhaps using the non-standard? groups claim.

https://github.com/Forceu/Gokapi/blob/49f11e94dab4762bb16d13762a67d43c858ace67/internal/webserver/authentication/Authentication.go#L78

Hello,

it would be very nice to have the possibilites to add new user that can access the admin board

And : remove a user, edit user passwords could be cool too

Thanks !