Elkjøp cloud config

What is the problem you are having with rclone?

I can’t make remote to elkjøp cloud. It has been working until today.

Run the command 'rclone version' and share the full output of the command.

rclone v1.71.0

I have chosen jottacloud and it fails here

Option config_type.
Select authentication type.
Choose a number from below, or type in an existing value of type string.
Press Enter for the default (standard).
/ Standard authentication.
1 | Use this if you're a normal Jottacloud user.
\ (standard)
/ Legacy authentication.
2 | This is only required for certain whitelabel versions of Jottacloud and not recommended for normal users.
\ (legacy)
/ Telia Cloud authentication.
3 | Use this if you are using Telia Cloud (Sweden).
\ (telia_se)
/ Telia Sky authentication.
4 | Use this if you are using Telia Sky (Norway).
\ (telia_no)
/ Tele2 Cloud authentication.
5 | Use this if you are using Tele2 Cloud.
\ (tele2)
/ Onlime Cloud authentication.
6 | Use this if you are using Onlime Cloud.
\ (onlime)
config_type> 2

Do you want to create a machine specific API key?

Rclone has it's own Jottacloud API KEY which works fine as long as one
only uses rclone on a single machine. When you want to use rclone with
this account on more than one machine it's recommended to create a
machine specific API key. These keys can NOT be shared between
machines.
y) Yes
n) No (default)
y/n> y

Error: failed to register device: Post "https://api.jottacloud.com/auth/v1/register?device_id=rclone-44vt04llECptGXr3FwurU": read tcp 192.168.1.195:52037->185.179.129.36:443: wsarecv: En eksisterende forbindelse blev tvangsafbrudt af en ekstern vært.

If i choose no instead of yes I get:

Option config_password.
Password (only used in setup, will not be stored)
Choose an alternative below. Press Enter for the default (n).
y) Yes, type in my own password
g) Generate random password
n) No, leave this optional password blank (default)
y/g/n> y
Enter the password:
password:
Confirm the password:
password:

2025/09/15 17:12:53 CRITICAL: Reveal failed: input too short when revealing password - is it obscured?

Which cloud storage system are you using? (eg Google Drive)

Elkjøp cloud

The rclone config contents with secrets removed.

I cant create meaningfull rclone.conf

welcome to the forum,

https://forum.rclone.org/t/jottacloud-legacy-mode-isnt-working-reveal-failed/42589

Doesn’t work sorry.

I noticed this as well. Worked fine up until today.

Attempting to create a new remote results in:
2025/09/15 18:45:10 NOTICE: Fatal error: failed to register device: Post "``https://api.jottacloud.com/auth/v1/register?device_id=rclone-tTGLLIXE1Z7wCEIjfWk4h``": read tcp [2001:2042:7566:4a00:b62e:99ff:fe94:be1b]:40356->[2a0a:cc80:0:c2a8:2::36]:443: read: connection reset by peer

contact the provider

Maybe they migrated to the standard, token based authentication, and you need to select authentication type 1 during configuration..? In the cloud service’s web gui, in Settings, and then the Security tab (probably at url /web/secure), do you have a section “Personal login token” with a “Generate” button?

You can’t make Personal login token in elkjøp.

Hello there, I’m currently having the same problem.

It was mounting perfectly fine yesterday, but today it returns the “connection reset by peer”

The status page said their API is still operational.

Hope there’s a fix soon.

The solution mentioned in this post: Using machine specific API

doesn’t work.

I already have that enable when I first mounted it from the start.

The current problem might be a new one.

Also having this problem. Can’t reconnect or anything or create new remotes.

Like the api site that handles the old way of authenticating just died for Elgiganten cloud / elkjøp cloud

You cant use Legacy on jottacloud any more either.

Elgiganten cloud / Elkjøp Cloud do have sms codes that works fine for the Desktop and mobile apps. They also got 2FA app codes, however the trick would be how to make it all work again.. sms codes might be the simplest to fix maybe?

I’m afraid us users using Elgiganten cloud / elkjøp cloud are screwed for now (hopefully not forever!) since i doubt they will bring back the legacy jottacloud authentication.

I have no clue what it would take to get this working again sadly.. But hey they fixed authentication for Telia, Tele2 etc! Basically the same right just different auth methods? :smiley:

