Closed GoogleCodeExporter closed 8 years ago
This issue is now solved in version 12.2.2
Original comment by gerard.f...@gmail.com
on 17 Aug 2012 at 2:26
Gerard -
In downloading v12.2.2 from the website, it keeps giving me v12.2.1
( http://prtg-addons.googlecode.com/files/PTF.TLDomainExpiration.zip )
Are you seeing the proper version there?
Original comment by scr...@turbs.com
on 17 Aug 2012 at 2:53
I have seen this before. It is some kind of cashing issue. Please download it
from an other pc or use a different browser.
Original comment by gerard.f...@gmail.com
on 17 Aug 2012 at 2:58
Ahh, thanks!
That update fixed the two domains I provided (and a few others) but I still
have some having an issue:
TLDomainExpiration.exe -d=barracudafilter.com
-106:The domain registration expires in -106 days.
Original comment by scr...@turbs.com
on 17 Aug 2012 at 4:23
There is an issue with the information provided by the whois website. It only
refreshes when requested by a browser. Once opened with a browser, the sensor
returns the correct information.
I'll look into this after my vacation.
Original comment by gerard.f...@gmail.com
on 17 Aug 2012 at 5:35
Can you try this beta version:
http://db.tt/GSWj7gTt
Please let me know if this solves your problem.
Original comment by gerard.f...@gmail.com
on 1 Sep 2012 at 2:41
Hello there. I am running PRTG V13.1.1.1181 and using TLDomainExpiration
v12.4.1.3 and having problems trying to get a good result. I have setup a
custom EXE/Script sensor with the -d=stinsonzone.com parameter (tried
yahoo.com) and keep getting back a "Protocol Error: No expiration date found".
I went into the whois.com website and looked up stinsonzone.com to find
everything looked normal. Can you suggest something I might try? My wife
would really be able to use this exe. Great idea.
Original comment by AStinso...@gmail.com
on 22 Feb 2013 at 1:33
This behaviour was caused by whois changing the layout of their website.
Version 13.1.1 of the sensor fixes this issue.
Original comment by gerard.f...@gmail.com
on 25 Feb 2013 at 12:48
Original issue reported on code.google.com by
scr...@turbs.com
on 17 Aug 2012 at 1:00