Anyone else having sudden Jottacloud authentication(?) issues?

Help and Support
1

I've been using the same rclone/shell script(s) to sync to Jottacloud for years now with minimal fuss. Code below is a sample, built by the script to substitute source/backup directories and timestamps for naming the log files:

rclone sync "*/mnt/FreeNAS-Music/*" "jotta:WD6TBNAS01/" --dry-run --log-file=/mnt/WD8TBNAS03/Logs/meddle/2024-06-20_08-54-32-Jotta.txt --transfers=1 --log-level INFO --exclude-from /mnt/WD8TBNAS03/Documents/ShellScripts/rclone_exclusions.txt --delete-after

As of a few days ago two of my machines are consistently giving me some version of:

2024/06/20 08:54:42 Failed to create file system for "jotta:WD6TBNAS01/": couldn't get customer info: Get "https://api.jottacloud.com/account/v1/customer": couldn't fetch token: Post "https://id.jottacloud.com/auth/realms/jottacloud/protocol/openid-connect/token": read tcp 192.168.1.18:50790->185.179.128.44:443: read: connection reset by peer

Attempts to generate a new token work on the Jottacloud site, but attempting to use that token to "feed" rclone config reconnect jotta: results in:

config_type> 1

Option config_login_token.
Personal login token.
Generate here: https://www.jottacloud.com/web/secure
Enter a value.
config_login_token> [redacted]

Error: failed to get oauth token: Get "https://id.jottacloud.com/auth/realms/jottacloud/.well-known/openid-configuration": read tcp 192.168.1.197:49464->185.179.128.44:443: read: connection reset by peer
Usage:
  rclone config reconnect remote: [flags]

Flags:
  -h, --help   help for reconnect

Use "rclone [command] --help" for more information about a command.
Use "rclone help flags" for to see the global flags.
Use "rclone help backends" for a list of supported services.

2024/06/20 08:47:33 Fatal error: failed to get oauth token: Get "https://id.jottacloud.com/auth/realms/jottacloud/.well-known/openid-configuration": read tcp 192.168.1.197:49464->185.179.128.44:443: read: connection reset by peer

Oddly, while this has been affecting two of my three Linux boxes (one Ubuntu Server, one Raspberry Pi OS), it has yet to hit my main Linux box, running Ubuntu 22.04.4 LTS Desktop.

I've updated rclone to the latest:

clone v1.67.0
- os/version: ubuntu 22.04 (64 bit)
- os/kernel: 5.15.0-112-generic (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.22.4
- go/linking: static
- go/tags: none

I'm wondering if Jottacloud is now wanting us to use their own CLI or something. I haven't altered the scripts on my end in a very long time, so the only change(s) I can imagine being relevant are whatever regular system updates have come down the pipe.

The scripts live on a network drive, which means that every system executes identical code, which has been the case for years.

2

are the two affected machines on the same local lan/internet as the working linbox.

as a test, might copy the working config file from the main linbox to one of the affected boxes.
can use --config= so as not touch the config file on the affected linbox

3

Well, THAT'S interesting...it worked! Thank you for the suggestion!

That maybe suggests that the config files on the other boxes got corrupted...but two of them on two physically different machines at the same time? That seems unlikely.

4

welcome

agreed, maybe a network issue or one-time issue that has since passed.
can confirm by trying one of the affected boxes again, using the non-working config.

5

Even weirder:

Using the copied rclone.conf file on the Raspberry Pi worked, running the command again using the original file also worked, even though it hadn't been.

Using the copied rclone.conf on the Ubuntu Server file worked, running the command again using the original file did not work. Starting to look like something is weird on Jottacloud's end.

6

that is what i would think, based on read: connection reset by peer

7

As of this morning, it's all working normally again...at least for now!

8

I had this problem a month or so ago.

Jottacloud's support was as useful as a chocolate tea pot, blaming everything than their own service. I mean, my own server or rclone is not capable of generating the "reset by peer" error...

So I've let the system lapse and the credit card company is involved.

This was before their 20% or so notice of price rise.

9

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.