• Joined on 2025-07-20
michael commented on issue dutchcoders/transfer.sh#133 2026-01-19 18:29:07 +00:00
Error while using Storj as provider

@stefanbenten commented on GitHub:

@driftywinds basedir is not used at all for the storj storage provider, only when using local storage. Could you paste your entire docker run command here,…

michael commented on issue dutchcoders/transfer.sh#133 2026-01-19 18:29:07 +00:00
Error while using Storj as provider

@stefanbenten commented on GitHub:

@driftywinds I did not had time to look into this. Will get to it today 🙏

michael commented on issue dutchcoders/transfer.sh#135 2026-01-19 18:29:07 +00:00
Dead v2 onion address

@JacksonChen666 commented on GitHub:

@aspacca you should close this issue by adding the words resolves #446 to the commit message when committing the removal of the onion address

(github…

michael commented on issue dutchcoders/transfer.sh#133 2026-01-19 18:29:07 +00:00
Error while using Storj as provider

@stefanbenten commented on GitHub:

@driftywinds After going down the rabbit hole i have found out its actually a dependency that the Storj provider uses itself and thus is not easy able to…

michael commented on issue dutchcoders/transfer.sh#135 2026-01-19 18:29:07 +00:00
Dead v2 onion address

@paolafrancesca commented on GitHub:

@stefanbenten let's delete it: I indeed didn't notice it when I refactored the frontend to use custom domain for self hosting

michael commented on issue dutchcoders/transfer.sh#135 2026-01-19 18:29:07 +00:00
Dead v2 onion address

@stefanbenten commented on GitHub:

@JacksonChen666 Thanks for bringing it up! I did notice that as well recently.

@aspacca I would be in favor of removing it for the time being.

michael commented on issue dutchcoders/transfer.sh#134 2026-01-19 18:29:07 +00:00
Is there any kind of documentation to set this up with docker other than the README?

@driftywinds commented on GitHub:

@aspacca My bad, here is the command I use to deploy the container -

sudo docker run --publish 8080:8080 dutchcoders/transfer.sh:latest --provider storj…
michael commented on issue dutchcoders/transfer.sh#134 2026-01-19 18:29:07 +00:00
Is there any kind of documentation to set this up with docker other than the README?

@paolafrancesca commented on GitHub:

@driftywinds this doesnàt seem related to docker

also, could please share the params you use to launch transfer.sh and please, do not attacch screenshot…

michael commented on issue dutchcoders/transfer.sh#134 2026-01-19 18:29:07 +00:00
Is there any kind of documentation to set this up with docker other than the README?

@driftywinds commented on GitHub:

@driftywinds do you have any specific issue?

starting from fixing your setup we can come out with better documentation

EDIT: - Forgot to mention I am…

michael commented on issue dutchcoders/transfer.sh#134 2026-01-19 18:29:07 +00:00
Is there any kind of documentation to set this up with docker other than the README?

@driftywinds commented on GitHub:

@driftywinds this doesnàt seem related to docker

also, could please share the params you use to launch transfer.sh and please, do not attacch…

michael commented on issue dutchcoders/transfer.sh#134 2026-01-19 18:29:07 +00:00
Is there any kind of documentation to set this up with docker other than the README?

@paolafrancesca commented on GitHub:

@driftywinds do you have any specific issue?

starting from fixing your setup we can come out with better documentation

michael commented on issue dutchcoders/transfer.sh#133 2026-01-19 18:29:07 +00:00
Error while using Storj as provider

@stefanbenten commented on GitHub:

@aspacca I am looking into this now and possibly found a workaround.

michael commented on issue dutchcoders/transfer.sh#133 2026-01-19 18:29:07 +00:00
Error while using Storj as provider

@paolafrancesca commented on GitHub:

@stefanbenten what's the dependency?

I would like to understand if we have a workaround before using alpine as base image

michael commented on issue dutchcoders/transfer.sh#134 2026-01-19 18:29:07 +00:00
Is there any kind of documentation to set this up with docker other than the README?

@stefanbenten commented on GitHub:

It looks like you have some sort of local DNS problem. Also why do you start it with sudo ?

michael commented on issue dutchcoders/transfer.sh#134 2026-01-19 18:29:07 +00:00
Is there any kind of documentation to set this up with docker other than the README?

@stefanbenten commented on GitHub:

Ok it sounds like your user is not part of the docker group then. Its always preferred to run with as few priviliges as possible :)

This however isnt the…

michael commented on issue dutchcoders/transfer.sh#134 2026-01-19 18:29:07 +00:00
Is there any kind of documentation to set this up with docker other than the README?

@driftywinds commented on GitHub:

Ok it sounds like your user is not part of the docker group then. Its always preferred to run with as few priviliges as possible :)

This however isnt…

michael commented on issue dutchcoders/transfer.sh#134 2026-01-19 18:29:07 +00:00
Is there any kind of documentation to set this up with docker other than the README?

@driftywinds commented on GitHub:

It looks like you have some sort of local DNS problem. Also why do you start it with sudo ?

Oh I didn't know I was not supposed to use sudo, it has…

michael commented on issue dutchcoders/transfer.sh#134 2026-01-19 18:29:07 +00:00
Is there any kind of documentation to set this up with docker other than the README?

@stefanbenten commented on GitHub:

The Storj Servers are not the problem. Its the DNS lookup of the container that fails. I do not have the time to test the docker image myself in the next few…

michael commented on issue usnistgov/macos_security#65 2026-01-19 18:29:07 +00:00
ScreenSaver

@vaughnhart commented on GitHub:

taking it all back... works now with the latest update.

michael commented on issue dutchcoders/transfer.sh#134 2026-01-19 18:29:07 +00:00
Is there any kind of documentation to set this up with docker other than the README?

@driftywinds commented on GitHub:

The Storj Servers are not the problem. Its the DNS lookup of the container that fails. I do not have the time to test the docker image myself in the next few…