Connection aborted - local problem or changes in API?

[Kucharskov]

Hello there!
Im using your python client for ages and today i lost all my readings. So i tried old-fasion way and restart service with proxy, but i got connection error:

[2026-01-02 21:23:27:INFO] Starting Carelink Client Proxy (version 1.2)
[2026-01-02 21:23:27:INFO] _read_token_file()
[2026-01-02 21:23:27:INFO] _get_access_token_payload()
[2026-01-02 21:23:27:INFO] _get_config()
[2026-01-02 21:23:28:INFO] _get_user()
[2026-01-02 21:23:28:ERROR] 'role'
[2026-01-02 21:23:28:INFO] _do_refresh()
[2026-01-02 21:23:28:ERROR] ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))
[2026-01-02 21:23:28:INFO] _read_token_file()
[2026-01-02 21:23:28:INFO] _get_access_token_payload()
[2026-01-02 21:23:28:INFO] _get_config()
[2026-01-02 21:23:29:INFO] _get_user()
[2026-01-02 21:23:29:ERROR] 'role'
[2026-01-02 21:23:29:INFO] _do_refresh()
[2026-01-02 21:23:29:ERROR] ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))
[2026-01-02 21:23:29:ERROR] ERROR: unable to initialize

So i tought about reissuing valid token, then i got this:

 python3 carelink_carepartner_api_login.py
performing login...
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/dist-packages/urllib3/connectionpool.py", line 787, in urlopen
    response = self._make_request(
               ^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/urllib3/connectionpool.py", line 488, in _make_request
    raise new_e
  File "/usr/local/lib/python3.11/dist-packages/urllib3/connectionpool.py", line 464, in _make_request
    self._validate_conn(conn)
  File "/usr/local/lib/python3.11/dist-packages/urllib3/connectionpool.py", line 1093, in _validate_conn
    conn.connect()
  File "/usr/local/lib/python3.11/dist-packages/urllib3/connection.py", line 796, in connect
    sock_and_verified = _ssl_wrap_socket_and_match_hostname(
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/urllib3/connection.py", line 975, in _ssl_wrap_socket_and_match_hostname
    ssl_sock = ssl_wrap_socket(
               ^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/urllib3/util/ssl_.py", line 483, in ssl_wrap_socket
    ssl_sock = _ssl_wrap_socket_impl(sock, context, tls_in_tls, server_hostname)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/urllib3/util/ssl_.py", line 527, in _ssl_wrap_socket_impl
    return ssl_context.wrap_socket(sock, server_hostname=server_hostname)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/ssl.py", line 517, in wrap_socket
    return self.sslsocket_class._create(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/ssl.py", line 1075, in _create
    self.do_handshake()
  File "/usr/lib/python3.11/ssl.py", line 1346, in do_handshake
    self._sslobj.do_handshake()
ConnectionResetError: [Errno 104] Connection reset by peer
... 

ERROR trucated but traceback goes up to main(args.us) and token_data = do_login(endpoint_config) with code 104.

Do you have the same problem? Maybe its local problem with Medtronic? I tried carelink_carepartner_api_login.py from my PC, my VM, my Raspberry Pi but even from my VPS in other country and all of them have issue with getting proper token.

Regards!

[code-with-abe]

Same here, was working just fine till yesterday, wondering if Medtronic did something

[m0rt4l1n]

Hi Ive been looking into this my current findings are here: NightscoutFoundation/xDrip#4318

[m0rt4l1n]

I am trying to get it running but the auth has been changed quite a bit. I am going with the xdrip companion app mode for now until a better solution is found but will investigate further

[ondrej1024]

Yes, things are definitely broken now. Looks like Medronic has changed the auth workflow.

[m0rt4l1n]

Small update: I've found a solution and locally it seems to work. I am now implementing a complete fix in my fork for y'all to try

[m0rt4l1n]

Work in progress but authentication should work: #35

[code-with-abe]

Small update: I've found a solution and locally it seems to work. I am now implementing a complete fix in my fork for y'all to try

Cool, thanks for working on this! the logindata.json is getting created but looks like the downstream data extractor script carelink_client2_cli.py is failing on mag-identifier
[2026-01-02 18:25:50:ERROR] 'mag-identifier'
[2026-01-02 18:25:50:ERROR] ERROR: unable to initialize
Should we tweak that script too?

[m0rt4l1n]

Yes, I fixed that. It should work all now. Please try it out if it works for you all too!

[ondrej1024]

Thanks @m0rt4l1n
Looks promising. I will give this a try tomorrow (it's gotten bit late right now)

[code-with-abe]

Small update: I've found a solution and locally it seems to work. I am now implementing a complete fix in my fork for y'all to try

Cool, thanks for working on this! the logindata.json is getting created but looks like the downstream data extractor script carelink_client2_cli.py is failing on mag-identifier [2026-01-02 18:25:50:ERROR] 'mag-identifier' [2026-01-02 18:25:50:ERROR] ERROR: unable to initialize Should we tweak that script too?

Yes, I fixed that. It should work all now. Please try it out if it works for you all too!

Yup it works now!! thanks!!

[ondrej1024]

I checked PR #35 and carelink_carepartner_api_login.py works fine here. I have carelink_client2_proxy.py running now with the new logindata.json and will have to wait until it refreshes the access token in 2 hours to see if that works also.

I noticed the the logindata.json now has a new key id_token which contain all your personal data. But this doesn't seem to be used during the authorization process. I wonder if this has to be handled somehow.

Anyway, I merged the PR into the branch auth_fix so we can test it thoroughly before doing a new release.

Big thanks to @m0rt4l1n for this highly appreciated contribution.