Good evening,
Duplicati is using the endpoint https://up.jottacloud.com/jfs whereas rclone is using https://jfs.jottacloud.com/jfs/ to upload files to Jottacloud.
The difference between those endpoints is that with rclone upload speed limits kick in (I have 44TB stored) while with Duplicati they don’t. I installed rclone and tried to upload a 2GB file - well…let’s see by when it will be finished 
Anways…does someone know why Duplicati is using this special Upload endpoint?
Hi, would you mind sharing the version you are running.
You can try configuring on your backup “Advanced Options” the throttle-upload parameter.
I am not certain at which version it was introduced, but it has been present for quite sometime, check if you have that available.
As to the difference in endpoints its worth noting that Duplicati uses jfs.jottacloud.com for downloads and up.jottacloud.com for uploads and that this backend was integrated back in 2017 and perhaps those were the endpoints then.
In any event most backends are being re-written and re-tested to remove deprecated WebClient and incorporate the more modern HttpClient and it might be an opportunity to contact Jottacloud to find out which are the more appropriate ones to use.
I’m running 2.0.7.102_canary_2024-04-03 - I can’t update to the most recent version since I’m running it inside a TrueNAS Core Jail and I tried to update mono but never made Duplicati run with it.
I’m planning to migrate to TrueNAS Scale but with Duplicati (inside Jail) and 2 bhyve VMs it’s not a click-and-run job 
Anyways: Reason why I have slow upload is because of Jottacloud, not duplicati. They throttle upload speed once you store more than 10TB and with my 44TB I’m throttled to 250kpbs (not joking!). But for some reason when uploading with Duplicati the throttling never kicked in. I had up to 200Mbps upload.
That’s why I asked my question. Since with rclone which only uses jfs.jottacloud.com for up- and Downloads the throttling kicks in and uploading larger files becomes impossible (I tried and eventually got a HTTP 420 error).
Here’s the relevant information from Jottacloud: Reduced upload speed | Jottacloud Help Center
In my opinion they are morons by advertising “unlimited storage” but already throttle upload speeds after 5TB.
Switching subscription is out of question, I can’t afford such lunatic prices (1800€/yr). For that money I can rent several dedicated server at Hetzner or OVH.
Hijacking this thread.
I also have the Jottacloud Personal subscription.
Since the change to httpClient my upload speeds went down to a quarter to previous versions.
Now I get around 1MB/s which was before 4-4.5 MB/s.
Don’t know if this is the mentioned upload speed limit from Jottacloud or s.th. else.
If it is the upload speed limit then I don’t understand it even more since if have over 50TB stored which would result in a much more lesser upload speed.
As far as I can see Duplicati is still using these two endpoint for contacting Jottacloud.
up.jottacloud.com
jfs.jottacloud.com
Can s.th. be done about it? If not, care to explain?
Correct.
That depends on where the problem is. If this is Jottacloud actively throttling connections, nothing can be done about it from Duplicati’s side.
Would you have an option to try with the previous version? Then we could see if there was really a change with the codebase. We did update to the new library, but all the calls etc that Jottacloud sees should be 100% identical with the previous version.
The upload itself from Duplicati is simply transmitting data in a single call as fast as it will go (unless you add throttle yourself). If there really is a difference between versions, it is most likely a quirk in the way Jottacloud applies throttle, and unlikely to be a fault (or fixable) in Duplicati.
Reading the speed descriptions, I agree that you should see around 0.1 Mbit/s (or 12.5KiB/s) for more than 50 TB stored.
I tried a clean docker installation of 2.1.0.108.
I can get my fullspeed upload.
It is a quirk in the way Jottacloud applies throttling since per my conversation with their support they don’t seem to be aware that it sometimes doesn’t work as intended.
If you find out what the difference between old and new version is that would be awesome!
So I did some more tests with .120 and would just for fun check out what my router shows as upload speed.
And to my surprise it showed fullspeed!
Further invastigating suggests this is an error in the old UI, which I was still using.
Changing to ngclient shows correct upload speeds.
