Error while getting DNS Record info: The session id is not in a valid format. about dynamic-dns-netcup-api HOT 5 CLOSED

This should now be fixed in the latest version of the script.

from dynamic-dns-netcup-api.

Hi Lars,

i got the same error message but in my case it seems that it only happens after (at least) one connection retry:

[2023/08/31 12:04:03 +0000][NOTICE] =============================================
[2023/08/31 12:04:03 +0000][NOTICE] Running dynamic DNS client for netcup 4.0
[2023/08/31 12:04:03 +0000][NOTICE] This script is not affiliated with netcup.
[2023/08/31 12:04:03 +0000][NOTICE] =============================================

[2023/08/31 12:04:03 +0000][NOTICE] Getting IPv4 address from API.
[2023/08/31 12:04:04 +0000][NOTICE] Logging into netcup CCP DNS API.
[2023/08/31 12:04:08 +0000][NOTICE] Logged in successfully!
[2023/08/31 12:04:08 +0000][NOTICE] Beginning work on domain "domain.de"
[2023/08/31 12:04:08 +0000][NOTICE] Getting Domain info for "domain.de".
[2023/08/31 12:04:38 +0000][WARNING] cURL Error while accessing https://ccp.netcup.net/run/webservice/servers/endpoint.php?JSON: (28) Operation timed out after 30001 milliseconds with 0 bytes received - Retrying in 30 seconds. (Try 1 / 3)
[2023/08/31 12:05:08 +0000][WARNING] Retrying now.
[2023/08/31 12:05:11 +0000][ERROR] Error while getting DNS Zone info: The session id is not in a valid format. Exiting.

I have checked a few times and it always fails if it has to retry.

For me it fails more than 50% of the time.

from dynamic-dns-netcup-api.

@M1scer At the time you commented this, there was an ongoing issue with the CCP due to incoming DDoS attacks. This should be resolved now, do you still see this issue?

from dynamic-dns-netcup-api.

Hi Lars,

I still see this issue. Currently multiple times a day. The script runs every 15 minutes. Maybe too often. My IP address at Telekom apparently only changes when I reconnect.

It seems to me that I am the only one with this problem. Is there a better solution since your last update here to set a DNS record with my public IP address?

from dynamic-dns-netcup-api.

This is caused by an API level issue (sessions are expiring too early). It is currently being looked into at netcup and depending on how soon a fix will be deployed, as well as my personal time constraints, I may or may not build a workaround.

from dynamic-dns-netcup-api.