netcup: the session id is not in a valid format.

[philippschuetz]

I am using lego inside the nginx/acme nixos module.
When running I get

2025/06/05 14:30:13 [INFO] no existing records, error ignored: error when sending the request: an error occurred during the action infoDnsRecords: [Status=error, StatusCode=4001, ShortMessage=Api session id in invalid format, LongMessage=The session id is not in a valid format.]

and

acme: error presenting token: netcup: failed to add TXT-Record: error when sending the request: an error occurred during the action updateDnsRecords: [Status=error, StatusCode=4001, ShortMessage=Api session id in invalid format, LongMessage=The session id is not in a valid format.]

I don't know if I made a mistake or the part of lego handling interaction with the nextcloud api might be broken.

[ldez]

Hello,

I checked the API documentation and I didn't see any changes.
The session ID is a simple string provided by the API server.

https://ccp.netcup.net/run/webservice/servers/endpoint.php#SessionObject

The session ID is obtained by calling the login endpoint and is used in the other API calls.

[HenriWahl]

Same here. Obtaining a session ID which is rejected with error code 4001 and

{'serverrequestid': 'oMZ=030dlcM5GnFQj', 'clientrequestid': '', 'action': 'updateDnsRecords', 'status': 'error', 'statuscode': 4001, 'shortmessage': 'Api session id in invalid format', 'longmessage': 'The session id is not in a valid format.', 'responsedata': ''}

[philippschuetz]

I don't know how but this has resolved for me after some time. Since then I switched to hetzner (they have a free dns console thing) as my dns provider as I've only had problems with netcup...

[HenriWahl]

I asked the Netcup support and they told me, that this is a known issue. A session ends after some seconds, which is a unwanted behavior they are about to fix. In the meantime my script logs in for every action so the problem is "solved".