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.
Posted on
Nothing really imporant though, but I just want to report a minor problem with Marcs Updater when it's used (that is, the service component/process) in cooperation with PsService program (basically it does same as Windows Net program) from Sysinternals. And with problem I mean that it doesn't (at least always) work as expected/it should.
So while pausing/resuming the service (almost always) works normally, restarting the service for example exists the process rather than restarting it.
Posted on
That is probably caused by PsService that does not run the program with the correct parameters. I don't think it's a problem with the program, because the Windows Service Manager is able to restart it without any trouble.