Yeah they are basically all the same i thought aswell, whitelabels of Jottacloud.
Sounds great if fixed and added as a new Elgiganten Cloud login, all one would have to do to get the old stuff back is a “rclone config reconnect” command and choosing the new login method right?
I hope it fixes it. Now someone with Elkjøp cloud needs to find those urls but one could maybe guess them almost?
perfect dont forget LetsGoCloud another White Label of Jotta letsgo.jotta.cloudb
I did. Elkjøp refers everything to Jottacloud, and pretty much wished me “good luck with that” when I explained the issue to them.
I emailed Jottaclouds support more than ten days ago and never received any reply.
Thank you so much for the fix, @knex666. The beta fix seems to work, though not entirely for my purpose. I use Duplicati to make a backup to Elkjøp Cloud using rclone. Duplicati needs a local remote, which I’ve had created that worked just fine up until their API changes.
The connection test in Duplicati passes, but when accessing/reading/writing files using the local remote it times out all the time and I have the timeout set to 5 min which should be plenty of time.
I cannot write this off yet as a bug in Duplicati, since it worked before. Is there any limitation in the new API? Perhaps prohibiting parallell access to files since I know Duplicati tries to access more than one file simultaneously during backup and restoration.
Hey, I am running a docker of duplicati and a docker of rclone serving Jottacloud as webdav to duplicati which works fine and can be used for other stuff too. Maybe a workaround?
probs goes out to @albertony he´s the one who build the fix.
which exact version works ?
In both Linux (Ubuntu desktop) and with windows, I get “Error: failed to get oauth token: EOF” when running the rclone authorize "jottacloud" “givenhashfromconfig” command.
Tried the latest commit (1 oct, 6805da679) and the one before (27 sep, c6cb9f308)
The remote configuration flow with this option:
Use web browser to automatically authenticate rclone with remote?
* Say Y if the machine running rclone has a web browser you can use
* Say N if running rclone on a (remote) machine without web browser access
If not sure try Y. If Y failed, try N.
y) Yes (default)
n) No
y/n> n
combined with
rclone authorize "jottacloud" "…"
Is not supported by the Jottacloud backend. This was reported in the issue as well, where there are some more details.
If you can select y above, and use a web browser, then that should work.
For headless machines, where you don’t have a web browser to use, the workaround is to run the config process on a different machine, where you have a web browser, and then copy the resulting configuration file to the headless machine. There are some general documentation for this in the Remote Setup page.
Thanks, tested that earlier today, and it worked (configured on a Linux desktop machine, which didn’t open the browser url, but gave the localhost-one to paste in for authentication). Was not sure if transferring the config details to another machine would work, but it did (not as the old config with ‘machine specific API key’ previously needed for accessing the same resource on multiple machines). Have to update my guide about this (Jottacloud as S3 storage for xcp-ng) when I get the time to do so.
The pull request has just been merged, so the changes are now included in the official betas (rclone-beta-latest-… etc in beta.rclone.org).
@albertony Was there ever a way to be able to use both the rclone mount and Elgiganten cloud desktop app at the same time?
I’m glad the mount works with the beta fixes! But it’s a shame one can’t run both at the same time, i kinda need to. It’s a weird issue i can’t wrap my head around.
I don't know. I haven't used any of the whitelabels for years. But I'm very curious myself: Did it ever work, to have, on the same machine, either multiple rclone remotes, or one rclone remote plus the official desktop app, when using:
I'm assuming yes on 1, due to the fact that existing users of Elgiganten and Elkjøp mentioned it when trying the beta migrating them to the traditional oauth authentication after legacy authentication stopped working.
Anyone have a definitive answer on 1 and/or 2?
perhaps they do not allow two logins/sessions at the same time or perhaps from the same ip address.
as a test, might use a different public ipaddress for rclone using a vpn + proxy server
1. Yes it did until they changed this login method.
Can’t anything be changed with the login to kinda make it “unique”, like someone in above commented had this: https://api.jottacloud.com/auth/v1/register?device_id=rclone-tTGLLIXE1Z7wCEIjfWk4h
What if one just changed to this example? https://api.jottacloud.com/auth/v2/register?device_id=rclone-tTGLLIXE1Z7wCEIjfWk4h
Does it make sense? Or is this probably not why both the app and rclone can’t run together?
edit: But this is apparently for Jottacloud, but maybe the rclone and app for Elgiganten has the same id or something?
An endpoint like that is not called anymore, that was only done for the legacy authentication.
Elgiganten / Elkjop allows connections from multiple devices on the same public IP, but you cannot use the same rclone config on multiple machines (this is the same as with the old setup question “Do you want to create a machine specific API key?”, where we had to select “yes” to avoid problems).
For a setup that works on multiple machines running rclone, and with others running the desktop client (never a problem), rclone has to be configured with a unique token for each machine (or even for every remote on the same machine). On a machine without a web browser (Ubuntu Server or something similar) select “N” on “Use web browser to automatically authenticate rclone with remote?”, then do the authentication on one with a browser (no need to save the config, just do the authentication and copy the token to the machine that needs it, then break out of the configuration on the machine creating the token).
This is the way around “Error: not supported by this backend” when following the instructions to use another computer to authorize the client with ‘rclone authorize "jottacloud" "eyJjb….’
Also, I had problems that my token was not renewed on the machine serving s3 for xcp-ng, so I added a crontab entry to keep my remote (named “s3”) alive:
*/15 * * * * /usr/bin/rclone about s3:
Hope this messy explanation helps someone 
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.