Login

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

anonymous-325768298

Posted on

RotBlitz wrote:

The new Securepoint DDNS function produces lots of "nochg" results. Whatever update check interval is configured in the Updater and whenever there is a new WLAN connect or TCP/IP settings change (e.g. DNS server), an unnecessary update is raised each time and at each interval. Not sure if Securepoint treats this as "abusive" leading to block the hostname (similar to DynDNS) soon.


mback2k

Posted on

Marc wrote:

I will take a look, thanks for the report.


mback2k

Posted on

Marc wrote:

Could you please enable logging by setting the system wide environment variable LOGLEVEL to 7 and then look for logfiles inside %ALLUSERSPROFILE% ?

From the code I can't see a problem right now.


anonymous-327507567

Posted on

RotBlitz wrote:

Thanks, will do soon. (Currently not much time...)


anonymous-329731362

Posted on

RotBlitz wrote:

Well, I did this, and as I can see from the logs, the problem is that the Updater "thinks" the IP address has changed, although it hasn't. Apparently a problem with the IP address comparison check. A typical log extract:

Internet is connected, checking IP using HTTPS
Validate current IP
Reading previous results from registry
Current IP is valid, compare to previous
Current IP does not equal previous IP, checking username
Sending IP update to remote service
Checking for empty result
Result is not empty, splitting into code and IP
Result = nochg
Setting next timer timeout to 2027 seconds


mback2k

Posted on

Marc wrote:

Please try the following build:
http://updater.marc-hoersken.d...

Changes:
Fixed new IP being empty if there was no good result before a nochg


anonymous-336183761

Posted on

RotBlitz wrote:

Unfortunately no difference...


mback2k

Posted on

Marc wrote:

It has to make at least one update until it gets the new IP and stores it inside the registry. Did you wait multiple updates?


anonymous-344299281

Posted on

RotBlitz wrote:

Hundreds - in between...


mback2k

Posted on

Marc wrote:

I am now looking into this problem.


mback2k

Posted on

Marc wrote:

It looks like it was a very stupid, but hidden mistake. The values read from the registry, like the IP address, which is compared to the new IP address contained a new line character at the end. Therefore all comparisons failed. Fix will be out soon™, hopefully.


mback2k

Posted on

Marc wrote:

The problem should be solved with version 1.5.0.257. Sorry for the late solution.