Open back-lacking opened 1 month ago
Issue would get temporarily fixed if i restart the send container, but would come back after some amount of time (not sure how long).
Yeah, I'm assuming Redis is the problem here. I've seen similar problems before.
You mention you can ping, but is Redis reachable on it's port? In other words, can you open a Redis connection and run commands from the Send container? Because it looks like Redis commands are not accepted at all.
How do i send commands to Redis from the Send container? I tried using curl redis:6379
but curl doesn't exist within the container.
but curl doesn't exist within the container.
You can probably install it through apk
: apk add curl
but curl doesn't exist within the container.
You can probably install it through
apk
:apk add curl
sorry for the late response trying to use apk results in an error as permission is denied. trying to use sudo to escalate the command doesnt work as sudo also doesnt exist in the container.
docker exec -it ff-send curl redis:6379
curl: (52) Empty reply from server
got curl and sudo installed by entering the root user of container and running apk through there. this is what i get from redis.
So I'm hosting Send in my homelab but its having issues with it not properly dealing with files. I would have no problem uploading the files. I would upload my files, and then I would get a link for the download. However, clicking on that download, it would result in a page showing that the download has been expired or no longer available. I looked at the logs for the send container and it would give errors about Redis. Currently, in my homelab, I'm running Redis as a completely separate container with its own compose file that i would then link to the networks of containers that need it. Below is the log for Send, along with compose configurations. Send is able to reach the Redis container, as I can ping Redis in Send's shell.
compose files: