search

timvisee / send

:mailbox_with_mail: Simple, private file sharing. Mirror of https://gitlab.com/timvisee/send
https://send.vis.ee
Mozilla Public License 2.0
4.36k stars 253 forks source link

Send not working on Synology #157

Open ideaalab opened 1 year ago

ideaalab commented 1 year ago

Hi, ive installed Send on a Synology DS720+ with 6GB ram. DSM 7.1.1 Docker image send:latest Ive configured a reverse proxy https://send.mydomain.com (443) -> localhost:1234 LetsEncrypt certificate for https://send.mydomain.com In docker container ive set external port 1234 to redirect to container 1443 TCP. Everything looks ok. Im able to enter the website and it displays fine. Also work with thunderbird addon. Problem is that files dont upload. They stay in 0% forever. Doesnt matter if in local or remote i can not upload the files via website or thunderbird. Ive searched all over the documentation and could not find anything. Im sure you are way aware of this problem and the possible solutions. Could you point me in the right direction? Thanks

ideaalab commented 1 year ago

Ups! Ive just found the problem I think... Looking at this issue: https://github.com/timvisee/send/issues/14 Looks like it was needed to enable the websocket for uploads. Enabled and uploading! :) ... But... when I try to download it sais "Link expired". The container has a persistant always empty folder /docker/send for the folder /uploads is this correct?

ideaalab commented 1 year ago

All morning dealing with this, and could not make it work. I think it was a problem with permissions in the upload folder. Finally went for the docker-compose to make it work. Now its running "fine", except that If i restart the containers the links are not working anymore

timvisee commented 1 year ago

Great to hear it is mostly running fine now.

Now its running "fine", except that If i restart the containers the links are not working anymore

For persistence a Redis instance is required. If you are already running a Redis instance, then Send may have trouble connecting to the Redis instance. In that case you should see errors in the Send logs.

ideaalab commented 1 year ago

I dont see any errors on redis loading:

compose-send_redis
date,stream,content
2023-05-19T08:50:40.828618846Z,stdout,1:M 19 May 2023 08:50:40.828 * Ready to accept connections

2023-05-19T08:50:40.828561763Z,stdout,1:M 19 May 2023 08:50:40.828 * DB loaded from disk: 0.000 seconds

2023-05-19T08:50:40.828525336Z,stdout,"1:M 19 May 2023 08:50:40.828 * Done loading RDB, keys loaded: 3, keys expired: 0.
"
2023-05-19T08:50:40.828478320Z,stdout,1:M 19 May 2023 08:50:40.828 * RDB memory usage when created 0.95 Mb

2023-05-19T08:50:40.828446599Z,stdout,1:M 19 May 2023 08:50:40.828 * RDB age 47 seconds

2023-05-19T08:50:40.828405195Z,stdout,1:M 19 May 2023 08:50:40.828 * Loading RDB produced by version 7.0.11

2023-05-19T08:50:40.828297720Z,stdout,"1:M 19 May 2023 08:50:40.827 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
"
2023-05-19T08:50:40.828244797Z,stdout,1:M 19 May 2023 08:50:40.827 # Server initialized

2023-05-19T08:50:40.827877527Z,stdout,1:M 19 May 2023 08:50:40.827 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.

2023-05-19T08:50:40.827721666Z,stdout,"1:M 19 May 2023 08:50:40.827 * Running mode=standalone, port=6379.
"
2023-05-19T08:50:40.827002930Z,stdout,1:M 19 May 2023 08:50:40.826 * monotonic clock: POSIX clock_gettime

2023-05-19T08:50:40.826935395Z,stdout,"1:C 19 May 2023 08:50:40.826 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
"
2023-05-19T08:50:40.826848210Z,stdout,"1:C 19 May 2023 08:50:40.826 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started
"
2023-05-19T08:50:40.826270423Z,stdout,1:C 19 May 2023 08:50:40.826 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo

After restarting compose in Send log there is nothing but this when I access the send page: 2023-05-19T08:51:06.312519137Z,stdout,"[ 'https://send.example.com', 'wss://send.example.com' ]

Download links are still valid, and they show on my "previous uploads" in the Send page, but when clicking on download the page reloads but the file is not downloaded.