Your Question
Hello, and thank you in advance to whoever is reading this.
Scenario:
- TrueNAS -> Domain Locker (as a Docker app)
- 3 Docker containers, ix-domain-locker-domain-locker-1 (the app) + ix-domain-locker-postgres-1 (postgre) + ix-domain-locker-cron-1 (cron instance)
- 18 domains added to the Domain Locker instance (self-hosted)
One of the domains expired about a week ago, it was still within the grace period so I renewed it. Domain Locker, after several days, continues to show that domain as "Imminently" because it says it will expire in the next 30 days.
I check the cron container (which I assume is periodically updating the information) and see that the /crontasks file is configured to update the information every day at 3am:
0 3 * * * curl -f -X POST http://domain-locker:30376/api/domain-updater
I execute that line manually:
curl -f -X POST http://domain-locker:30376/api/domain-updater
And I find this related to the domain in question:
{"domain":"XXXXXXXXXX.com","error":"Request timed out after 5 seconds for \"XXXXXXXXXX.com\""},
However, if I run the following command right there in that container, it does return all the information, including the expiration date updated to the next year:
whois XXXXXXXXXX.com
[Querying whois.iana.org:43 '.com']
[Redirected to whois.verisign-grs.com]
[Querying whois.verisign-grs.com:43 'XXXXXXXXXX.com']
[whois.verisign-grs.com]
Domain Name: XXXXXXXXXX.COM
Registry Domain ID: 287XXXXX77_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2026-05-03T05:52:11Z
Creation Date: 2024-04-30T04:32:12Z
Registry Expiry Date: 2027-04-30T04:32:12Z
I also notice that the same "Request timed out after 5 seconds" error appears for 7 other domains, some of which have not even expired and will not expire soon.
Am I missing something? Could it be related to a WHOIS rate limit?
Thank you so much to whoever read this far, I appreciate a little guidance.
Your Question
Hello, and thank you in advance to whoever is reading this.
Scenario:
One of the domains expired about a week ago, it was still within the grace period so I renewed it. Domain Locker, after several days, continues to show that domain as "Imminently" because it says it will expire in the next 30 days.
I check the cron container (which I assume is periodically updating the information) and see that the /crontasks file is configured to update the information every day at 3am:
0 3 * * * curl -f -X POST http://domain-locker:30376/api/domain-updaterI execute that line manually:
curl -f -X POST http://domain-locker:30376/api/domain-updaterAnd I find this related to the domain in question:
{"domain":"XXXXXXXXXX.com","error":"Request timed out after 5 seconds for \"XXXXXXXXXX.com\""},However, if I run the following command right there in that container, it does return all the information, including the expiration date updated to the next year:
I also notice that the same "Request timed out after 5 seconds" error appears for 7 other domains, some of which have not even expired and will not expire soon.
Am I missing something? Could it be related to a WHOIS rate limit?
Thank you so much to whoever read this far, I appreciate a little guidance.