-
Notifications
You must be signed in to change notification settings - Fork 627
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Creating Persistent Receive Files from CLI Only #1832
Comments
Thanks for the report. Sounds like a potential bug if the folder is created on the receiving side but the files are not. Can you run the same process but with You might then see some stacktraces during the uploading of files in Receive mode that could help uncover the issue. Just be careful if you share those logs here, to not include details that might appear in the log such as the onion address (if that's secret) or private/onion auth keys. |
It may take a little time, but I will try and get some better troubleshooting info over to you. I am running the process on a raspberry pi 3B using the headless raspberry lite minimum OS. |
It seems like running as a service using systemd might be a better way to accomplish what I'm trying to do. Curious if you have or know of someone who has had success trying it that way. |
I am attempting to run onionshare.cli in a more persistent manner on a headless server. My process is as follows...
onionshare.cli --receive --public --data-dir /path/to/share
bg
disown -h %1
exit
The end result is that the server is reachable after exiting and appears to be successful sending files from the client side. On the server side, folders are created for each instance of a new upload; however the files and any messages never appear. I have confirmed that uploading works correctly after steps 1-5. Trying to figure out what I am missing. Suggestions?
The text was updated successfully, but these errors were encountered: