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.