mirror of
https://github.com/qdm12/ddns-updater.git
synced 2026-03-31 06:24:01 -04:00
Bug: Don Dominio simple-api.dondominio.net connection reset by peer
#313
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @madmalkav on GitHub (Sep 27, 2023).
Is this urgent: No
DNS provider(s) you use: Don Dominio
Program version: Running version v2.5.0 built on 2023-06-07T09:11:38Z (commit
a6f72d9)What are you using to run the container: docker-compose image provided by TrueNAS Scale
I'm not sure the petition is being done at the correct address, my logs shows https://simple-api.dondominio.net but on their documentation they use https://dondns.dondominio.com/plain/ (for plain answer) https://dondns.dondominio.com/json/ (for json answer) or https://dondns.dondominio.com/xml/ (for xml answer)
Logs:
Configuration file (remove your credentials!):
Host OS:
Truenas Scale (Linux)
@qdm12 commented on GitHub (Jan 18, 2024):
Good point, but:
/jsonpath suffix (different API documentation page)I could change it to use https://dondominio.dev/en/dondns/docs/api/#usage as you mentioned, but to save me the ~hour of work, the error
ERROR Post "https://simple-api.dondominio.net": read tcp 172.16.0.94:56986->37.152.88.150:443: read: connection reset by peeryou get seems to be a low level networking problem instead of a bad request sent 🤔 Are you still getting it now??@qdm12 commented on GitHub (Jan 18, 2024):
Email sent to their support:
I'll update the code to work with the API described in https://dondominio.dev/en/api/docs/api/
@qdm12 commented on GitHub (Jan 18, 2024):
Actually I just received a response, can you try checking with dondominio's support why this is as such?
@madmalkav commented on GitHub (Jan 18, 2024):
Sorry, I’m no longer using this software and outta home. I can reinstall and test when I get back to home, but that will be some weeks for now
@madmalkav commented on GitHub (Jan 19, 2024):
Let’s shameless mention @mateusan while I’m not back to see if he, as the author of the original official DonDominio client, can provide some clue
@mateusan commented on GitHub (Jan 19, 2024):
endpoint: https://dondns.dondominio.com
documentation: https://dondominio.dev/en/dondns/docs/api/
@qdm12 commented on GitHub (Jan 19, 2024):
Ok so the current endpoint and API calls are no longer valid I guess then...
@qdm12 commented on GitHub (Jan 28, 2024):
7eee3fcccf8839db93dc- this is the reason I am using the more complex API at api.dondominio.com instead of dondns.dondominio.com"host"can now be something else than"@", and can be a subdomain or the wildcard"*". Please let me know if this is not possible, but I didn't spot any limitation on their documentation.Please let me know if it works, especially number 1. and perhaps number 3. 👍
@madmalkav commented on GitHub (Jan 28, 2024):
Thanks a lot for your work. I expect to be back in Spain in 2-3 weeks and will test extensively
@mateusan commented on GitHub (Jan 29, 2024):
EndPoint: api.dondominio.com -> not exists / old
EndPoint: https://simple-api.dondominio.net -> It is used for domain registration
Endpoint: https://dondns.dondominio.com/ -> Dynamic DNS URLs
@qdm12 commented on GitHub (Jan 29, 2024):
Thanks @mateusan
I'm not sure anymore where I read
api.dondominio.com, maybe just my mistake 🤔 Anyway it's changed tosimple-api.dondominio.netineee8485543and that should work (relevant service documentation)EDIT: Hopefully this doesn't trigger the
ERROR Post "https://simple-api.dondominio.net": read tcp 172.16.0.94:56986->37.152.88.150:443: read: connection reset by peererror ugh@mateusan commented on GitHub (Jan 29, 2024):
Yes, the new EndPoint for api.dondomain.com is simple-api.dondomain.net, but this endpoint is behind a FireWall. Therefore, it does not make sense to use this service for "Dynamic DNS".
@qdm12 commented on GitHub (Jan 29, 2024):
Oh sadly true...
Why not just sticking to rate limiting though?
It feels like the second part would do the trick and that the first part is kind of unneeded? Thanks!!
@mateusan commented on GitHub (Jan 29, 2024):
The service at simple-api.dondominio.net is focused on domain registration, not the "dynamic DNS" service
For "Dynamic DNS" services, use the other api. Any suggestions or changes needed, please let us know. We can even make a resource for you
@qdm12 commented on GitHub (Jan 29, 2024):
The point of the more complex API was to have ddns-updater create the A or AAAA record if it didn't exist (see issue #129 tracking this for existing providers).
I changed it in
f60f7212c3to use dondns.dondominio.com/json which should be working fine, I'll just add a note it's not possible to create records for dondominio. Thanks!@madmalkav commented on GitHub (Aug 13, 2024):
Live got complicated this year, and I had no chance to test this until recently. My container fails with this error:
Startup probe failed: 2024-08-13T17:17:43+02:00 ERROR program is unhealthy: record update failed: [domain: REDACTED | host: REDACTED | provider: dondominio | ip: ipv4]: failure (unsuccessful result: Incorrect data) 2024-08-13 17:17:29 CEST; Last success update: 2024-07-25 18:28:29 CEST; IP: REDACTED 2024-08-13T17:17:43+02:00 INFO Shutdown successfulI have tried every configuration I could think of, but nothing works. I think it might be related to the compulsory parameter "Name", as this is not mandatory according to the DonDominio docs
@qdm12 commented on GitHub (Aug 21, 2024):
The
namefield is unneeded indeed, and was not even used in the code. Removed in the code and the documentation in commitc7dbbcbaa0.I think I spotted the problem, and funnily enough, it's in their API documentation. They mention in https://dondominio.dev/en/dondns/docs/api/#usage the field
apikey, but in the example they have...&password=apikey&..., so I'm thinking maybe the key ispasswordinstead? Could you try:Does this work?? 🤔 If not, what error response do you get?
@madmalkav commented on GitHub (Aug 21, 2024):
It works OK with the API key, with the password it returns:
{"success":false,"version":"2.0","messages":["Wrong key"],"user":"","ts":"2024-08-21T12:12:58+02:00"}
Also, I think I didn't paste all the log info in my previous message, ddns-updater also throws:
Startup probe failed: 2024-08-21T11:59:51+02:00 ERROR program is unhealthy: lookup IP addresses do not match: REDACTED instead of REDACTED for REDACTED 2024-08-21T11:59:51+02:00 INFO Shutdown successful@qdm12 commented on GitHub (Aug 21, 2024):
Ok can you run ddns-updater with LOG_LEVEL=debug to see what request it sends to don dominio? I'm a bit confused, since it should work as it's currently using
apikey=password🤔@madmalkav commented on GitHub (Aug 21, 2024):
I edited my previous comment adding log information I forgot to add some days ago , I will try the LOG_LEVEL thing as soon as possible.
@madmalkav commented on GitHub (Aug 21, 2024):
As I mentioned in the past, I run ddns-updater in Truenas Scale. I'm starting to think the problem may be related to Truenas, because the log on ddns-updater looks ok, it sees the public IP correctly, sees it is already applied to the domain, and skips update.
2024-08-21T12:51:52.435997721+02:00 stdout F 2024-08-21T12:51:52+02:00 DEBUG ipv4 address of REDACTED is IP and your ipv4 address is SAME_IP, skipping updateBut on the Truenas GUI I see the error I posted before:
Startup probe failed: 2024-08-21T11:59:51+02:00 ERROR program is unhealthy: lookup IP addresses do not match: REDACTED instead of REDACTED for REDACTED 2024-08-21T11:59:51+02:00 INFO Shutdown successfulIt is showing an old IP and I don't know where that IP is coming from.
@qdm12 commented on GitHub (Aug 23, 2024):
Perhaps truenas shows an old unhealthy message? What do you get in a terminal with
docker inspect ddns-updaterin the healthcheck section?@madmalkav commented on GitHub (Aug 24, 2024):
The message was current and the web interface never became available. So definitively something to do with the startup probe. Now it is working OK, dunno why, will resume debugging next time I get an IP change. Maybe you want to close this ticket, as it seems it is not related to ddns-updater after all, or at least not with the Dondominio module.