Marcs Updater
There have been some reports about issues with the Updater not updating anymore. Please try the latest beta version and switch to another IP Check provider instead of the previous default dnsomatic.com. For some reason they are rate-limiting the number of requests to their service. The new IP Check provider selection allows you to choose another provider in such cases. You can test the functionality with the new "Test" panel.
If you want to add a custom provider to the unstable testing version, store a JSON file like the following under %PROGRAMDATA%\Marcs Updater\ServiceProviders\dyndns.json:
{
"name": "DynDNS.org (Test)",
"endpoint": "https://members.dyndns.org/nic/update",
"method": "GET",
"queryString": "hostname={HOSTNAME}&myip={MYIP}",
"dataPayload": "",
"defaults": {
"username": "test",
"password": "test",
"hostname": "test1.customtest.dyndns.org"
}
}Supported query and payload tags are {USERNAME}, {PASSWORD}, {HOSTNAME} and {MYIP}. Restart the background service and foreground application to apply any changes.
Issue created on
Posted on
Joe wrote:
Hi Marc - I've confirmed my userid and password, your client states "The username and password pair does not match a real user" I've logged into DNS-O-Matic's control panel with the same userid and password that I'm using in your update client, which is my email address. Any ideas? Thank you!
Posted on
Joe wrote:
I figured out the problem - my password has special characters in it, such as a semi colon. Once I changed my password and removed the special characters, it worked.
Great software!
1
Posted on
koyut wrote:
I think this is a bug. I tried re-entering the password and it works okay without any changes. This happened to me when the client updated to the latest version.
Posted on
Marc wrote:
I just verified that this was indeed caused by a previous bug being fixed. Versions older than 1.5.2.290 included a bug in the code that retrieved the key to encrypt or decrypt the password. This bug was unintentionally fixed in this version, because there were other side effects. I am sorry for the inconvience, but you will have to re-enter your password with this new version. I will update the changelog with this information. I did not notice it, because I used an internal version that contained this fix since some months.
Posted on
grant wrote:
Same problem - I changed my password at dns-o-matic, and the s/w, and it all started working again.