Just tried.
I deleted the bucket: OK.
I created a new one: OK.
I tried to upload a new one: KO
The messages on the bottom says:
āImpossible to start the transferā.
I created an empty file directly on the target server (i.e. to tardigrade satellite): it works!
I tried to edit its content: it works too! The file has been updated on Tardigrade and I am able to see my modifications (the size has changed and I was able to see the content).
[EDIT] OK, Iām feeling very stupidā¦ I actually used a different API Key (please donāt kick me). I thought I used the same because I requested an API Key on fz.tardigrade.io with the same email addressā¦ First characters were the same and so I thought it was actually the same (since the site is for testing purpose, I thought it was the same API Key for everybodyā¦).
I can see with uplink the bucket I created with FileZilla.
But I still have a problem to upload files with FileZilla.
@deathlessdd
On first pic there is a E3-1265L v2 wiht hypervisore esxi and machine 2012 r2, as on the sec pic there is CPU i5-8350 CPU, I am not sure what is using the CPU so much, maybe encryption?
So yeah your second one is identical to my laptop, CPU usage I mean im using a i5 7200U The encryption process is much dependent on cpu power, on my high end cpu it only uses 3.2% uploading 10 files at the same time.
Iām not sure encryption is the problem Iām seeing.
I have an old but more than capable dual quad-core Xeon Mac Pro and CPU usage barely goes up when Iām uploading files.
No idea what it is thatās stalling my transfers.
I tried many random ports using http://portquiz.net/ and they are all open so far.
My theoretical upload bandwidth is 20mbps.
I have not tried again (will do tonight) however it seems that the limiting factor of the first attempt was node availability.
Uploads keep getting stuck.
Small files like 100 MB upload ok. 1.5 GB file keeps getting stuck. Router monitor shows no upload traffic anymore after a while.
So, finally today had time to do a proper test on this:
The onboarding page is now responsive, thanks @super3 and team!
The full onboarding process is pretty straightforward, enter e-mail, get credentials, follow video and you should be all set.
There are issues on larger files as others mentioned, it gets better with multiple transfers set to 10 as advised but needs some improvements. Small files however are fine.
Suggestions:
I would like to have received my API key in my e-mail or a link where I could check it again. This would be useful for users (like me) that have found about this when browsing on their phone.
The API token page feels a bit empty, not that it impacts functionality but if you could provide a written quickstart as well would help.
I have multiple transfers set to 10. A 700 MB file just went through. Another one didnāt make it and just restarted upload. The 1.5 GB still gets stuck on its way up.