[[Template core/front/global/updateWarning is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]]
The old forums are being retired in favour of a more modern (free) community platform.
These forums will remain accessible as a read only archive for the time being.
I have turned off all options I can find in Apex to stop it trying to phone-home, but it just keeps trying over and over. The last 2 versions have shown this phoning home, and I can only assume that in the past the attempts and frequency was better obscured? It looks like Apex contacts the project every minute or so whilst it is running! You appear to be monitoring users very closely, or at least gaining data on them:
[2014-01-06 13:33] Update Check: could not download digital signature (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (http://update.apexdc.net/version.xml.sign))
[2014-01-06 13:34] Update Check: could not connect to the update server (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (http://update.apexdc.net/version.xml))
[2014-01-06 13:34] Update Check: could not download digital signature (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (http://update.apexdc.net/version.xml.sign))
[2014-01-06 13:35] Update Check: could not connect to the update server (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (http://update.apexdc.net/version.xml))
[2014-01-06 13:35] Update Check: could not download digital signature (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (http://update.apexdc.net/version.xml.sign))
[2014-01-06 13:36] Update Check: could not connect to the update server (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (http://update.apexdc.net/version.xml))
[2014-01-06 13:36] Update Check: could not download digital signature (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (http://update.apexdc.net/version.xml.sign))
[2014-01-06 13:37] Update Check: could not connect to the update server (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (http://update.apexdc.net/version.xml))
[2014-01-06 13:37] Update Check: could not download digital signature (A connection attempt failed because the connected party did noĂ properly respond after a period of time, or established connection failed because connected host has failed to respond. (http://update.apexdc.net/version.xml.sign))
[2014-01-06 13:38] Update Check: could not connect to the update server (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (http://update.apexdc.net/version.xml))
[2014-01-06 13:38] Update Check: could not download digital signature (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (http://update.apexdc.net/version.xml.sign))
[2014-01-06 13:39] Update Check: could not connect to the update server (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (http://update.apexdc.net/version.xml))
[2014-01-06 13:39] Update Check: could not download digital signature (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (http://update.apexdc.net/version.xml.sign))
[2014-01-06 13:40] Update Check: could not connect to the update server (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (http://update.apexdc.net/version.xml))
The above kind of thing just fills the system log.
IIRC the update server address has changed a few times over versions of Apex which looks like active efforts to hinder people trying to protect their privacy. When I update Apex these days I download the source and grep it first so I know what host needs null-routing (why am I telling you? If I am correct then you'll just obfuscate things).
Please can you stop this behaviour and anything related? Cheers
Apex phoning home every minute
in Support
Posted
I have turned off all options I can find in Apex to stop it trying to phone-home, but it just keeps trying over and over. The last 2 versions have shown this phoning home, and I can only assume that in the past the attempts and frequency was better obscured? It looks like Apex contacts the project every minute or so whilst it is running! You appear to be monitoring users very closely, or at least gaining data on them:
The above kind of thing just fills the system log.IIRC the update server address has changed a few times over versions of Apex which looks like active efforts to hinder people trying to protect their privacy. When I update Apex these days I download the source and grep it first so I know what host needs null-routing (why am I telling you? If I am correct then you'll just obfuscate things).
Please can you stop this behaviour and anything related? Cheers