Done that did that..
Their AI support “personnel” was very clear about that the fault is at my home network, until (when I tested on a machine outside my home) I repeated that same issue (“PR_CONNECT_RESET_ERROR“). Stopped working 16 Sept, probably at the same time their SSL certificate for [cannot mention api dot jottacloud dot com because it gets linked] expired (cannot access it through a web browser either). Same with the API url when sniffing traffic during web browser login (but it works from here, so there “is no error” at Jottacloud) that uses ‘api.jotta.cloud’ (server on the same C network).

I got their AI to acknowledge that the problem is at the Jotta-side, but still Jottacloud Public Status shows no errors on any service (specifically API):

= Jotta AI Support =

If someone ever reads here: [cannot mention api dot jottacloud dot com because it gets linked] is giving "connection reset by peer", as have happened a couple times before. Broken certificate again, maybe?

I can see you're experiencing a "connection reset by peer" error with [cannot mention api dot jottacloud dot com because it gets linked] ). This type of error can indeed be related to certificate issues, but there are several potential causes. Our API and all application endpoints use TLS/SSL encryption with an A+ rating in SSL Labs' tests, and we encrypt all data with 256-bit AES encryption during transfer. We use HTTPS and TLS 1.3 to protect data transfer, which includes strong cryptographic methods and key exchange mechanisms. To check if there are any ongoing system issues that might be causing this problem, you can visit our status page at [cannot mention it because it gets linked, but see above] to see if there are any active incidents or service disruptions. If the status page shows no issues, the problem might be on your end. Try clearing your browser cache and cookies, ensure your browser is updated to the latest version, or try accessing the API from a different network connection to rule out local connectivity issues.

besides from application logs, I tried accessing [cannot mention api dot jottacloud dot com because it gets linked]/auth/v1 through an updated Firefox, still gives me that connection reset by peer

The "Connection Not Encrypted" warning and "connection reset by peer" error you're seeing indicates a serious issue with our API endpoint's SSL/TLS configuration. This contradicts our standard security implementation. Our API and all application endpoints should be TLS/SSL only with an A+ rating on SSL Labs' tests, using 256-bit AES encryption for all data transfer. We're served 100% over HTTPS with strong cipher suites, HSTS, and Perfect Forward Secrecy fully enabled. Since you're getting an unencrypted connection warning, this appears to be a server-side configuration issue affecting the [cannot mention api dot jottacloud dot com because it gets linked]/auth/v1 endpoint specifically. The fact that Firefox shows "Not Secure" confirms the endpoint isn't properly serving HTTPS. This requires immediate technical attention from our infrastructure team, as it's a security vulnerability that shouldn't exist given our encryption standards.

The "connection reset by peer" error and SSL/TLS issues you're experiencing with our API endpoint are concerning, as they contradict our standard security implementation. Our API and all application endpoints should be TLS/SSL only with an A+ rating on SSL Labs' tests. We use 256-bit AES encryption for all data transfer and serve everything 100% over HTTPS with strong cipher suites, HSTS, and Perfect Forward Secrecy fully enabled. The "Connection Not Encrypted" warning you're seeing indicates a server-side configuration issue with the [cannot mention api dot jottacloud dot com because it gets linked]/auth/v1 endpoint specifically. This shouldn't occur given our encryption standards using HTTPS and TLS 1.3 to protect data transfer. Our status page shows no current unresolved incidents that would explain this issue. Since this appears to be an infrastructure problem affecting our API's SSL/TLS configuration, this requires immediate technical attention from our team. The fact that you're getting these errors across different browsers and seeing the "Not Secure" warning confirms this is a server-side security configuration problem that needs to be addressed at the infrastructure level.

what happened with the real support staff?

We have human support staff available through multiple channels. You can contact our support team at support@jottacloud.com or call (+47) 21 04 29 00 (Monday-Friday, 09:00-20:00). We're a close team of nearly 40 individuals working together to develop and build our product, handling almost everything ourselves. Our customer support team tries to answer all requests within a reasonable time frame. If you need to speak with a human agent about the API connection issues you've been experiencing, you can reach out through these contact methods.

