Open kidtire opened 6 years ago
In trying to debug this I forced curl to use ipv4 (-4 option) and it seems to be working. I will look next at my ipv6 routing as that seems to be a problem on this new system.
In trying to debug this I forced curl to use ipv4 (-4 option) and it seems to be working. I will look next at my ipv6 routing as that seems to be a problem on this new system.
How did you force it? Is it possible to pass curl parameters to the dropbox-uploader script?
I just edited the curl parameters in the Dropbox uploaded script to use -4 everywhere and it works.
I just edited the curl parameters in the Dropbox uploaded script to use -4 everywhere and it works.
Okey, it doesn't work for me on two different machines...could you share your file?
I just edited the curl parameters in the Dropbox uploaded script to use -4 everywhere and it works.
Nevermind it works now after creating a new dropbox app which has access on the full dropbox
I had a previous Raspberry Pi that was working fine with dropbox_uploader.sh until the WiFi adapter failed. So I installed a new Pi3 B+ and connected it to a Dropbox app that was being used on the old Pi.
Upload worked a few times then quit working. I can use the auth token on other machines. I can download and list files on this new machine.
I modified the curl command parameters in dropbox_uploader.sh to log as per previous issues and ran with -d and got this output (token masked in output):
dropbox_uploader.sh -d upload c100k cam2 1.0 Linux pi3b 4.14.62-v7+ #1134 SMP Tue Aug 14 17:10:10 BST 2018 armv7l GNU/Linux Raspbian GNU/Linux 9 \n \l
--
The /tmp/du_resp_debug contains: HTTP/1.1 100 Continue
--
I have tried creating a new Dropbox App, creating new tokens, new directories, rebooting the wifi AP. I have not tried configuring a new Raspberry Pi.
I tried the token on other systems and it worked.
Networking on this Pi seems to be ok for all other purposes including uploading large files via ftp.