If you still need any further assistance with the API connection issues or anything else, I’m here to help. Would you like to provide more details about what you’re trying to resolve so we can continue?

Yes, verified the "connection reset by peer" issue from another host (outside my home network), happens there too, so it's not limited to my network. I'm trying to set up authentication using rclone for my 'Elgiganten' branded Jottacloud service

The connection reset issue you're experiencing across multiple networks confirms this is a server-side problem with our API endpoint's SSL/TLS configuration. Our API endpoints should be TLS/SSL only with an A+ rating on SSL Labs' tests, using 256-bit AES encryption and HTTPS with TLS 1.3 for all data transfer. Regarding rclone setup: While some users do use third-party applications like rclone, we cannot provide support for any issues that may arise with these applications. The current API connection problems will prevent proper authentication setup until the SSL/TLS configuration is resolved. Since you've confirmed this affects multiple networks and is blocking your rclone authentication setup, this requires immediate infrastructure attention from our technical team.

Can you confirm that rclone authentication should work (I'm not asking for setup help for my particular application) ?

Yes, rclone authentication should work with our service. Some users do use third-party applications like rclone, though we cannot provide support for any issues that may arise with these applications. However, the current API connection issues you're experiencing with the "connection reset by peer" errors will prevent proper authentication setup until our SSL/TLS configuration problems are resolved on our end.

I don’t have time but if someone else does maybe make a proper issue/bug report here?

Good idea i´ve opened an issue on Github. rclone stopped working with Jottacloud legacy login · Issue #8852 · rclone/rclone · GitHub
I contacted the support and they say they didnt changed anything - its confiusing…
Did anyone try to use Jottacloud native with lagacy login?

Cheers

1 Like

The web which used legacy username password login is still fine.

The Jotta commandline tool, uses security token is also working fine.

The only thing not working right now that I know of is rclone legacy login for jottacloud.

rclone legacy login for jottacloud is exactly what Elgiganten cloud/Elkjøp cloud used to login.

Elgiganten cloud do have sms authentication and 2FA app authentication, i’m hoping someone can look into this and perhaps change some urls for authenticating (if it’s that easy haha!) and add a dedicated option for logging in to both Elgiganten Cloud and Elkjøp cloud.

One or 2+ more dedicated cloud logins added to rclone then too! :smiley: Like they did with Telia, Tele sky, Tele2 etc.

I think Elgiganten Cloud /Elkjøp cloud would need 2 different logins because they are in different countries i would imagine there being different authentication urls etc? Don’t know how many versions they have but i use Elgiganten Cloud the “Swedish” one.

I think the Jottacloud legacy option can be removed completely after that or is there anything else that uses it at all?

edit: Once the logins for these 2 clouds are updated one should only need to do a "rclone config reconnect" command and select the new login options that has the right login information for these 2 clouds to be back up and running right?

Maybe someone with an account can try to trace the login process of the official Elkjøp cloud (Windows) application, using Fiddler or similar, and try to grab which URLs etc it uses?

I have no idea what i’m doing but for Elgiganten cloud i got these starting the desktop application (I will try when logged out aswell, if it ever logs me out)

Sadly i cant do Elkjøp cloud the norwegian version but here is the swedish version

http://api.jottacloud.com:443
http://jfs.jottacloud.com:443
http://websocket.jottacloud.com:443
http://software.jottacloud.com:443
http://cloud.elgiganten.se:443
http://sw.jotta.cloud:443

Elkjøp cloud the norwegian version i only have this:

http://cloud.elkjop.no:443

Here are some more links for Elgiganten Cloud (Swedish version) Any of them interesting?

https://cloud.elgiganten.se/auth/realms/elgiganten/.well-known/openid-configuration
https://api.jotta.cloud/customer/v2/get_customer
https://cloud.elgiganten.se/auth/realms/elgiganten/login-actions/authenticate?session_code=
https://cloud.elgiganten.se/auth/realms/elgiganten/protocol/openid-connect/token

https://cloud.elgiganten.se/auth/realms/elgiganten/login-actions/authenticate?execution=

Great. Based on that, a wild guess is it has switched to a similar approach as current telia/tele2 auth. So maybe a small fix adding it as a new alternative with its own urls is all it takes…